Author: objectiser Date: 2010-08-02 07:02:32 -0400 (Mon, 02 Aug 2010) New Revision: 900 Modified: branches/RiftSaw-2.1.x/samples/quickstart/bpel_event_listener/readme.txt trunk/samples/quickstart/bpel_event_listener/readme.txt Log: Added more information on the configuration of the BPEL processes to generate events. Modified: branches/RiftSaw-2.1.x/samples/quickstart/bpel_event_listener/readme.txt =================================================================== --- branches/RiftSaw-2.1.x/samples/quickstart/bpel_event_listener/readme.txt 2010-08-02 09:54:59 UTC (rev 899) +++ branches/RiftSaw-2.1.x/samples/quickstart/bpel_event_listener/readme.txt 2010-08-02 11:02:32 UTC (rev 900) @@ -20,3 +20,22 @@ At this point, you can now start the server and deploy/test any of the other examples, to see the activity event information being displayed in the server console log. + +NOTE: To generate activity events for a particular BPEL process, you will +need to edit the process's deployment descriptor to indicate what level +of events should be generated. The following example is the 'hello_world' +quickstart modified to indicate that all events should be reported to +a registered listener: + + <process name="bpl:HelloWorld"> + <active>true</active> + <process-events generate="all"/> + + <provide partnerLink="helloPartnerLink"> + <service name="intf:HelloService" port="HelloPort"/> + </provide> + </process> + +To find out more about the different levels of filtering that are possible, +please see the ODE documentation: http://ode.apache.org/ode-execution-events.html + Modified: trunk/samples/quickstart/bpel_event_listener/readme.txt =================================================================== --- trunk/samples/quickstart/bpel_event_listener/readme.txt 2010-08-02 09:54:59 UTC (rev 899) +++ trunk/samples/quickstart/bpel_event_listener/readme.txt 2010-08-02 11:02:32 UTC (rev 900) @@ -20,3 +20,22 @@ At this point, you can now start the server and deploy/test any of the other examples, to see the activity event information being displayed in the server console log. + +NOTE: To generate activity events for a particular BPEL process, you will +need to edit the process's deployment descriptor to indicate what level +of events should be generated. The following example is the 'hello_world' +quickstart modified to indicate that all events should be reported to +a registered listener: + + <process name="bpl:HelloWorld"> + <active>true</active> + <process-events generate="all"/> + + <provide partnerLink="helloPartnerLink"> + <service name="intf:HelloService" port="HelloPort"/> + </provide> + </process> + +To find out more about the different levels of filtering that are possible, +please see the ODE documentation: http://ode.apache.org/ode-execution-events.html +