riftsaw-commits August 2010

riftsaw-commits@lists.jboss.org

2 participants
54 discussions

Start a nNew thread

Hudson build became unstable: Riftsaw-soa-p #66

by jboss-qa-internal＠redhat.com

See <http://hudson.qa.jboss.com/hudson/job/Riftsaw-soa-p/66/changes>

13 years, 9 months

1
1
0 / 0

Hudson build became unstable: Riftsaw-soa-p-2.1.x #24

by jboss-qa-internal＠redhat.com

See <http://hudson.qa.jboss.com/hudson/job/Riftsaw-soa-p-2.1.x/24/changes>

13 years, 9 months

1
2
0 / 0

riftsaw SVN: r900 - trunk/samples/quickstart/bpel_event_listener and 1 other directory.

by riftsaw-commits＠lists.jboss.org

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 +

13 years, 9 months

1
0
0 / 0

riftsaw SVN: r899 - trunk/samples/quickstart/bpel_event_listener and 1 other directory.

by riftsaw-commits＠lists.jboss.org

Author: objectiser Date: 2010-08-02 05:54:59 -0400 (Mon, 02 Aug 2010) New Revision: 899 Modified: branches/RiftSaw-2.1.x/samples/quickstart/bpel_event_listener/readme.txt trunk/samples/quickstart/bpel_event_listener/readme.txt Log: Update readme for sample to make clearer. 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-07-22 07:25:41 UTC (rev 898) +++ branches/RiftSaw-2.1.x/samples/quickstart/bpel_event_listener/readme.txt 2010-08-02 09:54:59 UTC (rev 899) @@ -6,6 +6,8 @@ can be used to write a custom event listener for logging and management purposes. +NOTE: This example needs to be deployed when the server is not running. + To deploy the example, open a command line window in the example's folder, and simply type 'ant deploy'. To undeploy, use the command 'ant undeploy'. @@ -15,3 +17,6 @@ bpel.event.listeners=org.jboss.riftsaw.event.RiftSawEventListener +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. Modified: trunk/samples/quickstart/bpel_event_listener/readme.txt =================================================================== --- trunk/samples/quickstart/bpel_event_listener/readme.txt 2010-07-22 07:25:41 UTC (rev 898) +++ trunk/samples/quickstart/bpel_event_listener/readme.txt 2010-08-02 09:54:59 UTC (rev 899) @@ -6,6 +6,8 @@ can be used to write a custom event listener for logging and management purposes. +NOTE: This example needs to be deployed when the server is not running. + To deploy the example, open a command line window in the example's folder, and simply type 'ant deploy'. To undeploy, use the command 'ant undeploy'. @@ -15,3 +17,6 @@ bpel.event.listeners=org.jboss.riftsaw.event.RiftSawEventListener +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.

13 years, 9 months

1
0
0 / 0

← Newer
1
2
3
4
5
6
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

riftsaw-commits August 2010