Convert Invoker, Receiver, Replier and Alarm into Actions --------------------------------------------------------- Key: BPEL-234 URL: http://jira.jboss.com/jira/browse/BPEL-234 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public(Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1.GA The actions of invoking, receiving or replying a message, or waiting for an alarm, have long been decoupled from the activities that perform these actions: -Receive, Pick and OnMessage aggregate one or more Receivers to handle incoming messages. -Wait, Pick and OnAlarm aggregate one or more Alarms to wait for time events to occur -Invoke and Reply delegate to Invoker and Replier, respectively, for consistency with the design of Receivers and Alarms. If a multi-invoke or multi-reply activity was ever introduced, we'd be able to implement them readily. The relationship between the basic activities (Receive, Wait, Invoke and Reply) and corresponding actions (Receiver, Alarm, Invoker and Replier) resembles the relationship between Node and the main Action. The latter four classes currently extend Object. By extending Action instead, the following transformations become possible: -Fold the BPEL_INVOKER, BPEL_RECEIVER, BPEL_REPLIER and BPEL_ALARM tables into JBPM_ACTION. -Replace fields Receive.receiver, Wait.alarm, Invoke.invoker and Reply.replier with Node.action. -Move the execute method from the activities to the actions. The net result is FOUR tables less, and increased coherence between jPDL and BPEL.

Convert Invoker, Receiver, Replier and Alarm into Actions --------------------------------------------------------- Key: BPEL-234 URL: http://jira.jboss.com/jira/browse/BPEL-234 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public(Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA The actions of invoking, receiving or replying a message, or waiting for an alarm, have long been decoupled from the activities that perform these actions: -Receive, Pick and OnMessage aggregate one or more Receivers to handle incoming messages. -Wait, Pick and OnAlarm aggregate one or more Alarms to wait for time events to occur -Invoke and Reply delegate to Invoker and Replier, respectively, for consistency with the design of Receivers and Alarms. If a multi-invoke or multi-reply activity was ever introduced, we'd be able to implement them readily. The relationship between the basic activities (Receive, Wait, Invoke and Reply) and corresponding actions (Receiver, Alarm, Invoker and Replier) resembles the relationship between Node and the main Action. The latter four classes currently extend Object. By extending Action instead, the following transformations become possible: -Fold the BPEL_INVOKER, BPEL_RECEIVER, BPEL_REPLIER and BPEL_ALARM tables into JBPM_ACTION. -Replace fields Receive.receiver, Wait.alarm, Invoke.invoker and Reply.replier with Node.action. -Move the execute method from the activities to the actions. The net result is FOUR tables less, and increased coherence between jPDL and BPEL.