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

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.