[jboss-svn-commits] JBL Code SVN: r13633 - in labs/jbossesb/trunk/product: samples/quickstarts and 36 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Thu Jul 19 08:58:22 EDT 2007
Author: kevin.conner at jboss.com
Date: 2007-07-19 08:58:21 -0400 (Thu, 19 Jul 2007)
New Revision: 13633
Added:
labs/jbossesb/trunk/product/install/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/jbpm_simple1/readme.txt
Modified:
labs/jbossesb/trunk/product/samples/quickstarts/aggregator/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/build.xml
labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/build.xml
labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/business_rules_service/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/business_service/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/conf/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/deadletter/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/dynamic_router/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/fun_cbr/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/helloworld/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/helloworld_db_registration/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/helloworld_file_action/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/helloworld_ftp_action/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/helloworld_hibernate_action/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/helloworld_sql_action/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/messagefilter/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/messagestore/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/more_action/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/native_client/build.xml
labs/jbossesb/trunk/product/samples/quickstarts/native_client/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/recipient_list/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/scripting_groovy/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/simple_cbr/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/spring_aop/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/spring_helloworld/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/spring_jpetstore/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/static_router/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/transform_CSV2XML/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/transform_EDI2XML_Groovy_XSLT/build.xml
labs/jbossesb/trunk/product/samples/quickstarts/transform_EDI2XML_Groovy_XSLT/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2POJO/build.xml
labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2POJO/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/README.txt
labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/build.xml
labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_simple/build.xml
labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_simple/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/README.TXT
labs/jbossesb/trunk/product/samples/quickstarts/webservice_producer/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/wiretap/readme.txt
Log:
Updated readme files: JBESB-607
Added: labs/jbossesb/trunk/product/install/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/install/readme.txt (rev 0)
+++ labs/jbossesb/trunk/product/install/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -0,0 +1,26 @@
+The build.xml script in this directory is responsible for deploying the ESB
+ant it's dependencies into the appropriate environment.
+
+Deployment into JBoss AS 4.2.0.GA
+=================================
+ - Install JBoss AS 4.2.0.GA into an appropriate location.
+ - Copy deployment.properties-example to deployment.properties and configure
+ the org.jboss.esb.server.home and org.jboss.esb.server.config properties
+ to reflect the location of the application server and the required profile.
+ - execute 'ant deploy'
+
+Webservice support in JBoss AS 4.2.0.GA
+=======================================
+Webservice support requires installing JBossWS 2.0.0GA into the application
+server.
+ - Download jbossws-native-2.0.0.GA.zip and unpack in an appropriate
+ location.
+ - edit the ant.properties file and modify jboss42.home to reflect the
+ location of the application server installation.
+ - execute 'ant deploy-jboss42'
+
+An additional requirement is to install the jaxbintros found in the extras
+directory of the jbossesb installation.
+ - Follow the 'Deployment into JBoss AS 4.2.0.GA' section above (if not
+ already installed)
+ - execute 'ant deployIntros'
Property changes on: labs/jbossesb/trunk/product/install/readme.txt
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Name: svn:eol-style
+ native
Modified: labs/jbossesb/trunk/product/samples/quickstarts/aggregator/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/aggregator/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/aggregator/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,60 +1,63 @@
Overview:
=========
- The purpose of this particular example is to demonstrate the Enterprise Integration
- Patterns of Splitter and Aggregator. In addition, this example demonstrates the
- concepts of multiple JVMs, each running unique services but all working in concert,
- a federated model that shares a common registry and uses JMS between the JVMs.
- The registry is managed by the ESB SAR (see Getting Started Guide). This example
- assumes JBoss MQ running on JBoss AS 4.x. However, it uses no JBoss Application
- Server specific features.
+ The purpose of this particular example is to demonstrate the Enterprise
+ Integration Patterns of Splitter and Aggregator. In addition, this example
+ demonstrates the concepts of multiple JVMs, each running unique services but
+ all working in concert, a federated model that shares a common registry and
+ uses JMS between the JVMs.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. Command Window 1: "ant jar" - compiles and builds the JARS
- 3. Command Window 1: "ant run" - contains the splitter
- It will display the entire XML message to its console
- 4. Command Window 2: "ant runRedService" - rips out just the Customer
- It will display just the Customer information to its console
- 5. Command Window 3: "ant runGreenService" - rips out just the LineItems
- It will display just the LineItems to its console
- 6. Command Window 4: "ant runBlueService" - rips out just the OrderHeader
- It will display just the Order header information to its console
- 7. Command Window 5: "ant runAggregatorService" - displays the parts together
- It will simply push out the individual message parts. More details on how that is
- achieved can be found below
- 8. Command Window 6: "ant runtest" - this sends the SampleOrder.xml into the splitter's queue
- 9. The split off messages can be set out from the ESB via Notification. You can run
- "ant receiveRed", "ant receiveGreen" and "ant receiveBlue" in three more command windows
- plus modify the Red, Green and Blue service's jbossesb.xml files to use notification
- to send to the appropriate queues. Notification is demonstrated in the fun_cbr quickstart.
- The Red Service doesn't notify, feel free to add in the XML necessary (copy from Blue or Green)
- and tweak. When you save Red's jbossesb.xml it will be automatically hot deployed.
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ This executes the splitter.
+ 3. In a command terminal window in this folder ("Window2"), type
+ 'ant runRedService'. This rips out the Customer.
+ 4. In a command terminal window in this folder ("Window3"), type
+ 'ant runGreenService'. This rips out the LineItems.
+ 5. In a command terminal window in this folder ("Window4"), type
+ 'ant runBlueService'. This rips out the OrderHeader.
+ 6. In a command terminal window in this folder ("Window5"), type
+ 'ant runAggregatorService'. Displays individual parts together.
+ 7. In a command terminal window in this folder ("Window6"), type
+ 'ant receiveRed'.
+ 8. In a command terminal window in this folder ("Window7"), type
+ 'ant receiveGreen'.
+ 9. In a command terminal window in this folder ("Window8"), type
+ 'ant receiveBlue'.
+ 10. Open another command terminal window in this folder ("Window9"), type
+ 'ant runtest'.
+ 11. Switch back to the previous windows to see the output.
+ 12. When finished, interrupt the ESB, services and receivers using Ctrl-C.
+ 13. Undeploy the JMS configuration, type 'ant undeploy-jms-dests'.
-
What to look at in this Quickstart:
===================================
- The aggregation action (SystemPrintln in this case) needs to contain logic for handling
- the "parts". The trick is using ActionUtils.getTaskObject(message) and then looping
- through the attachments:
+ The aggregation action (SystemPrintln in this case) needs to contain logic
+ for handling the "parts". The trick is to use ActionUtils.getTaskObject() and
+ loop through the attachments:
- public Message process(Message message) throws ActionProcessingException {
- Object messageObject = ActionUtils.getTaskObject(message);
+ public Message process(Message message) throws ActionProcessingException {
+ Object messageObject = ActionUtils.getTaskObject(message);
- if(messageObject instanceof byte[]) {
- System.out.println(printlnMessage + ": \n[" + format(new String((byte[])messageObject)) + "].");
- } else {
- if (messageObject!=null) System.out.println(printlnMessage + ": \n[" + format(messageObject.toString()) + "].");
- for (int i=0; i<message.getAttachment().getUnnamedCount(); i++) {
- Message attachedMessage = (Message) message.getAttachment().itemAt(i);
- System.out.println("attachment " + i + ": [" + new String(attachedMessage.getBody().getContents()) + "].");
- }
- }
- return message;
- }
-
+ if(messageObject instanceof byte[]) {
+ System.out.println(printlnMessage + ": \n[" +
+ format(new String((byte[])messageObject)) + "].");
+ } else {
+ if (messageObject!=null)
+ System.out.println(printlnMessage + ": \n[" +
+ format(messageObject.toString()) + "].");
+ for (int i=0; i<message.getAttachment().getUnnamedCount(); i++) {
+ Message attachedMessage = (Message) message.getAttachment().itemAt(i);
+ System.out.println("attachment " + i + ": [" +
+ new String(attachedMessage.getBody().getContents()) + "].");
+ }
+ }
+ return message;
+ }
Modified: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/build.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/build.xml 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/build.xml 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,4 +1,4 @@
-<project name="Quickstart_bpm_orchestration1" default="esb" basedir=".">
+<project name="Quickstart_bpm_orchestration1" basedir=".">
<description>
${ant.project.name}
@@ -32,8 +32,12 @@
</target>
<target name="run">
- <echo message="This target is not implemented for this quickstart. Please run 'ant deploy' and the 'ant runtest'"/>
+ <echo message="This target is not implemented for this quickstart. Please run 'ant deploy', 'ant deployProcess' and 'ant startProcess'"/>
</target>
+
+ <target name="runtest">
+ <echo message="This target is not implemented for this quickstart. Please run 'ant deployProcess' and 'ant startProcess'"/>
+ </target>
<target name="refreshProcess" description="Moves the changed process definition to the server without restarting all the services">
<echo>Moves the changed process definition to the server without restarting all the services</echo>
@@ -62,4 +66,12 @@
</java>
</target>
+ <target name="display-instructions">
+ <echo message='${line.separator}******************' />
+ <echo>Quickstart deployed to target JBoss ESB/App Server at '${org.jboss.esb.server.deploy.dir}'.</echo>
+ <echo>1. Check your ESB Server console to make sure the deployment was executed without errors.</echo>
+ <echo>2. Run 'ant deployProcess' and 'ant startProcess' to run the Quickstart.</echo>
+ <echo>3. Check your ESB Server console again. The Quickstart should have produced some output.</echo>
+ <echo message='******************' />
+ </target>
</project>
Added: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/readme.txt (rev 0)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -0,0 +1,39 @@
+Overview:
+=========
+ The purpose of the bpm_orchestration1 quickstart sample is to demonstrate the
+ integration of a process definition into JBoss ESB.
+
+To Run '.esb' archive mode:
+===========================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant deployProcess'.
+ 3. Switch back to Application Server console and wait for the message
+ '[SchemaExport] schema export complete' to appear on the console.
+ 4. Switch back to "Window2", type 'ant startProcess'.
+ 5. Switch back to Application Server console to see the output from the ESB.
+ 6. To undeploy the esb archive, type 'ant undeploy' ("Window1").
+
+Sample Output from "ant startProcess":
+======================================
+10:42:14,386 INFO [MessageSpy] Body: Start It Up
+10:42:14,463 INFO [ProcessInfo] Token ID: 1
+10:42:14,463 INFO [ProcessInfo] Process Name: null
+10:42:14,463 INFO [ProcessInfo] Process Version: null
+10:42:14,463 INFO [MessageSpy] Body: Start It Up
+10:42:14,482 WARN [ProxyWarnLog] Narrowing proxy to class org.jbpm.graph.node.StartState - this operation breaks ==
+10:42:15,182 INFO [STDOUT] 1********** Begin Service 1 ***********
+10:42:15,263 INFO [STDOUT] In: Start It Up
+10:42:15,263 INFO [STDOUT] Out: Service 1 Start It Up
+10:42:15,263 INFO [STDOUT] ************ End Service 1 ************
+10:42:15,747 INFO [STDOUT] 2********** Begin Service 2 ***********
+10:42:15,747 INFO [STDOUT] In: Start It Up
+10:42:15,747 INFO [STDOUT] Out: Service 2 Start It Up
+10:42:15,748 INFO [STDOUT] ************ End Service 2 ************
+10:42:16,889 INFO [STDOUT] 3********** Begin Service 3 ***********
+10:42:16,890 INFO [STDOUT] In: Start It Up
+10:42:16,890 INFO [STDOUT] Out: Service 3 Start It Up
+10:42:16,890 INFO [STDOUT] ************ End Service 3 ************
+10:42:17,596 INFO [STDOUT] Executed by the process, not by the ESB
+10:42:17,653 INFO [MessageSpy] Body: Start It Up
+10:42:18,637 INFO [MessageSpy] Body: Start It Up
Property changes on: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/readme.txt
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Name: svn:eol-style
+ native
Modified: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/build.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/build.xml 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/build.xml 2007-07-19 12:58:21 UTC (rev 13633)
@@ -47,4 +47,12 @@
</java>
</target>
+ <target name="display-instructions">
+ <echo message='${line.separator}******************' />
+ <echo>Quickstart deployed to target JBoss ESB/App Server at '${org.jboss.esb.server.deploy.dir}'.</echo>
+ <echo>1. Check your ESB Server console to make sure the deployment was executed without errors.</echo>
+ <echo>2. Run 'ant deployProcess' and 'ant startProcess' to run the Quickstart.</echo>
+ <echo>3. Check your ESB Server console again. The Quickstart should have produced some output.</echo>
+ <echo message='******************' />
+ </target>
</project>
Modified: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,81 +1,75 @@
Overview:
=========
- The purpose of the bpm_orchestration2 quickstart sample is to demonstrate the
-use of JMS-based endpoints/services where the flow of execution is controlled by
-the process definition. The process definition also includes a fork & join and
-makes each service invocation in a synchronous fashion.
+ The purpose of the bpm_orchestration2 quickstart sample is to demonstrate the
+ use of JMS-based endpoints/services where the flow of execution is controlled
+ by the process definition. The process definition also includes a fork & join
+ and makes each service invocation in a synchronous fashion.
-
To Run standalone mode:
=======================
-1. Open two command windows in the directory called "bpm_orchestration2"
-2. In command window 1, execute "ant deploy-jms-dests"
-3. In command window 1, execute "ant run" - starts the ESB in standalone mode
-4. In command window 2, execute "ant deployProcess" - sends a message that fires
-a service that loads the process definition from the file system and into the
-repository.
-5. In command window 2, execute "ant startProcess" - this sends a messge that
-causes a new process instance to be created and "signaled", since this process
-definition contains no wait-states it will execute until completion.
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant deployProcess' to deploy the process.
+ 4. Switch back to ESB console and wait for the message
+ 'Process Definition Deployed:' to appear on the console.
+ 5. Switch back to "Window2", type 'ant startProcess' to start the process.
+ 6. Switch back to "Window1" to see the output from the ESB
+ 7. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
-1. ant deploy - creates a folder called "Quickstart_bpm_orchestration2.esb" in
-your targeted deploy directory.
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant deployProcess'.
+ 3. Switch back to Application Server console and wait for the message
+ 'Process Definition Deployed:' to appear on the console.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
+ 5. Switch back to Application Server console to see the output from the ESB.
+ 6. To undeploy the esb archive, type 'ant undeploy' ("Window1").
-2. ant deployProcess - sends a message that fires a service that loads the
-process definition from the file system and into the repository. Alternatively,
-you could have deployed the process definition via the jBPM Graphical Process
-Designer or the jBPM web console.
-You will know when the process definition is successfully deployed when you see
-a lot of jBPM & Hibernate logging activity with something similiar to the
-following as the last 4 lines:
-11:16:08,859 INFO [SchemaExport] Running hbm2ddl schema export
-11:16:08,875 INFO [SchemaExport] exporting generated schema to database
-11:16:09,015 INFO [SchemaExport] schema export complete
-11:16:11,656 INFO [STDOUT] Process Definition Deployed:
-
-3. ant startProcess - this sends a messge that causes a new process instance to
-be created and "signaled", since this process definition contains no wait-states
-it will execute until completion. This step causes a lot of output to the
-server console as each node/service is visited in the process graph. Look for
-"SUCCESS!" to indicate that the service called "ResultsService" was invoked.
-
Extra Credit:
=============
-1. Modify the process definition using your favorite editor or the Grahpical
-Process Desginer (from jBPM 3.2.x). Remove the following transitions from the
-fork to Atlanta and Dallas:
- <transition name="tr2" to="Dallas WHSE"></transition>
- <transition name="tr3" to="Atlanta WHSE"></transition>
-This change means that the flow of execution will bypass Service6 and Service7.
+ 1. Modify the process definition using your favorite editor or the Grahpical
+ Process Desginer (from jBPM 3.2.x). Remove the following transitions from
+ the fork to Atlanta and Dallas:
-2. ant refreshProcess - This step copies the newly changed process definition to
-its appropriate location in the deployed .esb archive and then invokes the
-deployProcess command.
+ <transition name="tr2" to="Dallas WHSE"></transition>
+ <transition name="tr3" to="Atlanta WHSE"></transition>
-3. ant startProcess - Service6 (Dallas) and 7 (Atlanta) are gone.
+ This change means that the flow of execution will bypass Service6 and
+ Service7.
-Feel free to rewire the process definition in any order that you like to see the
-change in execution flow.
+ 2. ant refreshProcess - This step copies the newly changed process definition
+ to its appropriate location in the deployed .esb archive and then invokes
+ the deployProcess command.
+ 3. ant startProcess - Service6 (Dallas) and 7 (Atlanta) are gone.
+ Feel free to rewire the process definition in any order that you like to see
+ the change in execution flow.
+
Things to Consider:
-===========================
-- BPM related quickstarts deploy as an exploded archive.
-- The service "logic" is coded in Groovy
-- Carefully review the jboss-esb.xml and the processdefinition.xml. One of the
-key things to understand is how the ESB action invokes or interacts with the
-process and how it moves ESB message data into process instance variables.
- <property name="esb-to-jbpm">
+===================
+ - BPM related quickstarts deploy as an exploded archive.
+ - The service "logic" is coded in Groovy
+ - Carefully review the jboss-esb.xml and the processdefinition.xml. One of
+ the key things to understand is how the ESB action invokes or interacts with
+ the process and how it moves ESB message data into process instance
+ variables.
+
+ <property name="esb-to-jbpm">
<variables>
- <variable esb-name="esbMsgVar1" jbpm-name="processVar1" />
- <variable esb-name="BODY_CONTENT" jbpm-name="theBody" />
+ <variable esb-name="esbMsgVar1" jbpm-name="processVar1" />
+ <variable esb-name="BODY_CONTENT" jbpm-name="theBody" />
</variables>
- </property>
+ </property>
- esb-name maps to Message.getBody().get("esbMsgVar1")
- "BODY_CONTENT" maps to Message.getBody()
+ esb-name maps to Message.getBody().get("esbMsgVar1")
+ "BODY_CONTENT" maps to Message.getBody()
Sample Output from "ant startProcess":
======================================
Modified: labs/jbossesb/trunk/product/samples/quickstarts/business_rules_service/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/business_rules_service/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/business_rules_service/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,24 +1,47 @@
-Description:
- Demonstrates the use of the BusinessRulesProcessor which allows for modification of the POJOs
- attached to an ESB Message. The example uses Rules to calculate the priority associated with an
- inbound order for later routing, plus it calculates the discount percentage associated with an
- order.
+Overview:
+=========
+ Demonstrates the use of the BusinessRulesProcessor which allows for
+ modification of the POJOs attached to an ESB Message. The example uses Rules
+ to calculate the priority associated with an inbound order for later routing,
+ plus it calculates the discount percentage associated with an order.
-Prereqs:
- First make sure you have run simple_cbr, transformation_XML2POJO and fun_cbr quickstarts as their
- principles are used in this more complex example.
-
-Notes:
- - To test:
- -- startup the ESB Server
- -- ant deploy-jms-dests
- -- ant run (terminal window 1)
- -- ant runtest (terminal window 2)
- - Only runs via standalone bootstrapper (ant run), NOT with a .esb archive (ant deploy)
- - Only has queue declarations for JBoss Messaging, NOT JBossMQ
- - Review the 3 different .drl files to see the distinction between business rules used for
- calculation/validation and rules used for routing.
- - The customer status is actually set in the jboss-esb.xml via the SetupMessage action since
- it is not provided with the inbound XML. You don't want a customer to determine their status.
- In a real world situation, another system would be integrated via an action/service, that first
- calculates the customer's status (frequent flier, volume of previous purchases, etc.)
\ No newline at end of file
+ Make sure you have run simple_cbr, transformation_XML2POJO and fun_cbr
+ quickstarts as their principles are used in this more complex example.
+
+Running this quickstart:
+========================
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
+
+ A comprehensive description of message transformation can be found in
+ MessageTransformation.pdf, located in the docs/services folder.
+
+To Run standalone mode:
+=======================
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
+
+To Run '.esb' archive mode:
+===========================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
+
+What to look at in this Quickstart:
+===================================
+ Review the 3 different .drl files to see the distinction between business
+ rules used for calculation/validation and rules used for routing.
+
+ The customer status is actually set in the jboss-esb.xml via the SetupMessage
+ action since it is not provided with the inbound XML. You don't want a
+ customer to determine their status. In a real world situation, another
+ system would be integrated via an action/service, that first calculates the
+ customer's status (frequent flier, volume of previous purchases, etc.)
\ No newline at end of file
Modified: labs/jbossesb/trunk/product/samples/quickstarts/business_service/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/business_service/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/business_service/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,59 +1,23 @@
Overview:
=========
- This example demonstrates the how to access an EJB3 Stateless Session Bean
- from within an ESB Action. ESB Actions are primarily custom mediation
- components. They allow you to introduce different specialized transformations,
- routing behaviors, orchestration, etc. The EJB3 is a simple "Hello World"
- annotated POJO.
+ This example demonstrates the how to access an EJB3 Stateless Session Bean
+ from within an ESB Action. ESB Actions are primarily custom mediation
+ components which allow you to introduce different specialized transformations,
+ routing behaviors, orchestration, etc. The EJB3 is a simple "Hello World"
+ annotated POJO.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
- This example does require you to use a version for 4.0.4+ with the EJB3 profile.
- Note: This example doesn't have a deploy task implemented at this time.
+ Note, this quickstart requires an ESB embedded in JBoss AS 4.2.0.GA.
+ Installation instructions can be found in the install/readme.txt.
-To Run standalone mode:
-=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-queues'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
-
- 'run' target description:
- In the first command window, execute "ant". This will compile the project, build
- the needed jars and deploy the EJB3 component to the Application Server. If you are
- monitoring the Application Server console you will see it hot deploy the EJB3 jar.
- Shutdown the listener by simply using Ctrl-C in that window.
-
- 'runtest' target description:
- In a second command window, execute "ant runtest". You will see the ESB console
- (the first command window) display:
- [echo] Action uses EJB as a business service
-
- [java] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
- [java] Body: Your Name
- [java] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
-
- [java] Invoked EJB3: Hello World: Your Name Mon Jan 29 21:41:23 EST 2007
-
- [java] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
- [java] Body: Hello World: Your Name Mon Jan 29 21:41:23 EST 2007
- [java] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
-
- You should also notice the following on the Application Server console window:
- 21:41:23,515 INFO [STDOUT] Saying Hello to Your Name
-
-What to look at in this Quickstart:
-===================================
- The EJB3 POJO is very simple and the build.xml also includes tasks for testing the EJB3
- standalone apart from the ESB. You can execute "ant testasejb" to test the EJB3
- component by itself.
- The action is also very simple:
- InitialContext ctx = new InitialContext();
-
- HelloWorld client = (HelloWorld) ctx.lookup("HelloWorldBean/remote");
- results = client.sayHello(contents);
-
-
+To Run '.esb' archive mode:
+===========================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/conf/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/conf/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/conf/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,66 +1,65 @@
Quickstarts information:
========================
- The quickstarts come in two forms:
- 1. standalone mode which is started by 'ant run'
- 2. '.esb' package which is deployed to an application server by running 'ant deploy'.
+ The quickstarts come in two forms:
+ 1. standalone mode which is started by 'ant run'
+ 2. '.esb' package which is deployed to an application server by running
+ 'ant deploy'.
Before Running:
===============
- Non Bundled:
- 1. Copy install/deployment.properties-example to install/deployment.properties and modify the
- properties there to suit your environment[*].
- 2. Run 'ant deploy' in the "install" folder of the distribution. This
- deploys the required SARs to your JBoss Application Server instance.
- 3. Make sure the JBoss Application server is running.
+ 1. Copy install/deployment.properties-example to install/deployment.properties
+ and modify the properties there to suit your environment[*].
+ 2. Run 'ant deploy' in the "install" folder of the distribution. This
+ deploys the required SARs to your JBoss Application Server instance.
+ 3. Make sure the JBoss Application server is running.
- Bundled:
- 1. Copy install/deployment.properties-example to install/deployment.properties and modify the
- properties there to suit your environment[*].
- 2. Run 'ant install' in the "install" folder of the distribution. This
- target will unpack the JBoss Application Server to the localtion you specified in step 1
- 2. Run 'ant deploy' in the "install" folder of the distribution. This
- deploys the required SARs to your JBoss Application Server instance.
- 4. Make sure the JBoss Application server is running.
-
[*]
-It is often a good idea to copy the default server configuration to a different name
-so that you can easily start a fresh one by simply deleting it. This also makes it simple
-to diff both directories to find differences if problems occur.
-So, if you copied the default server configuration use the new configuration name for the property
-'org.jboss.esb.server.config' in install/deployment.properties.
-You can optionally copy the file samples/quickstarts/conf/quickstarts.properties-example to quickstart.properties
-if you want to run the quickstarts against a different server then the one specified in step 1 above. This is also
-needed if you run any of the quickstarts that use ftp.
+It is often a good idea to copy the default server configuration to a different
+name so that you can easily start a fresh one by simply deleting it. This also
+makes it simple to diff both directories to find differences if problems occur.
+So, if you copied the default server configuration use the new configuration
+name for the property 'org.jboss.esb.server.config' in
+install/deployment.properties.
+You can optionally copy the file conf/quickstarts.properties-example to
+quickstart.properties if you want to run the quickstarts against a different
+server then the one specified in step 1 above. This is also needed if you run
+any of the quickstarts that use ftp.
+
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- See the section "Notes about JMS" for more information.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
- 5. Run 'ant help' to get a description about the specific quickstart.
+ 1. In a command terminal window in the quickstart folder type 'ant
+ deploy-jms-dests'.
+ See the section "Notes about JMS" for more information.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to Application Server console to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In a command terminal window in this folder ("Window1"), type 'ant
+ undeploy'.
Notes about JMS:
================
- The standalone ESB uses JMS provided by a JBoss Application Server instance. This means
- that jms queues must be configured before running :
- 'ant deploy-jms'
+ The standalone ESB uses JMS provided by a JBoss Application Server instance.
+ This means that jms queues must be configured before running :
+ 'ant deploy-jms-dests'
- A '.esb' package is self-contained and has queue definitions that it needs in the 'esb'
- archive.
- Since we wanted to show you that the jboss-esb.xml configuration is the same for both modes
- of running the ESB the queue names are the same which means that if you have run the standalone
- mode and want to try the '.esb. archive mode you need to run :
- 'ant undeploy-jms-dests'
+ A '.esb' package is self-contained and has queue definitions that it needs in
+ the 'esb' archive.
+ Since we wanted to show you that the jboss-esb.xml configuration is the same
+ for both modes of running the ESB the queue names are the same which means
+ that if you have run the standalone mode and want to try the '.esb. archive
+ mode you need to run :
+ 'ant undeploy-jms-dests'
-More information about the quickstart can be found in the GettingStarted.pdf document, which is in
-the doc folder.
-
+More information about the quickstart can be found in the GettingStarted.pdf
+document, which is in the doc folder.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/deadletter/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/deadletter/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/deadletter/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,86 +1,57 @@
Overview:
=========
- The purpose of the messagestore quickstart sample is to show how to send
- a message in the DeadLetter Service. The interesting piece of configuration
- is:
-
- <!-- Add a copy of the message to the message store under categorization 'test' -->
- <action name="PersistAction" class="org.jboss.soa.esb.actions.MessagePersister" >
- <property name="classfication" value="test"/>
- <property name="message-store-class" value="org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl"/>
- </action>
-
- Which causes a message to be saved in the DB messageStore under the categorization 'test'. Tooling
- will be added to inspect the messageStore.
+ The purpose of the messagestore quickstart sample is to show how to send
+ a message in the DeadLetter Service. The interesting piece of configuration
+ is:
+ <!-- Add a copy of the message to the message store under categorization
+ 'test' -->
+ <action name="PersistAction" class="org.jboss.soa.esb.actions.MessagePersister" >
+ <property name="classfication" value="test"/>
+ <property name="message-store-class"
+ value="org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl"
+ />
+ </action>
+
+ Which causes a message to be saved in the DB messageStore under the
+ categorization 'test'. Tooling will be added to inspect the messageStore.
+
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch back to Application Server console to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. You might review the build.xml file to see how it is setup.
- More details on the build.xml can be found later in this document. Shutdown
- the listener by simply using Ctrl-C in that window.
+What to look at in this Quickstart:
+===================================
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" to shoot a JMS message
- into the listener which will then invoke the MyJMSListenerAction and display
- it to the console. You can modify the build.xml to change the phrase
- "Hello World" to something else and re-run "ant runtest".
+ src\quickstart\CheckMessageStoreAction.java:
+ The action class that is identified in the esb-config.xml file and is called
+ whenever a message is received.
-Project file descriptions:
-==========================
+ src\quickstart\helloworld\test\SendJMSMessage.java:
+ Shoots in the string passed in via the command line or in this case the arg
+ attribute in the ant runtest task.
- jbossesb.xml:
- The JMS gateway and ESB configuration file. It is listening for JMS ObjectMessages or TextMessages
- at "queue/quickstart_messagestore_Request". Messages received at "quickstart_messagestore_Request" are
- converted jbossesb-properties.xml. Also needed by jUDDI and needs to be at the head of the classpath.
- The jbossesb-properties.xml is used when the service first boots up for
- self-registration based upon the service-category and service-name found in the esb-config.xml file.
-
- jndi.properties:
- Needed primarily for org.jboss.soa.esb.samples.quickstart.messagestore.test.SendJMSMessage that is fired by ant runtest.
-
- log4j.xml:
- Needed to configure log4J used by both the quickstart and the ESB itself. A listener needs a place to log.
-
- src\quickstart\CheckMessageStoreAction.java:
- The action class that is identified in the esb-config.xml file and is called whenever a message is received.
-
- src\quickstart\helloworld\test\SendJMSMessage.java:
- Shoots in the string passed in via the command line or in this case the arg attribute in the ant runtest task.
-
- src\quickstart\helloworld\test\SendEsbMessage.java:
- Shoots in the string passed in via the command line or in this case the arg atribute in the ant sendesb task.
- This demonstrates how to build an "ESB aware" client that can invoke an ESB service.
-
- build.xml:
- Targets and structure description:
- * the classpath property pulls the jbossesb-properties.xml file to the
- front of the list
- * the echoCP task is useful for making sure what you think is in your classpath is actually in your classpath
- Usage is: ant echoCP > myclasspath.txt
- This generates a file called myclasspath.txt which can be reviewed in a text editor
- * the run task calls the Launcher passing in 3 arguments the most important are the esb-config.xml and
- esb-config-gateway.xml files
- * the runtest task calls the org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage class and passes in an argument representing
- the string-based message to be pused into the queue the gateway is listening on. Note: SendJMSMessage
- contains a hard-coded queue name.
-
-
+ src\quickstart\helloworld\test\SendEsbMessage.java:
+ Shoots in the string passed in via the command line or in this case the arg
+ atribute in the ant sendesb task. This demonstrates how to build an "ESB
+ aware" client that can invoke an ESB service.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/dynamic_router/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/dynamic_router/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/dynamic_router/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,54 +1,69 @@
Overview:
=========
- The purpose of the dynamic router list quickstart sample is demonstrate
- the recipient list EIP pattern (as defined here:
- http://www.enterpriseintegrationpatterns.com/DynamicRouter.html
+ The purpose of the dynamic router list quickstart sample is demonstrate
+ the recipient list EIP pattern (as defined here:
+ http://www.enterpriseintegrationpatterns.com/DynamicRouter.html
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the
- quickstarts and a more detailed descripton of the different ways to
- run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type ant receive-destination1'
- 4. Open another command terminal window in this folder ("Window3"), type ant receive-destination2'
- 5. Open another command terminal window in this folder ("Window4"), type ant receive-destination3'
- 6. Open another command terminal window in this folder ("Window5"), type 'ant runtest'.
- (Note the other ant targets listed below.)
- 7. Switch back to "Window2", "Window3", "Window4" to see the output from the ESB.
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. In a command terminal window in this folder ("Window2"), type
+ 'ant receive-destination1'.
+ 4. In a command terminal window in this folder ("Window3"), type
+ 'ant receive-destination2'.
+ 5. In a command terminal window in this folder ("Window4"), type
+ 'ant receive-destination3'.
+ 6. Open another command terminal window in this folder ("Window5"), type
+ 'ant runtest'.
+ 7. Switch back to "Window1", "Window2", "Window3" and "Window4" to see the
+ output from the ESB
+ 8. When finished, interrupt the ESB and receivers using Ctrl-C.
+ 9. Undpeloy the JMS configuration, type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder (Window2"), type ant receive-destination1'
- 4. Open another command terminal window in this folder ("Window3"), type ant receive-destination2'
- 5. Open another command terminal window in this folder ("Window4"), type ant receive-destination3'
- 6. Open another command terminal window in this folder ("Window5"), type 'ant runtest'.
- 7. Switch back to "Window2", "Window3", "Window4" to see the output from the ESB.
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. In a command terminal window in this folder ("Window2"), type
+ 'ant receive-destination1'.
+ 3. In a command terminal window in this folder ("Window3"), type
+ 'ant receive-destination2'.
+ 4. In a command terminal window in this folder ("Window4"), type
+ 'ant receive-destination3'.
+ 5. In "Window1", type 'ant runtest'.
+ 6. Switch back to the Application Server console, "Window2", "Window3" and
+ "Window4" to see the output from the ESB
+ 7. When finished, interrupt the receivers using Ctrl-C.
+ 8. Undpeloy the esb archive, type 'ant undeploy'.
+
+Things to Consider:
+===================
+ You can modify the argument defined in build.xml to control which channels
+ receive the messages. A value other than ":OK" will result in a destination
+ instance not receiving messages through the router. Stopping and starting the
+ destination app (for example: ant receive-destination1) instance will cause
+ the dynamic router rule base to be updated.
- You can modify the argument defined in build.xml to control which channels receive the
- messages. A value other than ":OK" will result in a destination instance not receiving
- messages through the router. Stopping and starting the destination app (for example:
- iant receive-destination1) nstance will cause the dynamic router rule base to be updated.
-
- The contents of the Hashtable - this is persisted in a serialized object written to a file
- in the server's bin directory - that holds the dynamic router's rule base is displayed on
- the server's stdout when it is changed. For example:
-
- [STDOUT] Writing Hashtable to disk
- [STDOUT] Hashtable entry: key = queue/qsdynamicrouter_1_Request, value = OK
- [STDOUT] Hashtable entry: key = queue/qsdynamicrouter_2_Request, value = not_OK
- [STDOUT] Hashtable entry: key = queue/qsdynamicrouter_3_Request, value = OK
+ The contents of the Hashtable - this is persisted in a serialized object
+ written to a file in the server's bin directory - that holds the dynamic
+ router's rule base is displayed on the server's stdout when it is changed.
+ For example:
+
+ [STDOUT] Writing Hashtable to disk
+ [STDOUT] Hashtable entry: key = queue/qsdynamicrouter_1_Request, value = OK
+ [STDOUT] Hashtable entry: key = queue/qsdynamicrouter_2_Request, value = not_OK
+ [STDOUT] Hashtable entry: key = queue/qsdynamicrouter_3_Request, value = OK
- The quickstart makes use of the queues illustrated (the queues are shown
- in boxes) in the following diagram. You might review the build.xml file to
- see how it is setup. More details on the build.xml can be found later in
- this document.
+ The quickstart makes use of the queues illustrated (the queues are shown
+ in boxes) in the following diagram. You might review the build.xml file to
+ see how it is setup. More details on the build.xml can be found later in
+ this document.
application initiated
|
@@ -72,45 +87,3 @@
| ------------------------------- |
|---------------------------- |dynamicrouter_Control_Request| <--------------------|
-------------------------------
-
-Project File Descriptions
-=========================
-
- * jbossesb.xml - the JMS gateway and ESB configuration file.
-
- * jbossesb-properties.xml - also needed by jUDDI and needs to
- be at the head of the classpath. Both juddi.properties and
- jbossesb-properties.xml are used when the service first
- boots up for self-registration based upon the
- service-category and service-name found in the
- esb-config.xml file.
-
- * jndi.properties - needed primarily for
- quickstart.test.SendJMSMessage that is fired by ant runtest.
-
- * log4j.xml - needed to configure log4J used by both the
- quickstart and the ESB itself. A listener needs a place to
- log.
-
- * src\quickstart\staticrouter\test\SendJMSMessage.java -
- shoots in the string passed in via the command line or in
- this case the arg attribute in the ant runtest task.
-
- * src\quickstart\staticrouter\test\ReceiveJMSMessage.java -
- reads the output queues and displays the messages.
-
- * build.xml - This quickstart implements the following tasks:
-
- * runtest - send message thru gateway listener in
- MyJMSListener directly to destination queue
-
- * the echoCP task is useful for making sure what you
- think is in your classpath is actually in your
- classpath Usage is: ant echoCP > myclasspath.txt
- This generates a file called myclasspath.txt which
- can be reviewed in a text editor
-
- * the classpath property pulls the
- jbossesb-properties.xml file and the
- juddi.properties file to the front of the list
-
\ No newline at end of file
Modified: labs/jbossesb/trunk/product/samples/quickstarts/fun_cbr/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/fun_cbr/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/fun_cbr/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,67 +1,57 @@
Overview:
=========
- This example demonstrates the dynamic hot reloading/redeploy capability of both the jbossesb.xml configuration and the rules associated with
- the CBR (Content-based Routing).
- The benefit of hot reloading means that the service does not have to come down in order to make a change. In addition, you can change the
- rules based upon current load situations scenarios. This example has three "teams" of order processors. All new orders that flow into
- the system are evaluated via the rules engine. These routing rules will determine which team receives the order for actually processing.
- In the case of the green team, the order is first transformed to a different format prior to routing.
- For standalone execution (running outside of an App Server) you will eventually need five (5) command windows running
- to execute this demonstration.
+ This example has three "teams" of order processors. All new orders that flow
+ into the system are evaluated via the rules engine. These routing rules will
+ determine which team receives the order for actually processing. In the case
+ of the green team, the order is first transformed to a different format prior
+ to routing.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-queues'.
- 1. In the first command window execute "ant clean". This removes the build folder from the project.
- 3. In the first command window execute "ant compile" then "ant jar". These steps compile the Java sources and create the appropriate
- jar files. You should notice that their are two jar files for this example. The additional jar file is for the Rules files. If you
- review the build.xml you should see there is a task called "updateRules" that will rebuild this jar file individually. This is useful
- for testing the redeployment of Rules without bringing down the overall ESB.
- 3. Now, in the first command window, execute "ant" to bring up the ESB for this set of services.
- 4. In the command windows 2, 3 and 4 run "ant receiveBlue", "ant receiveRed" and "ant receiveGreen" respectively. These
- are simply JMS queue listeners that will simply display any messages they receive to their console windows. Think of these
- simple JMS receivers as actual customer service teams within an organization. The routing depends on the statusCode attribute
- in the SampleOrder.xml file.
- It would be relatively simple to modify this example to include a service (listener & action combination) to introduce "scoring"
- rules logic that sets the status code of the message prior to sending it on to the CBR.
- 5. In the fifth command window execute "ant runtest". This will take a copy of SampleOrder.xml and shoot it into the primary JMS
- queue for this sample - quickstart_Fun_CBR_Request_GW.
- Open the FunCBRRules-XPath.drl file and review the actual routing rules:
- rule "Red Routing Rule using XPATH"
- when
- xpathEquals "/Order/@statusCode", "1"
- then
- Log : "Red Team";
- Destination : "RedTeam:GoRed";
- end
- 6. Open the SampleOrder.xml file and modify the statusCode to equal 0 or 2 and re-execute "ant runtest" to see that it properly
- routes to the correct endpoint.
- 7. Open FunCBRRules-XPath.drl and change the routes to the following:
- Blue for statusCode="1"
- Red for statusCode="2"
- Green for statusCode="0"
- Note: If you are using the JBossIDE 2.0 there is a great JBoss Rules editor which provides syntax highlighting and correction assistance.
- 8. In the fifth command window execute "ant updateRules" and then "ant runtest". You should see that the routes associated with
- the message flow have dynamically changed.
- 9. Open the jbossesb.xml and insert the following actions to transform the inbound XML message to a POJO and then the POJO to a simple
- ASCII message in the Green Team's service. Make sure to inject the transformer before the notification action:
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. In a command terminal window in this folder ("Window2"), type
+ 'ant receiveBlue'.
+ 4. In a command terminal window in this folder ("Window3"), type
+ 'ant receiveRed'.
+ 5. In a command terminal window in this folder ("Window4"), type
+ 'ant receiveGreen'.
+ 6. Open another command terminal window in this folder ("Window5"), type
+ 'ant runtest'.
+ 7. Switch back to "Window1", "Window2", "Window3" and "Window4" to see the
+ output from the ESB
+ 8. When finished, interrupt the ESB and receivers using Ctrl-C.
+ 9. Undpeloy the JMS configuration, type 'ant undeploy-jms-dests'.
- <action name="transform"
- class="org.jboss.soa.esb.actions.converters.SmooksTransformer">
- <property name="from" value="DVDStore:OrderDispatchService" />
- <property name="from-type" value="text/xml:fullFillOrder" />
- <property name="to" value="DVDWarehouse_1:OrderHandlingService" />
- <property name="to-type" value="text/xml:shipOrder" />
- </action>
- <action name="convertPOJO2Message" class="org.jboss.soa.esb.dvdstore.DVDStoreAction/>
- <action name="displayAfterTransformer"
- class="org.jboss.soa.esb.samples.quickstart.funcbr.MyJMSListenerAction" process="displayMessage" />
+To Run '.esb' archive mode:
+===========================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. In a command terminal window in this folder ("Window2"), type
+ 'ant receiveBlue'.
+ 3. In a command terminal window in this folder ("Window3"), type
+ 'ant receiveRed'.
+ 4. In a command terminal window in this folder ("Window4"), type
+ 'ant receiveGreen'.
+ 5. In "Window1", type 'ant runtest'.
+ 6. Switch back to the Application Server console, "Window2", "Window3" and
+ "Window4" to see the output from the ESB
+ 7. When finished, interrupt the receivers using Ctrl-C.
+ 8. Undpeloy the esb archive, type 'ant undeploy'.
- 10. In the fifth command window, make sure to modify the SampleOrder.xml to change statusCode to 0 (or to whatever is appropriate
- per your routing rules) then execute "ant runtest" to see the transformed message in the Green Team's console.
-
+Things to Consider:
+===================
+ The routing depends on the statusCode attribute in the SampleOrder.xml file.
+ It would be relatively simple to modify this example to include a service
+ (listener & action combination) to introduce "scoring" rules logic that sets
+ the status code of the message prior to sending it on to the CBR.
+
+ Change the statusCode to select another destination
+ 0 - Blue
+ 1 - Red
+ 2 - Green
Modified: labs/jbossesb/trunk/product/samples/quickstarts/helloworld/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/helloworld/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/helloworld/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,77 +1,29 @@
Overview:
=========
- The purpose of the helloworld quickstart sample is to prove that the ESB is
- properly configured and happy. As well as to demonstrate the needed minimal
- files to make a basic ESB component execute.
+ The purpose of the helloworld quickstart sample is to prove that the ESB is
+ is properly configured and happy. As well as to demonstrate the needed
+ minimal files to make a basic ESB component execute.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch back to Application Server console to see the output from the ESB
-
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. You might review the build.xml file to see how it is setup.
- More details on the build.xml can be found later in this document. Shutdown
- the listener by simply using Ctrl-C in that window.
-
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" to shoot a JMS message
- into the listener which will then invoke the MyJMSListenerAction and display
- it to the console. You can modify the build.xml to change the phrase
- "Hello World" to something else and re-run "ant runtest".
-
-Project file descriptions:
-==========================
-
- jbossesb.xml:
- The JMS gateway and ESB configuration file. It is listening for JMS ObjectMessages or TextMessages
- at "queue/quickstart_helloworld_Request". Messages received at "quickstart_helloworld_Request" are
- converted bossesb-properties.xml. Also needed by jUDDI and needs to be at the head of the classpath.
- Both juddi.properties and jbossesb-properties.xml are used when the service first boots up for
- self-registration based upon the service-category and service-name found in the esb-config.xml file.
-
- jndi.properties:
- Needed primarily for org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage that is fired by ant runtest.
-
- log4j.xml:
- Needed to configure log4J used by both the quickstart and the ESB itself. A listener needs a place to log.
-
- src\quickstart\MyJMSListenerAction.java:
- The action class that is identified in the esb-config.xml file and is called whenever a message is received.
-
- src\quickstart\helloworld\test\SendJMSMessage.java:
- Shoots in the string passed in via the command line or in this case the arg attribute in the ant runtest task.
-
- src\quickstart\helloworld\test\SendEsbMessage.java:
- Shoots in the string passed in via the command line or in this case the arg atribute in the ant sendesb task.
- This demonstrates how to build an "ESB aware" client that can invoke an ESB service.
-
- build.xml:
- Targets and structure description:
- * the classpath property pulls the jbossesb-properties.xml file and the juddi.properties file to the
- front of the list
- * the echoCP task is useful for making sure what you think is in your classpath is actually in your classpath
- Usage is: ant echoCP > myclasspath.txt
- This generates a file called myclasspath.txt which can be reviewed in a text editor
- * the run task calls the Launcher passing in 3 arguments the most important are the esb-config.xml and
- esb-config-gateway.xml files
- * the runtest task calls the org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage class and passes in an argument representing
- the string-based message to be pused into the queue the gateway is listening on. Note: SendJMSMessage
- contains a hard-coded queue name.
-
-
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,82 +1,69 @@
Overview:
=========
- The purpose of the helloworld_action quickstart sample is to show the use of
- multiple action invocations from a single configuration. You can use
- a single Action class and make multiple method calls or use multiple Action
- classes.
+ The purpose of the helloworld_action quickstart sample is to show the use of
+ multiple action invocations from a single configuration. You can use
+ a single Action class and make multiple method calls or use multiple Action
+ classes.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
- 5. Shutdown the listener by simply using Ctrl-C in that window.
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch back to Application Server console to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
-To Run '.esb' archive mode:
-===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch back to Application Server console to see the output from the ESB
-
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. You might review the build.xml file to see how it is setup.
- More details on the build.xml can be found later in this document. Shutdown
- the listener by simply using Ctrl-C in that window.
-
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" to shoot a JMS message
- into the listener which will then invoke the MyJMSListenerAction and display
- it to the console. You can modify the build.xml to change the phrase
- "Hello World" to something else and re-run "ant runtest".
- After you have run the test and seen the activity on the console also use the a queue viewer
- like the one found in the JBoss JMX Console (if you are using JBossMQ) to
- see the modified message in the outbound queue: quickstart_helloworld_action_Response
-
Project file descriptions:
==========================
- Review the helloworld quickstart as the majority of this is similiar to
- that example
+ Review the helloworld quickstart as the majority of this is similiar to
+ that example
- MyJMSListenerAction.java:
- Has methods to display the inbound message, modify the message and to handle an
- exceptions which might be thrown in the action processing.
+ MyJMSListenerAction.java:
+ Has methods to display the inbound message, modify the message and to handle
+ any exceptions which might be thrown in the action processing.
- jbossesb.xml:
- Includes a special action (from JBoss ESB core) that is used
- to send a message out of the ESB back to the non-"ESB aware" world. The gateway
- looks for inbound messages on "quickstart_helloworld_action_Request" which was configured
- by the "esb-quickstart-service.xml" file.
- The notifier sends the modified message to "quickstart_helloworld_action_Response":
- <action name="notificationAction" class="org.jboss.soa.esb.actions.Notifier">
- <property name="okMethod" value="notifyOK" />
- <property name="notification-details">
- <NotificationList type="OK">
- <target class="NotifyConsole" />
- <target class="NotifyQueues">
- <queue jndiName="queue/quickstart_helloworld_action_Response">
- <messageProp name="quickstart" value="hello_world_action" />
- </queue>
- </target>
- </NotificationList>
- </property>
- </action>
+ jbossesb.xml:
+ Includes a special action (from JBoss ESB core) that is used
+ to send a message out of the ESB back to the non-"ESB aware" world. The
+ gateway looks for inbound messages on "quickstart_helloworld_action_Request"
+ which was configured by the "esb-quickstart-service.xml" file.
- An ESB action class must have a constructor that accepts a ConfigTree argument like the following:
- public MyJMSListenerAction(ConfigTree config) { _config = config; }
+ The notifier sends the modified message to
+ "quickstart_helloworld_action_Response":
+
+ <action name="notificationAction" class="org.jboss.soa.esb.actions.Notifier">
+ <property name="okMethod" value="notifyOK" />
+ <property name="notification-details">
+ <NotificationList type="OK">
+ <target class="NotifyConsole" />
+ <target class="NotifyQueues">
+ <queue jndiName="queue/quickstart_helloworld_action_Response">
+ <messageProp name="quickstart" value="hello_world_action" />
+ </queue>
+ </target>
+ </NotificationList>
+ </property>
+ </action>
+
+ An ESB action class must have a constructor that accepts a ConfigTree argument
+ like the following:
+ public MyJMSListenerAction(ConfigTree config) { _config = config; }
- A ConfigTree is an object holding any attributes associated with the action declaration in the jbossesb.xml
+ A ConfigTree is an object holding any attributes associated with the action
+ declaration in the jbossesb.xml
Modified: labs/jbossesb/trunk/product/samples/quickstarts/helloworld_db_registration/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/helloworld_db_registration/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/helloworld_db_registration/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,110 +1,44 @@
Overview:
=========
- This example assumes your jUDDI registry is running in Mysql and it connects
- directly to the database to register the component.
+ This example assumes your jUDDI registry is running in Mysql and it connects
+ directly to the database to register the component.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
+ Make sure that you have MySQL running before starting this quickstart.
+
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-queues'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
- 5. Shutdown the listener by simply using Ctrl-C in that window.
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
-To Run '.esb' archive mode:
-===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to Application Server console to see the output from the ESB
-
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. You might review the build.xml file to see how it is setup.
- More details on the build.xml can be found later in this document. Shutdown
- the listener by simply using Ctrl-C in that window.
-
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" to shoot a JMS message
- into the listener which will then invoke the MyJMSListenerAction and display
- it to the console. You can modify the build.xml to change the phrase
- "Hello World" to something else and re-run "ant runtest".
-
What to look for in this Quickstart:
====================================
- The magic of DB registration (as opposed to RMI or SOAP) is in the jbossesb-properties.xml and the
- significant lines are marked with a **
- <properties name="registry">
- <property name="org.jboss.soa.esb.registry.queryManagerURI"
- ** value="org.apache.juddi.registry.local.InquiryService#inquire"/>
- <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI"
- ** value="org.apache.juddi.registry.local.PublishService#publish"/>
- <property name="org.jboss.soa.esb.registry.implementationClass"
- value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/>
- <property name="org.jboss.soa.esb.registry.factoryClass"
- value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
- <property name="org.jboss.soa.esb.registry.user" value="jbossesb"/>
- <property name="org.jboss.soa.esb.registry.password" value="password"/>
- <!-- the following parameter is scout specific to set the type of
- communication between scout and the UDDI (embedded, rmi, soap) -->
- <property name="org.jboss.soa.esb.scout.proxy.transportClass"
- ** value="org.apache.ws.scout.transport.LocalTransport"/>
- </properties>
-
-Project file descriptions:
-==========================
-
- esb-config.xml:
- The ESB listener configuration file
-
- esb-config-gateway.xml:
- The JMS gateway configuration file. It is listening for JMS ObjectMessages or TextMessages
- at "queue/quickstart_helloworld_Request"
-
- juddi.properties:
- Configures jUDDI, needs to be at the head of the classpath
-
- jbossesb-properties.xml:
- Also needed by jUDDI and needs to be at the head of the classpath. Both juddi.properties and
- jbossesb-properties.xml are used when the service first boots up for self-registration based upon the
- service-category and service-name found in the esb-config.xml file.
-
- jndi.properties:
- Needed primarily for org.jboss.soa.esb.samples.quickstart.helloworlddbregistration.test.SendJMSMessage that is fired by ant runtest.
-
- log4j.xml:
- Needed to configure log4J used by both the quickstart and the ESB itself. A listener needs a place to log.
-
- src\quickstart\Launcher.java:
- Called by ant "run" target with 3 arguments. The most important arguments being the locations of
- the esb-config.xml and esb-config-gateway.xml files. The Launcher starts the gateway and esb listener
- threads and then waits indefinitely.
-
- src\quickstart\MyJMSListenerAction.java:
- The action class that is identified in the esb-config.xml file and is called whenever a message is received.
-
- src\quickstart\test\SendJMSMessage.java:
- Shoots in the string passed in via the command line or in this case the arg attribute in the ant runtest task.
-
- lib\mysql-connector-java-3.1.12-bin.jar:
- The listener must register itself when it boots up therefore it needs access to the MySQL environment where
- jUDDI is living. This works in conjunction with juddi.properties.
-
- build.xml:
- * the classpath property pulls the jbossesb-properties.xml file and the juddi.properties file to the
- front of the list
- * the echoCP task is useful for making sure what you think is in your classpath is actually in your classpath
- Usage is: ant echoCP > myclasspath.txt
- This generates a file called myclasspath.txt which can be reviewed in a text editor
- * the run task calls the Launcher passing in 3 arguments the most important are the esb-config.xml and
- esb-config-gateway.xml files
- * the runtest task calls the org.jboss.soa.esb.samples.quickstart.helloworlddbregistration.test.SendJMSMessage class and passes in an argument representing
- the string-based message to be pused into the queue the gateway is listening on. Note: SendJMSMessage
- contains a hard-coded queue name.
-
-
+ The magic of DB registration (as opposed to RMI or SOAP) is in the
+ jbossesb-properties.xml and the significant lines are marked with a **
+
+ <properties name="registry">
+ <property name="org.jboss.soa.esb.registry.queryManagerURI"
+ ** value="org.apache.juddi.registry.local.InquiryService#inquire"/>
+ <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI"
+ ** value="org.apache.juddi.registry.local.PublishService#publish"/>
+ <property name="org.jboss.soa.esb.registry.implementationClass"
+ value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/>
+ <property name="org.jboss.soa.esb.registry.factoryClass"
+ value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
+ <property name="org.jboss.soa.esb.registry.user" value="jbossesb"/>
+ <property name="org.jboss.soa.esb.registry.password" value="password"/>
+ <!-- the following parameter is scout specific to set the type of
+ communication between scout and the UDDI (embedded, rmi, soap) -->
+ <property name="org.jboss.soa.esb.scout.proxy.transportClass"
+ ** value="org.apache.ws.scout.transport.LocalTransport"/>
+ </properties>
Modified: labs/jbossesb/trunk/product/samples/quickstarts/helloworld_file_action/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/helloworld_file_action/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/helloworld_file_action/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,59 +1,56 @@
Overview:
=========
- This is a basic example of using the File gateway feature of the JBoss ESB
- Files that are found in a particular directory with a particular
- extension are sent to a JMS queue with actions for processing.
+ This is a basic example of using the File gateway feature of the JBoss ESB.
+ Files that are found in a particular directory with a particular extension
+ are sent to a JMS queue with actions for processing.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
-
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
+
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-queues'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-queues'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to Application Server console to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
- 'run' target description:
- Start the listeners. You might review the build.xml file to see how it is setup.
- Shutdown the listener by simply using Ctrl-C in that window.
-
- 'runtest' target description:
- This will create a new file called "MyInput.dat" in the directory "build/dirs/input"
- with the contents "Hello World In A File"
- You can modify the build.xml to change the phrase "Hello World" to something else
- and re-run "ant runtest".
-
What to look at in this Quickstart:
===================================
- This example demonstrates the use of a file gateway that by default loads the file
- and pushes into a JMS message queue. What follows is a more detailed discussion on the
- file gateway:
-
- * directory - the directory to be monitored for input file messages
- * input-suffix - the file extension to be monitored, other files will be ignored
- * work-suffix - the file extension that is used while the file is "in process" by the
- ESB. The file is considered to be "in process" while the gateway is passing it into
- the ESB listener/service (in this case JMS queue).
- * post-delete - "true" or "false". The file can be removed once has been successfully
- processed.
- * post-directory - The place where the "processed" file ends up assuming no errors
- and assuming post-delete="false"
- * post-suffix - The file extension that is used to mark the file as "completed"
- * error-delete - "true" or "false". If there is an internal error and the file fails to
- be loaded by the ESB, delete it.
- * error-directory - The place to drop any file that fails to be uploaded/processed
- * error-suffix - The file extension that is used to mark a file has had an internal error.
- Note: Error processing in this case means the file failed to pass through the gateway
- and into the waiting queue.
-
-
+ This example demonstrates the use of a file gateway that by default loads the
+ file and pushes into a JMS message queue. What follows is a more detailed
+ discussion on the file gateway:
+
+ * directory - the directory to be monitored for input file messages
+ * input-suffix - the file extension to be monitored, other files will be
+ ignored
+ * work-suffix - the file extension that is used while the file is "in process"
+ by the ESB. The file is considered to be "in process" while the gateway is
+ passing it into the ESB listener/service (in this case JMS queue).
+ * post-delete - "true" or "false". The file can be removed once has been
+ successfully processed.
+ * post-directory - The place where the "processed" file ends up assuming no
+ errors and assuming post-delete="false"
+ * post-suffix - The file extension that is used to mark the file as
+ "completed".
+ * error-delete - "true" or "false". If there is an internal error and the file
+ fails to be loaded by the ESB, delete it.
+ * error-directory - The place to drop any file that fails to be
+ uploaded/processed.
+ * error-suffix - The file extension that is used to mark a file has had an
+ internal error.
+ Note: Error processing in this case means the file failed to pass through
+ the gateway and into the waiting queue.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/helloworld_ftp_action/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/helloworld_ftp_action/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/helloworld_ftp_action/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,110 +1,96 @@
Overview:
=========
- This is a very basic example that demonstrates how to configure the FTP gateway
- so that it picks up messages from an ftp server, routes them through a JMS queue
- and finally to your action class for processing.
-
+ This is a very basic example that demonstrates how to configure the FTP
+ gateway so that it picks up messages from an ftp server, routes them through
+ a JMS queue and finally to your action class for processing.
+
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
-Before Running:
-===============
- 1. Make sure the you have set the jboss.ftp properties in either install/deployment.properties
- or in samples/quickstarts/conf/quickstarts.properties.
- 2. Make sure you have read/write access to an FTP server. Write access is required
- so that a file can be marked as "completed" (or just deleted) and not reprocessed
- again and again. Write access is not needed for the read-only version.
+ Make sure that the quickstarts.properties file contains the configuration
+ information for the FTP hostname, user, password and base directory.
+ Make sure that you have write access to the FTP server.
+
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB. You should see the file contents
- displayed in the listener window
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run standalone mode readonly configuration:
==============================================
- 1. In a command terminal window in this folder ("Window1"), type 'ant run-readonly'.
- 1. In another command terminal window in this folder ("Window2"), type 'ant run-readonly'.
- 2. Open another command terminal window in this folder ("Window3"), type 'ant runtest'.
- 3. You should see the file contents displayed in the one of the listener windows.
- Log onto the ftpserver and see that the file has not been renamed.
- 4. Examine the jboss-esb-readonly-unfiltered.xml file and specifically this ftp-listener
- section:
- <property name="remoteFileSystemStrategy-configFile" value="./ftpfile-cache-config.xml"/>
- <property name="remoteFileSystemStrategy-cacheListener" value="org.jboss.soa.esb.listeners.gateway.remotestrategies.cache.DeleteOnEvictTreeCacheListener"/>
- Setting the deleteOnEviction to true will cause the file name to be deleted from the
- cacheloader. You can set the eviction time in ftpfile-cache-config.xml:
- <region name="/ftp/cache">
- <attribute name="maxNodes">5000</attribute>
- <attribute name="timeToLiveSeconds">20</attribute>
- <attribute name="maxAgeSeconds">20</attribute>
- </region>
- This will cause the filename to be deleted every 20 seconds. Such as short period is only
- for testing and a more realistic interval could perhaps be every day or so.
+ 1. In a command terminal window in this folder ("Window1"), type
+ 'ant deploy-jms-dests'.
+ 1. In a command terminal window in this folder ("Window2"), type
+ 'ant run-readonly'.
+ 2. In another command terminal window in this folder ("Window3"), type
+ 'ant run-readonly'.
+ 3. In "Window1", type 'ant runtest'.
+ 4. You should see the file contents displayed in the one of the listener
+ windows.
+ Log onto the ftpserver and see that the file has not been renamed.
+ 5. Examine the jboss-esb-readonly-unfiltered.xml file and specifically this
+ ftp-listener section:
-To Run as a .esb archive:
-=========================
- 1. In a command terminal window in the quickstart folder type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in the quickstart folder type 'ant deploy'.
- 3. In a command terminal window in the quickstart folder type 'ant runtest'.
+ <property name="remoteFileSystemStrategy-configFile"
+ value="./ftpfile-cache-config.xml"/>
+ <property name="remoteFileSystemStrategy-cacheListener"
+ value="org.jboss.soa.esb.listeners.gateway.remotestrategies.cache.DeleteOnEvictTreeCacheListener"/>
-To Run as a .esb archive readonly version:
-==========================================
- 1. In a command terminal window in the quickstart folder type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in the quickstart folder type 'ant deploy-readonly'.
- 3. In a command terminal window in the quickstart folder type 'ant runtest'.
-
-
-What to consider in this Quickstart:
-===================================
- 1) The FTP configuration has been initialised in ../conf/quickstarts.properties
+ Setting the deleteOnEviction to true will cause the file name to be deleted
+ from the cacheloader. You can set the eviction time in
+ ftpfile-cache-config.xml:
- 2) The FTP directory is accessable and can be written to as the "in process"
- and "completed" files are renamed accordingly.
-
- If you do not have write access you will receive an error that looks something like the
- following:
- [java] 20:41:36,625 ERROR [Thread-5][AbstractFileGateway] Problems renaming
- file new_file.dat to new_file.dat.esbWorking
+ <region name="/ftp/cache">
+ <attribute name="maxNodes">5000</attribute>
+ <attribute name="timeToLiveSeconds">20</attribute>
+ <attribute name="maxAgeSeconds">20</attribute>
+ </region>
- 3) Running the read-only version:
- Note that the database used by the cacheloader is hypersonic and it is an inmemory database. This means that if
- you close all the ESBs running('ant run-readonly') windows all files will be retrieved once
- more. This would not be the case with a persistent database.
+ This will cause the filename to be deleted every 20 seconds. Such as short
+ period is only for testing and a more realistic interval could perhaps be
+ every day or so.
-Project file descriptions:
-==========================
+To Run '.esb' archive mode:
+===========================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
- * jboss-esb-unfiltered.xml - the jboss-esb configuration file before it is filtered by Ant
- to add the proper values for the remote ftp server. Ant will generate a file name jboss-esb.xml.
+To Run as a .esb archive readonly version:
+==========================================
+ 1. In a command terminal window in this folder ("Window1"), type
+ 'ant deploy-readonly'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
+
+What to consider in this Quickstart:
+===================================
+ 1. The FTP configuration has been initialised in
+ ../conf/quickstarts.properties
- * jboss-esb-readonly-unfiltered.xml - same as the file above but configured for a readonly ftp server.
- Ant will generate an file named jboss-esb-XX.xml. The reason for this is that if two standalone
- instances of the ESB are started in the same directory and use the same config file they will
- interfere with each other on startup. The one already started will think that it file as changed.
- Just run 'ant clean' to get rid of all the generated files.
+ 2. The FTP directory is accessable and can be written to as the "in process"
+ and "completed" files are renamed accordingly.
+
+ If you do not have write access you will receive an error that looks
+ something like the following:
+ [java] 20:41:36,625 ERROR [Thread-5][AbstractFileGateway] Problems
+ renaming file new_file.dat to new_file.dat.esbWorking
- * ftpfile-cache-config.xml - JBossTreeCache configuration file used with the readonly version.
-
- * jbossesb-properties.xml - also needed by jUDDI and needs to be at the head of the classpath.
- Both juddi.properties and jbossesb-properties.xml are used when the service first
- boots up for self-registration based upon the service-category and
- service-name found in the esb-config.xml file.
-
- * jndi.properties - needed primarily for
- quickstart.test.SendJMSMessage that is fired by ant runtest.
-
- * log4j.xml - needed to configure log4J used by both the
- quickstart and the ESB itself. A listener needs a place to
- log.
-
- * src/org/jboss/soa/esb/samples/quickstarts/helloworldftpaction/MyAction.java -
- Action that prints the message received to sysout
-
- * src/org/jboss/soa/esb/samples/quickstarts/helloworldftpaction/test/CreateTestFile.java -
- Creates a test file on the ftpserver. This is what triggers the ftplistener
-
+ 3. Running the read-only version:
+ Note that the database used by the cacheloader is hypersonic and it is an
+ inmemory database. This means that if you close all the ESBs
+ running('ant run-readonly') windows all files will be retrieved once more.
+ This would not be the case with a persistent database.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/helloworld_hibernate_action/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/helloworld_hibernate_action/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/helloworld_hibernate_action/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,57 +1,40 @@
Overview:
=========
-This Quickstart requires jboss-4.2.0.GA.
+ This is a demonstration of a Hibernate listener. This test is configured
+ to use a mysql database running on localhost (see jbossesb.xml). This
+ quickstart builds an ear containing both an .esb and a .war. The .war
+ has a series of .jsps which demonstrate insert/delete/load/update.
-This is a demonstration of a Hibernate listener. This test is configured
-to use a mysql database running on localhost (see jbossesb.xml). This
-quickstart builds an ear containing both an .esb and a .war. The .war
-has a series of .jsps which demonstrate insert/delete/load/update.
+ If you browse the .war and insert items, you can see the Hibernate entities
+ that you load and delete items, you can watch the Hibernate entities sent
+ in messages to JBoss's console.
-If you browse the .war and insert items, you can see the Hibernate entities
-that you load and delete items, you can watch the Hibernate entities sent
-in messages to JBoss's console.
+ Here are the Hibernate Interceptor events which can be listened for:
+ onCollectionRemove
+ onCollectionUpdate
+ onDelete
+ onFlushDirty
+ onLoad
+ onSave
-Here are the Hibernate Interceptor events which can be listened for:
-onCollectionRemove
-onCollectionUpdate
-onDelete
-onFlushDirty
-onLoad
-onSave
+ See the sample jboss-esb.xml for how these are used within a
+ <hibernate-message-filter>.
-See the sample jboss-esb.xml for how these are used within a
-<hibernate-message-filter>.
-
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
-Before Running:
-===============
- 1. install mysql if you have not already.
- 2. start the mysql database
- 3. edit hibernate.cfg.xml with the user, password, and connection settings to be used with mysql
- 4. ant createdb
+ Make sure that you have MySQL running before starting this quickstart. Once
+ it is running, execute 'ant createdb' to create the database.
+ Note, this quickstart requires an ESB embedded in JBoss AS 4.2.0.GA.
+ Installation instructions can be found in the install/readme.txt.
To Run .ear mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy'.
- 2. Assuming that your appserver is running tomcat on port 8080, Browse to http://localhost:8080/hibernateaction/list.jsp
- 3. Watch the events in the JBoss appserver console.
-
-Project file descriptions:
-==========================
- jbossesb.xml:
- The JMS gateway and ESB configuration file. It is listening for new rows in the gateway table.
-
- hibernate.cfg.xml:
- The Hibernate configuration file.
-
- create.sql:
- Creates the database and tables.
-
- lib:
- Additional jars needed (ex mysql JDBC driver)
-
+ 1. In a command terminal window in the quickstart folder type 'ant deploy'.
+ 2. Assuming that your appserver is running tomcat on port 8080, Browse to
+ http://localhost:8080/hibernateaction/index.jsp
+ 3. Watch the events in the JBoss appserver console.
+ 4. To undeploy the application, type 'ant undeploy'
Modified: labs/jbossesb/trunk/product/samples/quickstarts/helloworld_sql_action/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/helloworld_sql_action/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/helloworld_sql_action/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,62 +1,27 @@
Overview:
=========
- This quickstart demonstrates an SQL listener. This test is configured to use a mysql database
- running in localhost (see jbossesb.xml).
+ This quickstart demonstrates an SQL listener.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
-Before Running:
-===============
- 1. install mysql if you have not already.
- 2. start the mysql database
- 3. edit mysql.proprties with the user and password to be used with mysql
- 4. ant createdb
+ Make sure that you have MySQL running before starting this quickstart. Once
+ it is running, execute 'ant createdb' to create the database.
-
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-queues'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to "Window1" to see the output from the ESB
+ 4. When finished, interrupt the ESB using Ctrl-C.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-queues'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch to Application Server console to see the output from the ESB
-
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. You might review the build.xml file to see how it is setup.
- More details on the build.xml can be found later in this document. Shutdown
- the listener by simply using Ctrl-C in that window.
-
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" will insert values into
- the database by executing the populate.sql database script. You can modify this
- file and observe the change.
-
- You can also configure other preferences by modifying the following build.xml targets:
- dropdb, createdb (that runs the create.sql),purgetable and runtest (that runs the populate.sql)
-
- There's a helpful target (select) to see status of table polled by gateway
-
-Project file descriptions:
-==========================
- jbossesb.xml:
- The JMS gateway and ESB configuration file. It is listening for new rows in the gateway table.
-
- create.sql:
- Will create the database and tables.
-
- populate.sql:
- This is what gets inserted into the database when the runtest target is run.
-
- lib:
- Additional jars needed. For example jar for database drivers
-
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
Added: labs/jbossesb/trunk/product/samples/quickstarts/jbpm_simple1/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/jbpm_simple1/readme.txt (rev 0)
+++ labs/jbossesb/trunk/product/samples/quickstarts/jbpm_simple1/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -0,0 +1,25 @@
+Overview:
+=========
+ The purpose of the jbpm_simple quickstart sample is to demonstrate the
+ integration of a process definition into JBoss ESB.
+
+Running this quickstart:
+========================
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
+
+To Run standalone mode:
+=======================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to "Window1" to see the output from the ESB
+ 4. When finished, interrupt the ESB using Ctrl-C.
+
+To Run '.esb' archive mode:
+===========================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
\ No newline at end of file
Property changes on: labs/jbossesb/trunk/product/samples/quickstarts/jbpm_simple1/readme.txt
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Name: svn:eol-style
+ native
Modified: labs/jbossesb/trunk/product/samples/quickstarts/messagefilter/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/messagefilter/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/messagefilter/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,88 +1,41 @@
Overview:
=========
- The purpose of the messagefilter quickstart sample is to show how to filter
- a messag based on content. Here we pass in an Order object and the FilterRules
- parse this object to looks for the quantity. If the quantity does not meet
- the threshold of 10, then the message is filter out. On the console you should see:
-
- [STDOUT] 9 Does not make the threshold
-
- In the build.xml you can change the default argument from '9' to '10' to see
-
- [STDOUT] 10 Makes the threshold
-
- In this case the message will get forwarded to the DemoService (service-category="Test" service-name="NextService")
- which prints out the message to the console.
-
+ The purpose of the messagefilter quickstart sample is to show how to filter
+ a messag based on content. Here we pass in an Order object and the FilterRules
+ parse this object to looks for the quantity. If the quantity does not meet
+ the threshold of 10, then the message is filter out. On the console you should
+ see:
+
+ [STDOUT] 9 Does not make the threshold
+
+ In the build.xml you can change the default argument from '9' to '10' to see
+
+ [STDOUT] 10 Makes the threshold
+
+ In this case the message will get forwarded to the DemoService
+ (service-category="Test" service-name="NextService") which prints out the
+ message to the console.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to Application Server console to see the output from the ESB
-
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. You might review the build.xml file to see how it is setup.
- More details on the build.xml can be found later in this document. Shutdown
- the listener by simply using Ctrl-C in that window.
-
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" to shoot a JMS message
- into the listener which will then invoke the MyJMSListenerAction and display
- it to the console. You can modify the build.xml to change the phrase
- "Hello World" to something else and re-run "ant runtest".
-
-Project file descriptions:
-==========================
-
- jbossesb.xml:
- The JMS gateway and ESB configuration file. It is listening for JMS ObjectMessages or TextMessages
- at "queue/quickstart_messagestore_Request". Messages received at "quickstart_messagestore_Request" are
- converted jbossesb-properties.xml. Also needed by jUDDI and needs to be at the head of the classpath.
- The jbossesb-properties.xml is used when the service first boots up for
- self-registration based upon the service-category and service-name found in the esb-config.xml file.
-
- jndi.properties:
- Needed primarily for org.jboss.soa.esb.samples.quickstart.messagestore.test.SendJMSMessage that is fired by ant runtest.
-
- log4j.xml:
- Needed to configure log4J used by both the quickstart and the ESB itself. A listener needs a place to log.
-
- src\quickstart\CheckMessageStoreAction.java:
- The action class that is identified in the esb-config.xml file and is called whenever a message is received.
-
- src\quickstart\helloworld\test\SendJMSMessage.java:
- Shoots in the string passed in via the command line or in this case the arg attribute in the ant runtest task.
-
- src\quickstart\helloworld\test\SendEsbMessage.java:
- Shoots in the string passed in via the command line or in this case the arg atribute in the ant sendesb task.
- This demonstrates how to build an "ESB aware" client that can invoke an ESB service.
-
- build.xml:
- Targets and structure description:
- * the classpath property pulls the jbossesb-properties.xml file to the
- front of the list
- * the echoCP task is useful for making sure what you think is in your classpath is actually in your classpath
- Usage is: ant echoCP > myclasspath.txt
- This generates a file called myclasspath.txt which can be reviewed in a text editor
- * the run task calls the Launcher passing in 3 arguments the most important are the esb-config.xml and
- esb-config-gateway.xml files
- * the runtest task calls the org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage class and passes in an argument representing
- the string-based message to be pused into the queue the gateway is listening on. Note: SendJMSMessage
- contains a hard-coded queue name.
-
-
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/messagestore/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/messagestore/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/messagestore/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,86 +1,57 @@
Overview:
=========
- The purpose of the messagestore quickstart sample is to show how to store
- a message in the MessageStore. The only interesting piece of configuration
- is:
-
- <!-- Add a copy of the message to the message store under categorization 'test' -->
- <action name="PersistAction" class="org.jboss.soa.esb.actions.MessagePersister" >
- <property name="classfication" value="test"/>
- <property name="message-store-class" value="org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl"/>
- </action>
-
- Which causes a message to be saved in the DB messageStore under the categorization 'test'. Tooling
- will be added to inspect the messageStore.
+ The purpose of the messagestore quickstart sample is to show how to store
+ a message in the MessageStore. The only interesting piece of configuration
+ is:
+ <!-- Add a copy of the message to the message store under categorization
+ 'test' -->
+ <action name="PersistAction" class="org.jboss.soa.esb.actions.MessagePersister" >
+ <property name="classfication" value="test"/>
+ <property name="message-store-class"
+ value="org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl"
+ />
+ </action>
+
+ Which causes a message to be saved in the DB messageStore under the
+ categorization 'test'. Tooling will be added to inspect the messageStore.
+
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch back to Application Server console to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. You might review the build.xml file to see how it is setup.
- More details on the build.xml can be found later in this document. Shutdown
- the listener by simply using Ctrl-C in that window.
+What to look at in this Quickstart:
+===================================
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" to shoot a JMS message
- into the listener which will then invoke the MyJMSListenerAction and display
- it to the console. You can modify the build.xml to change the phrase
- "Hello World" to something else and re-run "ant runtest".
+ src\quickstart\CheckMessageStoreAction.java:
+ The action class that is identified in the esb-config.xml file and is called
+ whenever a message is received.
-Project file descriptions:
-==========================
+ src\quickstart\helloworld\test\SendJMSMessage.java:
+ Shoots in the string passed in via the command line or in this case the arg
+ attribute in the ant runtest task.
- jbossesb.xml:
- The JMS gateway and ESB configuration file. It is listening for JMS ObjectMessages or TextMessages
- at "queue/quickstart_messagestore_Request". Messages received at "quickstart_messagestore_Request" are
- converted jbossesb-properties.xml. Also needed by jUDDI and needs to be at the head of the classpath.
- The jbossesb-properties.xml is used when the service first boots up for
- self-registration based upon the service-category and service-name found in the esb-config.xml file.
-
- jndi.properties:
- Needed primarily for org.jboss.soa.esb.samples.quickstart.messagestore.test.SendJMSMessage that is fired by ant runtest.
-
- log4j.xml:
- Needed to configure log4J used by both the quickstart and the ESB itself. A listener needs a place to log.
-
- src\quickstart\CheckMessageStoreAction.java:
- The action class that is identified in the esb-config.xml file and is called whenever a message is received.
-
- src\quickstart\helloworld\test\SendJMSMessage.java:
- Shoots in the string passed in via the command line or in this case the arg attribute in the ant runtest task.
-
- src\quickstart\helloworld\test\SendEsbMessage.java:
- Shoots in the string passed in via the command line or in this case the arg atribute in the ant sendesb task.
- This demonstrates how to build an "ESB aware" client that can invoke an ESB service.
-
- build.xml:
- Targets and structure description:
- * the classpath property pulls the jbossesb-properties.xml file to the
- front of the list
- * the echoCP task is useful for making sure what you think is in your classpath is actually in your classpath
- Usage is: ant echoCP > myclasspath.txt
- This generates a file called myclasspath.txt which can be reviewed in a text editor
- * the run task calls the Launcher passing in 3 arguments the most important are the esb-config.xml and
- esb-config-gateway.xml files
- * the runtest task calls the org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage class and passes in an argument representing
- the string-based message to be pused into the queue the gateway is listening on. Note: SendJMSMessage
- contains a hard-coded queue name.
-
-
+ src\quickstart\helloworld\test\SendEsbMessage.java:
+ Shoots in the string passed in via the command line or in this case the arg
+ attribute in the ant sendesb task. This demonstrates how to build an "ESB
+ aware" client that can invoke an ESB service.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/more_action/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/more_action/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/more_action/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,77 +1,63 @@
Overview:
=========
- The purpose of the more_action quickstart example is to show different ways of using Action classes.
+ The purpose of the more_action quickstart example is to show different ways of
+ using Action classes.
- In the jbossesb.xml:
- <action class="org.jboss.soa.esb.samples.quickstart.moreaction.MyJMSListenerAction" process="displayMessage" exceptionMethod="exceptionHandler" />
- <action class="org.jboss.soa.esb.samples.quickstart.moreaction.MyJMSListenerAction" exceptionMethod="exceptionHandler" />
- <action class="org.jboss.soa.esb.samples.quickstart.moreaction.StatefulAction" process="methodOne,methodTwo,displayCount" exceptionMethod="exceptionHandler" />
- <action class="org.jboss.soa.esb.samples.quickstart.moreaction.CustomConfigAction" process="displayConfig"
- myStuff="rocks"
- moreStuff="rocks harder">
- <subElement1>Value of 1</subElement1>
- <subElement2>Value of 2</subElement2>
- <subElement3>Value of 3</subElement3>
- </action>
-
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-queues'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-queues'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to Application Server console to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
+
+Things to Consider:
+===================
+ jbossesb.xml:
+ <action class="org.jboss.soa.esb.samples.quickstart.moreaction.MyJMSListenerAction"
+ process="displayMessage" exceptionMethod="exceptionHandler" />
+ <action class="org.jboss.soa.esb.samples.quickstart.moreaction.MyJMSListenerAction"
+ exceptionMethod="exceptionHandler" />
+ <action class="org.jboss.soa.esb.samples.quickstart.moreaction.StatefulAction"
+ process="methodOne,methodTwo,displayCount"
+ exceptionMethod="exceptionHandler" />
+ <action class="org.jboss.soa.esb.samples.quickstart.moreaction.CustomConfigAction"
+ process="displayConfig" myStuff="rocks" moreStuff="rocks harder">
+ <subElement1>Value of 1</subElement1>
+ <subElement2>Value of 2</subElement2>
+ <subElement3>Value of 3</subElement3>
+ </action>
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. You might review the build.xml file to see how it is setup.
- More details on the build.xml can be found later in this document. Shutdown
- the listener by simply using Ctrl-C in that window.
+ The second MyJMSListenerAction doesn't have a "process" attribute. That means
+ JBoss ESB is looking for a method with the following signature:
+ public Message process(Message message) {
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" to shoot a JMS message
- into the listener which will then invoke the MyJMSListenerAction and display
- it to the console. You can modify the build.xml to change the phrase
- "Hello World" to something else and re-run "ant runtest".
+ The StatefulAction declaration has a process attribute that has a command
+ delimited list of method names. These methods will be called in the order in
+ which they appear in the list. In addition, the StatefulAction class is only
+ instantiated one time and all method calls are executed against the same
+ instance. When you execute this example you'll be able to see that the cnt
+ maintains its state between method calls. If you would like to see the
+ alternative of calling each method with a new instance of StatefulAction
+ review the esb-config.xml.backup file that lists all the actions individually.
-Project file descriptions:
-==========================
- jbossesb.xml:
- <action class="org.jboss.soa.esb.samples.quickstart.moreaction.MyJMSListenerAction" process="displayMessage" exceptionMethod="exceptionHandler" />
- <action class="org.jboss.soa.esb.samples.quickstart.moreaction.MyJMSListenerAction" exceptionMethod="exceptionHandler" />
- <action class="org.jboss.soa.esb.samples.quickstart.moreaction.StatefulAction" process="methodOne,methodTwo,displayCount" exceptionMethod="exceptionHandler" />
- <action class="org.jboss.soa.esb.samples.quickstart.moreaction.CustomConfigAction" process="displayConfig"
- myStuff="rocks"
- moreStuff="rocks harder">
- <subElement1>Value of 1</subElement1>
- <subElement2>Value of 2</subElement2>
- <subElement3>Value of 3</subElement3>
- </action>
-
- The second MyJMSListenerAction doesn't have a "process" attribute. That means JBoss ESB is looking for a
- method with the following signature:
- public Message process(Message message) {
-
- The StatefulAction declaration has a process attribute that has a command delimited list of method names.
- These methods will be called in the order in which they appear in the list. In addition, the StatefulAction
- class is only instantiated one time and all method calls are executed against the same instance.
- When you execute this example you'll be able to see that the cnt maintains its state between method calls.
- If you would like to see the alternative of calling each method with a new instance of StatefulAction
- review the esb-config.xml.backup file that lists all the actions individually.
-
- The CustomConfigAction demonstrates how to access custom attributes on the main action tag and child
- elements of the action tag. As an action developer you have full access to these items as a means of
- configuration for your action thus making them more reusable between various projects.
-
-
+ The CustomConfigAction demonstrates how to access custom attributes on the
+ main action tag and child elements of the action tag. As an action developer
+ you have full access to these items as a means of configuration for your
+ action thus making them more reusable between various projects.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/native_client/build.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/native_client/build.xml 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/native_client/build.xml 2007-07-19 12:58:21 UTC (rev 13633)
@@ -47,4 +47,14 @@
<delete verbose="true" quiet="true"
file="${org.jboss.esb.server.deploy.dir}/${ant.project.name}.war"/>
</target>
+
+ <target name="display-instructions">
+ <echo message='${line.separator}******************' />
+ <echo>Quickstart deployed to target JBoss ESB/App Server at '${org.jboss.esb.server.deploy.dir}'.</echo>
+ <echo>1. Check your ESB Server console to make sure the deployment was executed without errors.</echo>
+ <echo>2. Use your favorite Web Service testing tool to test the webservice.</echo>
+ <echo>3. Check your ESB Server console again. The Quickstart should have produced some output.</echo>
+ <echo message='******************' />
+ </target>
+ </target>
</project>
Modified: labs/jbossesb/trunk/product/samples/quickstarts/native_client/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/native_client/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/native_client/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,52 +1,45 @@
Overview:
=========
- This example demonstrates how to develop and host a 181 Web Service on
- the JBoss Application Server. This Web Service is then used to make a
- synchronous call into the ESB via a "native client". This quickstart
- has no gateway, it uses a native "ESB Aware" listener and the client
- side code demonstrates how to use the MessageDeliveryAdapter.
-
+ This example demonstrates how to develop and host a 181 Web Service on the
+ JBoss Application Server. This Web Service is then used to make a synchronous
+ call into the ESB via a "native client". This quickstart has no gateway, it
+ uses a native "ESB Aware" listener and the client side code demonstrates how
+ to use the MessageDeliveryAdapter.
-Before Running:
-===============
-1. Update the "org.jboss.esb.server.home" property in the quickstarts.properties
- file in "../".
-2. Make sure the jbossesb.sar is deployed on your JBoss Application Server.
- In the ESB "install" folder update deployment.properties and then run "ant".
- This example does require you to use a version for 4.0.4+ with the EJB3 profile.
- It was most recently tested on App Server 4.2.0.GA with JBoss Messaging 1.3.0.GA
-3. Make sure the JBoss Application server is running.
+Running this quickstart:
+========================
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
+ Note, this quickstart requires an ESB and JBossWS installation into
+ JBoss AS 4.2.0.GA. Installation instructions for both can be found in the
+ install/readme.txt.
To Run:
=======
-1. In the first command window, execute "ant". This will compile the project, build
-the needed jars and deploy the WAR component to the Application Server. If you are
-monitoring the Application Server console you will see it hot deploy the WAR.
+ 1. In a command terminal window in the quickstart folder type 'ant deploy'.
-2. Using a browser, hit the following URL: "http://localhost:8080/jbossws".
+ 2. Using a browser, hit the following URL: "http://localhost:8080/jbossws".
-You should see something like the following:
-------------------------------------------------------------------------------------------
-| jboss.ws:context=Quickstart_native_client,endpoint=HelloWorldWS |
-| http://127.0.0.1:8080/Quickstart_native_client/HelloWorldWS?wsdl |
-------------------------------------------------------------------------------------------
+ You should see something like the following:
+ -----------------------------------------------------------------------
+ | jboss.ws:context=Quickstart_native_client,endpoint=HelloWorldWS |
+ | http://127.0.0.1:8080/Quickstart_native_client/HelloWorldWS?wsdl |
+ -----------------------------------------------------------------------
-3. Use for favorite Web Service testing tool to invoke the Web Service. A great one
-is called SoapUI at www.soapui.org.
+ 3. Use your favorite Web Service testing tool to invoke the Web Service. A
+ great one is called SoapUI at www.soapui.org.
-The ESB console should produce the following messages:
+ The ESB console should produce the following messages:
- [java] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
- [java] Body: Your Name
- [java] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
+ &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
+ Body: Your Name
+ &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
- [java] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
- [java] Body: Hello From ESB MyAction: Your Name
- [java] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
+ &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
+ Body: Hello From ESB MyAction: Your Name
+ &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
-This assumes you put in "Your Name" as the parameter in your WS client testing tool.
-
-
-
+ This assumes you put in "Your Name" as the parameter in your WS client
+ testing tool.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,5 +1,5 @@
-Please run 'ant help-quickstarts' from any quickstart project or read conf/readme.txt for
-information about running the quickstarts
+Please run 'ant help-quickstarts' from any quickstart project or read
+conf/readme.txt for information about running the quickstarts
The purpose of the quickstart samples is to illustrate various JBoss ESB product
features and general "how tos".
@@ -8,82 +8,80 @@
improving on the ones contained here simply post on the JBoss ESB User Forum
with "quickstart" in the subject line and a description of your thoughts.
-Each quickstart has its own readme.txt file that should be reviewed carefully. This can
-also be displayed by running 'ant help'.
+Each quickstart has its own readme.txt file that should be reviewed carefully.
+This can also be displayed by running 'ant help'.
Run 'ant -p' to see which targets are available for each quickstart.
-If you wish to run the quickstarts against a different server then the one that you deployed to when
-you ran 'ant deploy' in the product/install directory then you can modify this file to point to
-your specific version of JBoss AS.
+If you wish to run the quickstarts against a different server then the one that
+you deployed to when you ran 'ant deploy' in the product/install directory then
+you can modify this file to point to your specific version of JBoss AS.
org.jboss.esb.server.home=/opt/jboss/jboss405-GA
jboss.server=quickstarts
-#### TODO ####
-What needs to be here? Could we have most of this in conf/readme.txt ?
-
-
Prerequisites:
- Assumes you are comfortable working at the command line with Ant
-- Assumes you are running JBossMQ on JBoss Application Server. Other JMS
-solutions should work as well but the configuration files contained in the
-quickstarts are focused on JBossMQ.
-- Assumes you have properly configured the JBoss ESB Registry. A minimum configuration
-is included in the SAR deployment option. If you are using JBoss Application Server simply
-go into the "install" folder for the JBoss ESB. Modify the deployment.properties file and
-run "ant". Make sure to have the App Server turned "off" while this process is occuring.
-This process will add the "jbossesb.sar" to your JBoss Application Server as well
-as tweak the configuration.
-- Almost all of these examples use RMI-based registration. "helloworld_embedded_reg" deploys
-its own registry. "helloworld_db_registration" makes a client/server connection to
-the registry database. It assumes a MySQL DB holds the registry.
-- The file "esb-quickstart-service.xml" should be dropped into your "deploy"
-directory for your application server if you are using JBossMQ in JBossAS. This
-will setup the JMS queues for the quickstart samples.
+- Assumes you are running JBossMQ or JBossMessaging on JBoss Application Server.
+ Other JMS solutions should work as well but the configuration files contained
+ in the quickstarts are focused on those.
+- Assumes you have properly configured the JBoss ESB. If you are using JBoss
+ Application Server 4.2 simply go into the "install" folder for the JBoss ESB,
+ modify the deployment.properties file and run "ant". Make sure to have the
+ App Server turned "off" while this process is occuring.
+ This process will add the JBoss ESB artifacts to your JBoss Application
+ Server.
+- Almost all of these examples use RMI-based registration.
+ "helloworld_embedded_reg" deploys its own registry.
+ "helloworld_db_registration" makes a client/server connection to the registry
+ database. It assumes a MySQL DB holds the registry.
-The following is a brief outline of the various quickstarts. If this is your first
-time working with the JBoss ESB we recommend at least trying "helloworld", "helloworld_action"
-and "more_action".
+The following is a brief outline of some of the various quickstarts. If this is
+your first time working with the JBoss ESB we recommend at least trying
+"helloworld", "helloworld_action" and "more_action".
* helloworld - Uses a JMS Gateway combined with a Listener. If this is your
-first time using the JBoss ESB then start by exercising this simple
-"Hello World" example.
+ first time using the JBoss ESB then start by exercising this simple
+ "Hello World" example.
* helloworld_action - Builds on the concepts of the helloworld example but also
-show the use of multiple methods in a given action, how to "chain" action
-invocations into a particular sequence for a listener and how to respond
-(request/reply). This example uses the notification feature.
+ show the use of multiple methods in a given action, how to "chain" action
+ invocations into a particular sequence for a listener and how to respond
+ (request/reply). This example uses the notification feature.
-* more_action - demonstrates numerous tips & tricks to using the JBoss ESB actions. The first option
-shows what happens if you don't specify a "process" attribute. The second option illustrates how to
-make multiple method calls of a since action class instance. The third option shows you how to create
-your own custom attributes and child elements for the action tag.
+* more_action - demonstrates numerous tips & tricks to using the JBoss ESB
+ actions. The first option shows what happens if you don't specify a "process"
+ attribute. The second option illustrates how to make multiple method calls of
+ a since action class instance. The third option shows you how to create your
+ own custom attributes and child elements for the action tag.
-* transform_XML2POJO - Shows you how to setup a basic Smooks-based transformation to convert
-an XML document into Java POJOs.
+* transform_XML2POJO - Shows you how to setup a basic Smooks-based
+ transformation to convert an XML document into Java POJOs.
-* simple_cbr - demonstrates how to use JBoss Rules and the Content-based Router Action for determining
-how a particular message should follow through the various services. This example also shows you that you
-can setup multiple services in a single esb-config.xml.
+* simple_cbr - demonstrates how to use JBoss Rules and the Content-based Router
+ Action for determining how a particular message should follow through the
+ various services. This example also shows you that you can setup multiple
+ services in a single esb-config.xml.
-* fun_cbr - demonstrates the JBoss ESB's capability for hot deployment both of the CBR rules
-and the jbossesb.xml configuration file.
+* fun_cbr - demonstrates the JBoss ESB's capability for hot deployment both of
+ the CBR rules and the jbossesb.xml configuration file.
-* business_service - JBoss ESB actions are custom mediators. Their not specifically focused
-on business logic. This example demonstrates how to invoke an EJB3 stateless session
-bean (plus how to build a deploy an EJB3 SLSB on the JBoss AS). The SLSB is where
-your business logic can go. Feel free to use your favorite middle-tier component for
-handling business logic (e.g. business validation, persistence).
+* business_service - JBoss ESB actions are custom mediators. Their not
+ specifically focused on business logic. This example demonstrates how to
+ invoke an EJB3 stateless session bean (plus how to build a deploy an EJB3
+ SLSB on the JBoss AS). The SLSB is where your business logic can go. Feel
+ free to use your favorite middle-tier component for handling business logic
+ (e.g. business validation, persistence).
-* webservice_war1 - demonstrates how to create a 181 Web Service and use it as the
-front-end to the ESB. This also demonstrates a synchronous call into the bus service.
+* native_client - demonstrates how to create a 181 Web Service and use it as
+ the front-end to the ESB. This also demonstrates a synchronous call into the
+ bus service.
-* static_router - is primarily interesting because it is completely JMS-less. It uses
-FTP and File drop monitoring to move a message and send it out to multiple endpoints.
+* static_router - is primarily interesting because it is completely JMS-less.
+ It uses FTP and File drop monitoring to move a message and send it out to
+ multiple endpoints.
* aggregator - demonstrations how to use the Splitter/Aggregator capabilities of
-JBoss ESB. It uses the Transformation engine as well as the static-routing feature.
-It also demonstrations the use of multiple JVMs running different services.
-This is a fairly advanced demonstration.
-
-#### END TODO ####
+ JBoss ESB. It uses the Transformation engine as well as the static-routing
+ feature. It also demonstrations the use of multiple JVMs running different
+ services.
+ This is a fairly advanced demonstration.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/recipient_list/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/recipient_list/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/recipient_list/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,49 +1,65 @@
Overview:
=========
- The purpose of the recipient list quickstart sample is demonstrate
- the recipient list EIP pattern (as defined here:
- http://www.enterpriseintegrationpatterns.com/RecipientList.html) using a
- static router as implemented in org.jboss.soa.esb.actions.StaticRouter
- and a content based router (CBR) as implemented in
- org.jboss.soa.esb.actions.ContentBasedRouter
+ The purpose of the recipient list quickstart sample is demonstrate the
+ recipient list EIP pattern (as defined here:
+ http://www.enterpriseintegrationpatterns.com/RecipientList.html) using a
+ static router as implemented in org.jboss.soa.esb.actions.StaticRouter and a
+ content based router (CBR) as implemented in
+ org.jboss.soa.esb.actions.ContentBasedRouter
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the
- quickstarts and a more detailed descripton of the different ways to
- run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type ant receive-destination'
- 4. Open another command terminal window in this folder ("Window3"), type ant receive-destination1'
- 5. Open another command terminal window in this folder ("Window4"), type ant receive-destination2'
- 6. Open another command terminal window in this folder ("Window5"), type 'ant runtest-cbr'.
- (Note the other ant targets listed below.)
- 7. Switch back to "Window1", "Window2", "Window3", "Window4" to see the output from the ESB.
-
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. In a command terminal window in this folder ("Window2"), type
+ 'ant receive-destination'.
+ 4. In a command terminal window in this folder ("Window3"), type
+ 'ant receive-destination1'.
+ 5. In a command terminal window in this folder ("Window4"), type
+ 'ant receive-destination2'.
+ 6. Open another command terminal window in this folder ("Window5"), type
+ 'ant runtest-cbr'.
+ 7. Switch back to "Window1", "Window2", "Window3" and "Window4" to see the
+ output from the ESB
+ 8. When finished, interrupt the ESB and receivers using Ctrl-C and, in folder
+ "Window1", type 'ant undeploy-jms-dests'.
+
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder (Window2"), type ant receive-destination'
- 4. Open another command terminal window in this folder ("Window3"), type ant receive-destination1'
- 5. Open another command terminal window in this folder ("Window4"), type ant receive-destination2'
- 6. Open another command terminal window in this folder ("Window5"), type 'ant runtest-cbr'.
- (Note the other ant targets listed below.) You can modify the "totalAmount" element
- value in SampleOrder.xml to control the path that is followed thru the CBR. The valid
- ranges of values are less than 100 or greater than 99.99 - the behavior modeled is suggested
- in the EIP pattern definition, that being a credit account monitor where purchases below a
- certain cost are reviewed by a single credit agency while purchases above a certain cost
- are reviewed by that same credit agency and two additional credit agencies.
- 6. Switch back to "Window1", "Window2", "Window3", "Window4" to see the output from the ESB.
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. In a command terminal window in this folder ("Window2"), type
+ 'ant receive-destination'.
+ 3. In a command terminal window in this folder ("Window3"), type
+ 'ant receive-destination1'.
+ 4. In a command terminal window in this folder ("Window4"), type
+ 'ant receive-destination2'.
+ 5. Open another command terminal window in this folder ("Window5"), type
+ 'ant runtest'.
+ 6. Switch back to Application Server and receiver consoles to see the output
+ from the ESB
+ 7. When finished, interrupt the receivers using Ctrl-C and, in folder
+ "Window1", type 'ant undeploy'.
- The quickstart makes use of the queues illustrated (the queues are shown
- in boxes) in the following diagram. You might review the build.xml file to
- see how it is setup. More details on the build.xml can be found later in
- this document.
+Things to Consider:
+===================
+ You can modify the "totalAmount" element value in SampleOrder.xml to control
+ the path that is followed thru the CBR. The valid ranges of values are less
+ than 100 or greater than 99.99 - the behavior modeled is suggested in the
+ EIP pattern definition, that being a credit account monitor where purchases
+ below a certain cost are reviewed by a single credit agency while purchases
+ above a certain cost are reviewed by that same credit agency and two
+ additional credit agencies.
+
+ The quickstart makes use of the queues illustrated (the queues are shown
+ in boxes) in the following diagram. You might review the build.xml file to
+ see how it is setup. More details on the build.xml can be found later in
+ this document.
application initiated
|
@@ -64,90 +80,11 @@
|qsrecipientlist_2_Request|---> output above 99.99
---------------------------
-Project File Descriptions
-=========================
-
- * jbossesb.xml - the JMS gateway and ESB configuration file.
- * jbossesb-properties.xml - also needed by jUDDI and needs to
- be at the head of the classpath. Both juddi.properties and
- jbossesb-properties.xml are used when the service first
- boots up for self-registration based upon the
- service-category and service-name found in the
- esb-config.xml file.
-
- * jndi.properties - needed primarily for
- quickstart.test.SendJMSMessage that is fired by ant runtest.
-
- * log4j.xml - needed to configure log4J used by both the
- quickstart and the ESB itself. A listener needs a place to
- log.
-
- * src\quickstart\staticrouter\test\SendJMSMessage.java -
- shoots in the string passed in via the command line or in
- this case the arg attribute in the ant runtest task.
-
- * src\quickstart\staticrouter\test\SendTestJMSMessage.java -
- shoots in the string to the static router passed in via the
- command line or in this case the arg attribute in the ant
- static-router task.
-
- * src\quickstart\staticrouter\test\SendCBRJMSMessage.java -
- shoots in the string to the CBR router in the ant
- runtest-cbr task.
-
- * src\quickstart\staticrouter\test\ReceiveJMSMessage.java -
- reads the output queues and displays the messages.
-
- * MyESBRules-XPath.drl - JBoss Rules definition file
-
- * build.xml - This quickstart implements the following tasks:
-
- * runtest - send message thru gateway listener in
- MyJMSListener directly to destination queue
-
- * static-router - send message thru static router
- gateway in org.jboss.soa.esb.actions.StaticRouter
-
- * runtest-cbr - send message thru CBR router gateway
- in org.jboss.soa.esb.actions.ContentBasedRouter
-
- * config - copies the JBoss Rules file into
- /build/classes
-
- * quickstart-specific-deploys - creates the JBoss
- Rules jar file
-
- * the echoCP task is useful for making sure what you
- think is in your classpath is actually in your
- classpath Usage is: ant echoCP > myclasspath.txt
- This generates a file called myclasspath.txt which
- can be reviewed in a text editor
-
- In order to run the tests, you must first run these
- ant tasks - in this order:
-
- * ant compile
- * ant config
- * ant quickstart-specific-deploys
- * ant deploy
-
- This quickstart uses the queues called:
-
- * qsrecipientlist_static_router_Request - Where the
- message enters the static router
-
- * qsrecipientlist_regular_Request - The application
- destination for the message when the total is below
- the configured limit
-
- * qsrecipientlist_1_Request, qsrecipientlist_1_Request -
- The application destination for the message when the total is
- above the configured limit
-
- * qsrecipientlist_cbr_Request - Where the message enters
- the CBR router
-
- * the classpath property pulls the
- jbossesb-properties.xml file and the
- juddi.properties file to the front of the list
+ * build.xml - This quickstart implements the following additional targets:
+ * runtest - send message thru gateway listener in MyJMSListener directly to
+ destination queue
+ * static-router - send message thru static router gateway in
+ org.jboss.soa.esb.actions.StaticRouter
+ * runtest-cbr - send message thru CBR router gateway in
+ org.jboss.soa.esb.actions.ContentBasedRouter
Modified: labs/jbossesb/trunk/product/samples/quickstarts/scripting_groovy/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/scripting_groovy/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/scripting_groovy/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,24 +1,28 @@
Overview:
=========
- Simple quickstart demonstrating implementation of a Groovy scripted action using
- the GroovyActionProcessor.
+ Simple quickstart demonstrating implementation of a Groovy scripted action
+ using the GroovyActionProcessor.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-queues'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the Groovy action scripts.
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-queues'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to Application Server console to see the output from the ESB
-
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/simple_cbr/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/simple_cbr/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/simple_cbr/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,81 +1,52 @@
Overview:
=========
- The purpose of the simple_cbr quickstart is to demonstrate the Content Based Router in JBoss ESB.
+ The purpose of the simple_cbr quickstart is to demonstrate the Content Based
+ Router in JBoss ESB.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-queues'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. In a command terminal window in this folder ("Window2"), type 'ant receiveExpress'.
- 4. In a command terminal window in this folder ("Window3"), type 'ant receiveNormal'.
- 3. Open another command terminal window in this folder ("Window4"), type 'ant runtest'.
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. In a command terminal window in this folder ("Window2"), type
+ 'ant receiveExpress'.
+ 4. In a command terminal window in this folder ("Window3"), type
+ 'ant receiveNormal'.
+ 5. Open another command terminal window in this folder ("Window4"), type
+ 'ant runtest'.
+ 6. Switch back to "Window1", "Window2" and "Window3" to see the output fro
+ the ESB
+ 7. When finished, interrupt the ESB and receivers using Ctrl-C and, in folder
+ "Window1", type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-queues'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch back to Application Server console to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. In a command terminal window in this folder ("Window2"), type
+ 'ant receiveExpress'.
+ 3. In a command terminal window in this folder ("Window3"), type
+ 'ant receiveNormal'.
+ 4. Open another command terminal window in this folder ("Window4"), type
+ 'ant runtest'.
+ 5. Switch back to Application Server console, "Window2" and "Window3" to see
+ the output from the ESB
+ 6. When finished, interrupt the receivers using Ctrl-C and, in folder
+ "Window1", type 'ant undeploy'.
+
+Things to Consider:
+===================
+ - Use a text editor to change the "totalAmount" in the order above/below $50
+ and re-execute ant runtest to see the order flash up in the different
+ receivers.
+
+ <Order orderId="1" orderDate="Wed Nov 15 13:45:28 EST 2006" statusCode="0"
+ netAmount="59.97" totalAmount="64.92" tax="4.95">
-
- "ant run" :
- Starts the listeners
-
- "ant receiveExpress"
- In another command window, this process will wait for messages to hit the queue/CBRExpressFreeShippingAlert queue
-
- "ant receiveNormal"
- In another command window, this process will wait for messages to hit the queue/CBRNormalShippingAlert queue
-
- "ant runtest"
- In another command window, this process will pick up the SampleOrder.xml and shoot it into the
- queue/quickstart_simple_cbr_Request queue which is identified in the esb-config-gateway.xml
-
-
- Use a text editor to change the "totalAmount" in the order above/below $50 and re-execute ant runtest to
- see the order flash up in the different receivers.
- <Order orderId="1" orderDate="Wed Nov 15 13:45:28 EST 2006" statusCode="0"
- netAmount="59.97" totalAmount="64.92" tax="4.95">
-
- What follows are the highlights that uncover some of the magic associated with CBR:
- * src\services\rules\SimpleCBRRules-XPath.drl is a JBoss Rules ruleset that has simple logic that evaluates
- the totalAmount attribute of the SampleOrder.xml. Over $50 means Free Express shipping, Under $50 means
- Normal shipping.
-
-Project file descriptions:
-==========================
- src\services\rules\SimpleCBRRules.drl:
- Can be used for selecting a path based upon a piece of meta-data as opposed to the message content.
- It is not used in the example but provided anyway.
-
- src\quickstart\test\ReceiveJMSMessage.java:
- Has been modified to accept the queue to listen to from the command line (from build.xml)
-
- RouteExpressShipping.java:
- Simply pushes the message to the CBRExpressFreeShippingAlert queue
-
- RouteNormalShipping.java:
- Ssimply pushes the message to the CBRNormalShippingAlert queue
-
- build.xml
- Creates an additional jar file for the rules files. This jar file is also loaded into the classpath.
- <jar destfile="${build.dir}/${ant.project.name}_Rules.jar"
- basedir="${basedir}/src/services/rules" includes="*.*"/>
-
- jbossesb.xml
- Establishes 3 services. The first is the perform the CBR evaluation and has this action:
- ruleSet="SimpleCBRRules-XPath.drl"
- ruleLanguage="XPathLanguage.dsl"
- XPathLanguage.dsl lives in core\services\rules\XPathLanguage.dsl and ships as jbossesb-rules.jar
-
- SimpleCBRRules-XPath.drl:
- routes to the appropriate destination service via this command Destination : "express";
-
- In the jbossesb.xml the "express" destination is related to:
- "ExpressShipping" is the service-category (found in esb-config.xml)
- "ExpressShippingService" is the service-name (also found in the jbossesb.xml)
+ - SimpleCBRRules-XPath.drl is a JBoss Rules ruleset that has simple logic that
+ evaluates the totalAmount attribute of the SampleOrder.xml. Over $50 means
+ Free Express shipping, Under $50 means Normal shipping.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/spring_aop/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/spring_aop/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/spring_aop/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,80 +1,66 @@
Overview:
=========
- The purpose of the spring_aop quickstart sample is to show the use of Spring AOP.
- You can specify Spring bean XML definitions in jboss-esb.xml and lookup the beans
- in your Action class. Each Action loads a single Spring IoC container upon first spring bean
- invocation. Subsequent invocations will not load a new IoC container. Also, none of the Spring
- dependencies are included. You must manually add additional Spring dependency JARs to the classpath
- to create Spring beans that have special dependencies, like a DB connection pool.
+ The purpose of the spring_aop quickstart sample is to show the use of Spring
+ AOP. You can specify Spring bean XML definitions in jboss-esb.xml and lookup
+ the beans in your Action class. Each Action loads a single Spring IoC
+ container upon first spring bean invocation. Subsequent invocations will not
+ load a new IoC container. Also, none of the Spring dependencies are included.
+ You must manually add additional Spring dependency JARs to the classpath to
+ create Spring beans that have special dependencies, like a DB connection pool.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
- 5. Shutdown the listener by simply using Ctrl-C in that window.
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch back to Application Server console to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
+
+Things to Consider:
+===================
+ Review the helloworld quickstart as the majority of this is similiar to
+ that example
-To Run '.esb' archive mode:
-===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch back to Application Server console to see the output from the ESB
+ MySpringEnabledAction.java:
+ There is one action method called "sayHelloAopStyle". The method gets
+ triggered when a JMS message is sent. "sayHelloAopStyle" actually uses the
+ message payload to get the greeting, but the interceptor will change the
+ greeting.
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. You might review the build.xml file to see how it is setup.
- More details on the build.xml can be found later in this document. Shutdown
- the listener by simply using Ctrl-C in that window.
+ jboss-esb.xml
+ The method, "sayHelloAopStyle" uses a spring interceptor to change the
+ greeting message. Notice that the action does not have any println
+ statements, "MyInterceptor" is doing all of the console output work. The
+ interceptor is configured in spring-context.xml, not annotation style. You
+ can change the greeting in build.xml. The greeting is sent to the ESB via
+ JMS.
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" to shoot a JMS message
- into the listener which will then invoke the MySpringEnabledAction.
- You can modify the build.xml to change the phrase "Hello World" to something
- else and re-run "ant runtest". You can modify spring-context-hello.xml and/or
- spring-context-goodbye.xml and change the greeting value of the Spring beans.
-
- After you have run the test and seen the activity on the console also use the a queue viewer
- like the one found in the JBoss JMX Console (if you are using JBossMQ) to
- see the modified message in the outbound queue: quickstart_spring_aop_Response
-
-Project file descriptions:
-==========================
- Review the helloworld quickstart as the majority of this is similiar to
- that example
-
- MySpringEnabledAction.java:
- There is one action method called "sayHelloAopStyle". The method
- gets triggered when a JMS message is sent. "sayHelloAopStyle" actually uses the message
- payload to get the greeting, but the interceptor will change the greeting.
-
- jboss-esb.xml
- The method, "sayHelloAopStyle" uses a spring interceptor to change the greeting message.
- Notice that the action does not have any println statements, "MyInterceptor"
- is doing all of the console output work. The interceptor is configured in spring-context.xml,
- not annotation style. You can change the greeting in build.xml. The greeting is sent to the
- ESB via JMS.
- <action name="sayHelloAopStyle"
- class="org.jboss.soa.esb.samples.quickstart.helloworldaction.MySpringEnabledAction"
- process="sayHelloAopStyle">
- <property name="exceptionMethod" value="exceptionHandler"/>
- <property name="springContextXml" value="spring-context.xml"/>
+ <action name="sayHelloAopStyle"
+ class="org.jboss.soa.esb.samples.quickstart.helloworldaction.MySpringEnabledAction"
+ process="sayHelloAopStyle">
+ <property name="exceptionMethod" value="exceptionHandler"/>
+ <property name="springContextXml" value="spring-context.xml"/>
</action>
-
- An ESB action class must have a constructor that accepts a ConfigTree argument like the following:
- public MyJMSListenerAction(ConfigTree config) { _config = config; }
+
+ An ESB action class must have a constructor that accepts a ConfigTree
+ argument like the following:
+ public MyJMSListenerAction(ConfigTree config) { _config = config; }
- A ConfigTree is an object holding any attributes associated with the action declaration in the jbossesb.xml
+ A ConfigTree is an object holding any attributes associated with the action
+ declaration in the jbossesb.xml
Modified: labs/jbossesb/trunk/product/samples/quickstarts/spring_helloworld/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/spring_helloworld/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/spring_helloworld/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,105 +1,91 @@
Overview:
=========
- The purpose of the spring_helloworld quickstart sample is to show the use of
- Spring based action invocations. You can use a single Action class and make
- multiple method calls or use multiple Action classes.
- You can specify Spring bean XML definitions in jboss-esb.xml and lookup the beans
- in your Action class. Each Action loads a single Spring IoC container upon first spring bean
- invocation. Subsequent invocations will not load a new IoC container. Also, none of the Spring
- dependencies are included. You must manually add additional Spring dependency JARs to the classpath
- to create Spring beans that have special dependencies, like a DB connection pool.
+ The purpose of the spring_helloworld quickstart sample is to show the use of
+ Spring based action invocations. You can use a single Action class and make
+ multiple method calls or use multiple Action classes.
+ You can specify Spring bean XML definitions in jboss-esb.xml and lookup the
+ beans in your Action class. Each Action loads a single Spring IoC container
+ upon first spring bean invocation. Subsequent invocations will not load a new
+ IoC container. Also, none of the Spring dependencies are included. You must
+ manually add additional Spring dependency JARs to the classpath to create
+ Spring beans that have special dependencies, like a DB connection pool.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
- 5. Shutdown the listener by simply using Ctrl-C in that window.
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch back to Application Server console to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
+
+Things to Consider:
+===================
+ Review the helloworld quickstart as the majority of this is similiar to
+ that example
-To Run '.esb' archive mode:
-===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 3. Switch back to Application Server console to see the output from the ESB
+ MySpringEnabledAction.java:
+ Has methods to display the inbound message, modify the message and to handle
+ any exceptions which might be thrown in the action processing.
+ MySpringEnabledAction will also lookup 2 different Spring beans located in 2
+ different Spring config files and append the "greeting" to the message.
+ Lastly, this action extends AbstractSpringAction. If you extend
+ AbstractSpringAction, you can define spring configuration files in
+ jboss-esb.xml and lookup Spring beans with
+ "getSpringBeanFactory().getBean("someObject")".
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. You might review the build.xml file to see how it is setup.
- More details on the build.xml can be found later in this document. Shutdown
- the listener by simply using Ctrl-C in that window.
+ jbossesb.xml:
+ There are 3 different actions. The first loads up a spring context, does a
+ Spring bean lookup for "helloObject" and displays the JMS message payload
+ plus the "helloObject.getGreeting()" value that is set in
+ spring-context-hello.xml.
+
+ The second action will Spring lookup the "goodbyeObject" and append the
+ "goodbyeObject.getGreeting()" value to the message.
+
+ The third action will Spring lookup the "helloObject" and "goodbyeObject"
+ and append the "helloObject.getGreeting()" and "goodbyeObject.getGreeting()"
+ value to the message. This last action demonstrates that a single action can
+ lookup Spring beans that are in different Spring config files, so long as
+ both config files are a comma separated list value for "springContextXml".
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" to shoot a JMS message
- into the listener which will then invoke the MyJMSListenerAction and display
- it to the console. You can modify the build.xml to change the phrase
- "Hello World" to something else and re-run "ant runtest". You can modify
- spring-context-hello.xml and/or spring-context-goodbye.xml and change the greeting
- value of the Spring beans.
-
- After you have run the test and seen the activity on the console also use the a queue viewer
- like the one found in the JBoss JMX Console (if you are using JBossMQ) to
- see the modified message in the outbound queue: quickstart_spring_helloworld_Response
-
-Project file descriptions:
-==========================
- Review the helloworld quickstart as the majority of this is similiar to
- that example
-
- MySpringEnabledAction.java:
- Has methods to display the inbound message, modify the message and to handle an
- exceptions which might be thrown in the action processing. MySpringEnabledAction will also
- lookup 2 different Spring beans located in 2 different Spring config files and append the
- "greeting" to the message. Lastly, this action extends AbstractSpringAction. If you
- extend AbstractSpringAction, you can define spring configuration files in jboss-esb.xml
- and lookup Spring beans with "getSpringBeanFactory().getBean("someObject")".
-
- jbossesb.xml:
- There are 3 different actions. The first loads up a spring context, does a Spring bean lookup
- for "helloObject" and displays the JMS message payload plus the "helloObject.getGreeting()"
- value that is set in spring-context-hello.xml.
-
- The second action will Spring lookup the "goodbyeObject" and append the
- "goodbyeObject.getGreeting()" value to the message.
-
- The third action will Spring lookup the "helloObject" and "goodbyeObject" and append the
- "helloObject.getGreeting()" and "goodbyeObject.getGreeting()" value to the message. This
- last action demonstrates that a single action can lookup Spring beans that are in differnt
- Spring config files, so long as both config files are a comma separated list value for
- "springContextXml".
- <action name="sayHello"
- class="org.jboss.soa.esb.samples.quickstart.helloworldaction.MyJMSListenerAction"
- process="sayHelloSpring,displayMessage">
- <property name="exceptionMethod" value="exceptionHandler"/>
- <property name="springContextXml" value="spring-context-hello.xml"/>
+ <action name="sayHello"
+ class="org.jboss.soa.esb.samples.quickstart.helloworldaction.MyJMSListenerAction"
+ process="sayHelloSpring,displayMessage">
+ <property name="exceptionMethod" value="exceptionHandler"/>
+ <property name="springContextXml" value="spring-context-hello.xml"/>
</action>
<action name="addGoodbye"
- class="org.jboss.soa.esb.samples.quickstart.helloworldaction.MyJMSListenerAction"
- process="sayGoodbyeSpring,displayMessage">
- <property name="exceptionMethod" value="exceptionHandler"/>
- <property name="springContextXml" value="spring-context-goodbye.xml"/>
+ class="org.jboss.soa.esb.samples.quickstart.helloworldaction.MyJMSListenerAction"
+ process="sayGoodbyeSpring,displayMessage">
+ <property name="exceptionMethod" value="exceptionHandler"/>
+ <property name="springContextXml" value="spring-context-goodbye.xml"/>
</action>
<action name="addHelloGoodbye"
- class="org.jboss.soa.esb.samples.quickstart.helloworldaction.MyJMSListenerAction"
- process="sayHelloSpring,sayGoodbyeSpring,displayMessage">
- <property name="exceptionMethod" value="exceptionHandler"/>
- <property name="springContextXml" value="spring-context-goodbye.xml,spring-context-hello.xml"/>
+ class="org.jboss.soa.esb.samples.quickstart.helloworldaction.MyJMSListenerAction"
+ process="sayHelloSpring,sayGoodbyeSpring,displayMessage">
+ <property name="exceptionMethod" value="exceptionHandler"/>
+ <property name="springContextXml" value="spring-context-goodbye.xml,spring-context-hello.xml"/>
</action>
- An ESB action class must have a constructor that accepts a ConfigTree argument like the following:
- public MySpringEnabledAction(ConfigTree config) { _config = config; }
+ An ESB action class must have a constructor that accepts a ConfigTree
+ argument like the following:
+ public MySpringEnabledAction(ConfigTree config) { _config = config; }
- A ConfigTree is an object holding any attributes associated with the action declaration in the jbossesb.xml
+ A ConfigTree is an object holding any attributes associated with the action
+ declaration in the jbossesb.xml
Modified: labs/jbossesb/trunk/product/samples/quickstarts/spring_jpetstore/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/spring_jpetstore/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/spring_jpetstore/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,97 +1,73 @@
Overview:
=========
- The purpose of the spring_jpetstore quickstart sample is to show advanced use of
- Spring based action invocations. You can leverage any application logic, like
- the business logic tier of a spring based web application by looking up the
- business service bean and executing a method. This is a complex usage of Spring
- that includes AOP, iBatis, a datasource and transaction management.
-
- You can specify Spring bean XML definitions in jboss-esb.xml and lookup the beans
- in your Action class. Each Action loads a single Spring IoC container upon first spring bean
- invocation. Subsequent invocations will not load a new IoC container. In this example
- many Spring dependencies are included and used.
+ The purpose of the spring_jpetstore quickstart sample is to show advanced use
+ of Spring based action invocations. You can leverage any application logic,
+ like the business logic tier of a spring based web application by looking up
+ the business service bean and executing a method. This is a complex usage of
+ Spring that includes AOP, iBatis, a datasource and transaction management.
+
+ You can specify Spring bean XML definitions in jboss-esb.xml and lookup the
+ beans in your Action class. Each Action loads a single Spring IoC container
+ upon first spring bean invocation. Subsequent invocations will not load a new
+ IoC container. In this example many Spring dependencies are included and used.
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant start-hsqldb'.
- 3. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 4. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 5. Switch back to "Window1" to see the output from the ESB
- 6. Shutdown the listener by simply using Ctrl-C in that window.
-
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type
+ 'ant start-hsqldb'.
+ 3. In a command terminal window in this folder ("Window2"), type 'ant run'.
+ 4. Open another command terminal window in this folder ("Window3"), type
+ 'ant runtest'.
+ 5. Switch back to "Window2" to see the output from the ESB
+ 6. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window2"), type 'ant undeploy-jms-dests'.
+ 7. Interrupt the database ("Window1") using Ctrl-C.
+
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant start-hsqldb'.
- 3. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 4. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 5. Switch back to Application Server console to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Start the database in this folder ("Window1"), type 'ant start-hsqldb'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to Application Server console to see the output from the ESB
+ 5. Interrupt the database ("Window1") using Ctrl-C.
+ 6. In this folder ("Window1"), type 'ant undeploy'.
-To Run '.esb' archive mode:
-===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant start-hsqldb'.
- 3. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 4. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 5. Switch back to Application Server console to see the output from the ESB
-
- 'run' target description:
- In a command prompt window, start the listeners by simply running "ant"
- in this directory. It is important to note that this build.xml file adds several
- Spring dependency JARs to the classpath. Those JARS are located in the "lib" directory.
- Since spring.jar, spring-aspects.jar and spring-mock.jar are already in the JBossESB
- classpath, they are not included in the lib directory. You might review the build.xml
- file to see how it is setup. More details on the build.xml can be found later in this
- document. Shutdown the listener by simply using Ctrl-C in that window.
-
- 'runtest' target description:
- In a separate command prompt window, run "ant runtest" to shoot a JMS message
- into the listener which will then place the contents of "sample-order.xml"
- on a JMS queue. You can modify the "sample-order.xml" to change the order details
- and re-run "ant runtest". The following XML changes will be output to the console:
- <totalPrice></totalPrice>
- <shipToFirstName></shipToFirstName>
- <shipToLastName></shipToLastName>
- <shipAddress1></shipAddress1>
- <shipAddress2></shipAddress2>
- <shipCity></shipCity>
- <shipState></shipState>
- <shipZip></shipZip>
-
- After you have run the test and seen the activity on the console also use the a queue viewer
- like the one found in the JBoss JMX Console (if you are using JBossMQ) to
- see the modified message in the outbound queue:
-quickstart_spring_jpetstore_Response
-
Project file descriptions:
==========================
-
- InsertOrderAction.java:
- Takes the sample order XML from the ESB message then converts it into an Order POJO. The
- order POJO is then inserted into the Spring JPetstore database by calling the
- "PetStoreFacade.insertOrder()" method. The "PestoreFacade.insertOrder()" method uses
- a SpringAOP transaction advice.
-
- After successful insert, the InsertOrderAction will query the database, by using
- "PetStoreFacade.getOrdersByUsername()". and display the Order
- details in the console.
- jbossesb.xml:
- Make sure that the Spring application context files are defined via the "springContextXml" property.
- <action name="insertOrderAction"
- class="org.jboss.soa.esb.samples.quickstart.spring.InsertOrderAction"
- process="insertOrder">
- <property name="exceptionMethod" value="exceptionHandler"/>
- <property name="springContextXml" value="applicationContext.xml,dataAccessContext-local.xml"/>
- </action>
+ InsertOrderAction.java:
+ Takes the sample order XML from the ESB message then converts it into an
+ Order POJO. The order POJO is then inserted into the Spring JPetstore
+ database by calling the "PetStoreFacade.insertOrder()" method. The
+ "PestoreFacade.insertOrder()" method uses a SpringAOP transaction advice.
- An ESB action class must have a constructor that accepts a ConfigTree argument like the following:
- public MyJMSListenerAction(ConfigTree config) { _config = config; }
+ After successful insert, the InsertOrderAction will query the database, by
+ using "PetStoreFacade.getOrdersByUsername()". and display the Orderd details
+ in the console.
+
+ jbossesb.xml:
+ Make sure that the Spring application context files are defined via the
+ "springContextXml" property.
+
+ <action name="insertOrderAction"
+ class="org.jboss.soa.esb.samples.quickstart.spring.InsertOrderAction"
+ process="insertOrder">
+ <property name="exceptionMethod" value="exceptionHandler"/>
+ <property name="springContextXml"
+ value="applicationContext.xml,dataAccessContext-local.xml"/>
+ </action>
+
+ An ESB action class must have a constructor that accepts a ConfigTree
+ argument like the following:
+ public MyJMSListenerAction(ConfigTree config) { _config = config; }
- A ConfigTree is an object holding any attributes associated with the action declaration in the jbossesb.xml
+ A ConfigTree is an object holding any attributes associated with the action
+ declaration in the jbossesb.xml
Modified: labs/jbossesb/trunk/product/samples/quickstarts/static_router/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/static_router/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/static_router/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,34 +1,31 @@
Overview:
=========
- This quick start will create a file on the FTP server and show the progress
- of the message through a static route. Intermediate files will be created
- in the directories under build/dirs/
+ This quick start will create a file on the FTP server and show the progress
+ of the message through a static route. Intermediate files will be created
+ in the directories under build/dirs/
Running this quickstart:
========================
- This test assumes:
- 1) That the quickstarts.properties file has been configured with the details
- of the ftp server.
- 2) That the configured ftp directory is writable.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Make sure that the quickstarts.properties file contains the configuration
+ information for the FTP hostname, user, password and base directory.
+ Make sure that you have write access to the FTP server.
+
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to "Window1" to see the output from the ESB
+ 4. When finished, interrupt the ESB using Ctrl-C.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to Application Server console to see the output from the ESB
-
-
-
-
-
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/transform_CSV2XML/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_CSV2XML/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_CSV2XML/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,79 +1,73 @@
Overview:
=========
- This quickstart demonstrates how to transform a comma separated value (CSV) file to an xml.
- The tranformation is done by configuring Smooks and performing two transformation, one
- transformation from CSV to an intermediate xml format, and a second transformation from
- the intermediate xml format to the target xml.
-
- This Quickstart does not use the JBoss ESB Administration Console to manage the
- message Transformation configurations to the ESB.
- to manage this Quickstart's transformations via the Console.
+ This quickstart demonstrates how to transform a comma separated value (CSV) file to an xml.
+ The tranformation is done by configuring Smooks and performing two transformation, one
+ transformation from CSV to an intermediate xml format, and a second transformation from
+ the intermediate xml format to the target xml.
+ This Quickstart does not use the JBoss ESB Administration Console to manage the
+ message Transformation configurations to the ESB.
+ to manage this Quickstart's transformations via the Console.
+
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts and a
- more detailed descripton of the different ways to run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
- It would be a great idea to read MessageTransformation.pdf to fully understand this Quickstart.
- It is located in the docs/services folder.
+ A comprehensive description of message transformation can be found in
+ MessageTransformation.pdf, located in the docs/services folder.
-
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to "Window1" to see the output from the ESB
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder ("Window2"), type 'ant runtest'.
- 4. Switch back to Application Server console to see the output from the ESB
- Note: that there is currently a problem when running in this mode. I had to comment out
- the following in jbossesb-properties that is located in the jbossesb.sar:
- <!--
- <properties name="filters">
- <property name="org.jboss.soa.esb.courier.filter.1" value="org.jboss.internal.soa.esb.message.metadata.MetaDataFilter"/>
- </properties>
- -->
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
- 'run' target description:
- Will start a standalone ESB. This window will display the CVS message before it is
- transformed into the intermediate xml format, and the display the taget xml
- transformation.
- To shutdown the ESB simply use Ctrl-C.
+What to look at in this Quickstart:
+===================================
+ As stated above, reading MessageTransformation.pdf would be of great benefit
+ in understanding JBoss ESB Transformations.
- 'runtest' target description:
- This target will shoot a JMS message containing the contents of the SampleOrder.csv
- file located in this folder.
+ jbossesb.xml:
+ The ESB configuration file in this Quickstart simply defines a JMS Listener
+ for receiving the contents of the SampleOrder.csv file located in this
+ folder.
+ smooks-cdr.lst:
+ This file is used by the JBoss ESB Transformation Service to list the
+ Transformation resource configuration URIs. Out of the box, the
+ smoooks-cdr.lst file in this Quickstart refers to 2 resource URIs, both of
+ which are classpath based.
-What to look at in this Quickstart:
-===================================
- As stated above, a read of MessageTransformation.pdf would be of great benefit in understanding
- JBoss ESB Transformations.
+ smooks-res.xml:
+ This file defines the Transformations for the Quickstart. In this case it
+ defines two transformations.
+
+ 1. The first transformation uses smooks CSVParser to parse the CVS file and
+ create an intermediate xml format that looks like this:
+
+ <cvs-set>
+ <cvs-record>
+ <orderId>1</orderId>
+ <orderDate>Wed Nov 15 13:45:28 EST 2006</orderDate>
+ <statusCode>0</statusCode>
+ ...
+ </cvs-record>
+ </cvs-set>
- jbossesb.xml: The ESB configuration file in this Quickstart simply defines a JMS Listener for receiving
- the contents of the SampleOrder.csv file located in this folder.
-
- smooks-cdr.lst: This file is used by the JBoss ESB Transformation Service to list the Transformation
- resource configuration URIs. Out of the box, the smoooks-cdr.lst file in this Quickstart
- refers to 2 resource URIs, both of which are classpath based.
-
- smooks-res.xml: This file defines the Transformations for the Quickstart. In this case it defines
- two transformations.
- 1. The first transformation uses smooks CSVParser to parse the CVS file and create an
- intermediate xml format that looks like this:
- <cvs-set>
- <cvs-record>
- <orderId>1</orderId>
- <orderDate>Wed Nov 15 13:45:28 EST 2006</orderDate>
- <statusCode>0</statusCode>
- ...
- </cvs-record>
- </cvs-set>
- 2. The second tranformation transforms the intermediate smooks format to the
- target xml format. This is the second section in smooks-res.xml. It is here you
- can map the values to you're target xml format.
+ 2. The second tranformation transforms the intermediate smooks format to the
+ target xml format. This is the second section in smooks-res.xml. It is
+ here you can map the values to you're target xml format.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/transform_EDI2XML_Groovy_XSLT/build.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_EDI2XML_Groovy_XSLT/build.xml 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_EDI2XML_Groovy_XSLT/build.xml 2007-07-19 12:58:21 UTC (rev 13633)
@@ -19,9 +19,6 @@
</copy>
</target>
- <!-- The ESB itself is started by the default "run" target - defined in base-build.xml -->
-
- <!-- Target for injecting the sample order message for transformation... -->
<target name="runtest" description="runs Test JMS Sender" depends="compile">
<echo>Runs Test JMS Sender</echo>
<java fork="yes" classname="org.jboss.soa.esb.samples.quickstart.transformedi2xmlgroovyxslt.test.SendJMSMessage" failonerror="true">
Modified: labs/jbossesb/trunk/product/samples/quickstarts/transform_EDI2XML_Groovy_XSLT/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_EDI2XML_Groovy_XSLT/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_EDI2XML_Groovy_XSLT/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,60 +1,70 @@
Overview:
=========
- This is the most advanced of the "transform" Quickstarts. Be sure to go through the other
- Quickstarts before going through this.
-
- This Quickstart is quite detailed. There's an accompanying Flash demo that walks you through
- all the steps that were involved in creating this Quickstart. You should check this out before
- or as you go through this quickstart:
- http://labs.jboss.com/portal/jbossesb/resources/tutorials/xformation-demos/console-demo-03.html
-
- Out of the box, this Quickstart does not use the JBoss ESB Administration Console to manage the
- message Transformation configurations to the ESB. However, as you'll hopefully have seen from the
- Flash demo mentioned above, this Quickstart was created using the Admin Console. In order to ship
- with the ESB distribution, the transformations configurations were exported from the console and
- into the "smooks-res.xml" file here in this Quickstart. See the end of this README for details on how
- to re-import and manage this Quickstart's transformations via the Console.
+ This is the most advanced of the "transform" Quickstarts. Be sure to go
+ through the other transformation Quickstarts before going through this.
+
+ This Quickstart is quite detailed. There's an accompanying Flash demo that
+ walks you through all the steps that were involved in creating this
+ Quickstart. You should check this out before or as you go through this
+ quickstart:
+ http://labs.jboss.com/portal/jbossesb/resources/tutorials/xformation-demos/console-demo-03.html
+
+ Out of the box, this Quickstart does not use the JBoss ESB Administration
+ Console to manage the message Transformation configurations to the ESB.
+ However, as you'll hopefully have seen from the Flash demo mentioned above,
+ this Quickstart was created using the Admin Console. In order to ship with
+ the ESB distribution, the transformations configurations were exported from
+ the console and into the "smooks-res.xml" file here in this Quickstart. See
+ the end of this README for details on how to re-import and manage this
+ Quickstart's transformations via the Console.
+Running this quickstart:
+========================
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
-Before Running:
-===============
- 1. Update the "org.jboss.esb.appserver.home" property in the quickstarts.properties file in "../".
- 2. Make sure to run the the ant script in the "install" folder of the distribution. This
- deploys the required SARs to your JBoss Application Server instance.
- 3. Make sure the JBoss Application server is running.
- 4. It would be a great idea to read MessageTransformation.pdf to fully understand this
- Quickstart. It is located in the docs/services folder.
+ A comprehensive description of message transformation can be found in
+ MessageTransformation.pdf, located in the docs/services folder.
+To Run standalone mode:
+=======================
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
-To Run:
-=======
- 1. In a command terminal window in this folder ("Window1"), type "ant run".
- 2. Open another command terminal window in this folder ("Window2"), type "ant runtest".
- 3. Switch back to "Window1" to see the message transformation before and after.
-
- Note that, as with all these Quickstarts, you can deply and run them through your local
- JBoss Application Server instance. To do this, skip step 1 above and in it's place
- execute the following Ant task:
- "ant deployToSAR"
- This will package up this Quickstart and deploy it to your JBoss AS instance. The Quickstart
- "Service" will automatically start then. At that point, continue with steps 2 and 3.
+To Run '.esb' archive mode:
+===========================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
-
What to look at in this Quickstart:
===================================
- The Flash demo at:
- http://labs.jboss.com/portal/jbossesb/resources/tutorials/xformation-demos/console-demo-03.html
+ As stated above, reading MessageTransformation.pdf would be of great benefit
+ in understanding JBoss ESB Transformations.
+ The Flash demo at:
+ http://labs.jboss.com/portal/jbossesb/resources/tutorials/xformation-demos/console-demo-03.html
Playing with this Transformation through the Administration Console:
====================================================================
- To load the Transformation Configurations defined in smooks-res.xml into the Admin Console, and have them
- managed from the Admin Console, do the following:
-
- 1. Deploy the console as outlined in MessageTransformation.pdf.
- 2. Edit the smooks-cdr.lst file in this folder, commenting out both the classpath based listings and
- uncommenting out the listing for the console HTTP URI. The same set of steps were executed at the
- start of the Flash demo.
- 3. In the console, import "smooks-res.xml" through the "Import Configurations" form.
- 4. You are now ready to start managing the message transformations through the console. You can add more
- transformations and modify the existing transformations. Be sure to read MessageTransformation.pdf!!!
+ To load the Transformation Configurations defined in smooks-res.xml into the
+ Admin Console, and have them managed from the Admin Console, do the following:
+
+ 1. Deploy the console as outlined in MessageTransformation.pdf.
+ 2. Edit the smooks-cdr.lst file in this folder, commenting out both the
+ classpath based listings and uncommenting out the listing for the console
+ HTTP URI. The same set of steps were executed at the start of the Flash
+ demo.
+ 3. In the console, import "smooks-res.xml" through the "Import Configurations"
+ form.
+ 4. You are now ready to start managing the message transformations through the
+ console. You can add more transformations and modify the existing
+ transformations.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2POJO/build.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2POJO/build.xml 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2POJO/build.xml 2007-07-19 12:58:21 UTC (rev 13633)
@@ -12,9 +12,6 @@
<import file="../conf/base-build.xml"/>
- <!-- The ESB itself is started by the default "run" target - defined in base-build.xml -->
-
- <!-- Target for injecting the sample order message for transformation... -->
<target name="runtest" depends="compile" description="runs test JMS Sender">
<echo>Runs Test JMS Sender</echo>
<java fork="yes" classname="org.jboss.soa.esb.samples.quickstart.transformxml2pojo.test.SendJMSMessage" failonerror="true">
Modified: labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2POJO/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2POJO/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2POJO/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,32 +1,61 @@
-XML to POJO
+Overview:
+=========
+The purpose of the simple_transformation quickstart sample is to illustrate the
+use of Smooks performing a simple transformation by converting a XML file into
+Java POJOs.
-The purpose of the simple_transformation quickstart sample is to illustrate the use of Smooks performing
-a simple transformation by converting a XML file into Java POJOs.
+Running this quickstart:
+========================
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
-You will need three command windows to execute this demonstration. In the three windows execute the following
-commands in the order listed:
-ant
-ant receive
-ant runtest
+ A comprehensive description of message transformation can be found in
+ MessageTransformation.pdf, located in the docs/services folder.
-The listener executes by simply typing "ant" at the command line and it waits. Shut it down via Ctrl-C.
-The message sender executes by typing in "ant runtest". This executes the SendJMSMessage.java class that
-picks up the SampleOrder.xml file from the root of the project and shoots it over to the "quickstart_simple_transformation_Request"
-queue. The gateway listener is looking for messages in that particular queue.
-The message receive executes by typing in "ant receive". This executes the ReceiveJMSMessage.java class
-that waits until a message is received (polls every 2 seconds) and displays it to the console. You can
-shut it down via Ctrl-C.
+To Run standalone mode:
+=======================
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant receive'.
+ 4. Open another command terminal window in this folder ("Window3"), type
+ 'ant runtest'.
+ 5. Switch back to "Window1" to see the output from the ESB
+ 6. When finished, interrupt the receiver ("Window2") using Ctrl-C.
+ 7. Interrupt the ESB ("Window1") using Ctrl-C and type
+ 'ant undeploy-jms-dests'.
-For more information on the Smooks Transformation engine please consult the MessagesTransformation.pdf
-in the docs directory.
+To Run '.esb' archive mode:
+===========================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant receive'.
+ 3. Open another command terminal window in this folder ("Window3"), type
+ 'ant runtest'.
+ 4. Switch back to Application Server console to see the output from the ESB
+ 5. When finished, interrupt the receiver ("Window2") using Ctrl-C.
+ 6. Undeploy the esb archive ("Window1"), type 'ant undeploy'.
-Files to review:
-* esb-config.xml - uses the SmooksTransformerAction which is shipped with the JBoss ESB
-* smooks-res.xml - handles the mappings of the from/to combinations and determines which transformer to apply
-* SampleOrder.xml - is the inbound test order. Feel free to modify the data (not the structure) and send
-it into the transformer multiple times (ant runtest) to see the results.
-* src\org\jboss\soa\esb\dvdstore\DVDStoreAction.java - converts the beans into a concatenated string
-* src\org\jboss\soa\esb\dvdstore\OrderHeader.java - holds the header portion of the Order
-* src\org\jboss\soa\esb\dvdstore\OrderItem.java - holds a line item for the Order
-* src\org\jboss\soa\esb\dvdstore\Customer.java - holds the Customer associated with the Order.
-* src\org\jboss\soa\esb\dvdstore\orderitem.st - is the string transformation template
\ No newline at end of file
+What to look at in this Quickstart:
+===================================
+ As stated above, reading MessageTransformation.pdf would be of great benefit
+ in understanding JBoss ESB Transformations.
+
+ * esb-config.xml - uses the SmooksTransformerAction which is shipped with the
+ JBoss ESB.
+ * smooks-res.xml - handles the mappings of the from/to combinations and
+ determines which transformer to apply.
+ * SampleOrder.xml - is the inbound test order. Feel free to modify the data
+ (not the structure) and send it into the transformer multiple times (ant
+ runtest) to see the results.
+ * src\org\jboss\soa\esb\dvdstore\DVDStoreAction.java - converts the beans into
+ a concatenated string.
+ * src\org\jboss\soa\esb\dvdstore\OrderHeader.java - holds the header portion
+ of the Order.
+ * src\org\jboss\soa\esb\dvdstore\OrderItem.java - holds a line item for the
+ Order.
+ * src\org\jboss\soa\esb\dvdstore\Customer.java - holds the Customer associated
+ with the Order.
+ * src\org\jboss\soa\esb\dvdstore\orderitem.st - is the string transformation
+ template.
\ No newline at end of file
Modified: labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/README.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/README.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/README.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,87 +1,101 @@
Overview:
=========
- This is another simple example of how to manually define and apply a Message Transformation
- within JBoss ESB 4.0GA.
-
- This Quickstart is an extension of the "transformation_XML2XML_simple" Quickstart, demonstrating how
- JBoss ESB Transformations can simplify your XSLT transformations by combining the
- power of XSLT with Java. In this Quickstart, we use Java to perform the ugly string manipulation
- on the SampleOrder date field (see OrderDate.java) and use XSLT for what it's good at i.e.
- Templating. Again, the transformed SampleOrder.xml message is just printed to the Java
- console (message before and after).
-
- This Quickstart does not use the JBoss ESB Administration Console to manage the
- message Transformation configurations to the ESB. See the end of this README for details on how
- to manage this Quickstart's transformations via the Console.
-
- Check out the Administration Console Flash demos at:
- http://labs.jboss.com/portal/jbossesb/resources/tutorials/xformation-demos/console-demos.html
+ This is another simple example of how to manually define and apply a Message
+ Transformation within JBoss ESB.
+ This Quickstart is an extension of the "transformation_XML2XML_simple"
+ Quickstart, demonstrating how JBoss ESB Transformations can simplify your
+ XSLT transformations by combining the power of XSLT with Java. In this
+ Quickstart, we use Java to perform the ugly string manipulation on the
+ SampleOrder date field (see OrderDate.java) and use XSLT for what it's good at
+ i.e. Templating. Again, the transformed SampleOrder.xml message is just
+ printed to the Java console (message before and after).
-Before Running:
-===============
- 1. Update the "org.jboss.esb.appserver.home" property in the quickstarts.properties file in "../".
- 2. Make sure to run the the ant script in the "install" folder of the distribution. This
- deploys the required SARs to your JBoss Application Server instance.
- 3. Make sure the JBoss Application server is running.
- 4. It would be a great idea to read MessageTransformation.pdf to fully understand this
- Quickstart. It is located in the docs/services folder.
+ This Quickstart does not use the JBoss ESB Administration Console to manage
+ the message Transformation configurations to the ESB. See the end of this
+ README for details on how to manage this Quickstart's transformations via the
+ Console.
+ Check out the Administration Console Flash demos at:
+ http://labs.jboss.com/portal/jbossesb/resources/tutorials/xformation-demos/console-demos.html
-To Run:
-=======
- 1. In a command terminal window in this folder ("Window1"), type "ant run".
- 2. Open another command terminal window in this folder ("Window2"), type "ant runtest".
- 3. Switch back to "Window1" to see the message transformation before and after.
-
- Note that, as with all these Quickstarts, you can deply and run them through your local
- JBoss Application Server instance. To do this, skip step 1 above and in it's place
- execute the following Ant task:
- "ant deployToSAR"
- This will packagce up this Quickstart and deploy it to your JBoss AS instance. The Quickstart
- "Service" will automatically start then. At that point, continue with steps 2 and 3.
+Running this quickstart:
+========================
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
+ A comprehensive description of message transformation can be found in
+ MessageTransformation.pdf, located in the docs/services folder.
+To Run standalone mode:
+=======================
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
+
+To Run '.esb' archive mode:
+===========================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
+
What to look at in this Quickstart:
===================================
- As stated above, a read of MessageTransformation.pdf would be of great benefit in understanding
- JBoss ESB Transformations.
+ As stated above, reading MessageTransformation.pdf would be of great benefit
+ in understanding JBoss ESB Transformations.
- jbossesb.xml: The ESB configuration file in this Quickstart simply defines a JMS Listener for receiving
- the contents of the SampleOrder.xml file located in this folder (line 31). The listener
- configuration then executes the "SmooksTransformer" action for the Message Exchange between
- "A" and "B".
-
- smooks-cdr.lst: This file is used by the JBoss ESB Transformation Service to list the Transformation
- resource configuration URIs. Out of the box, the smoooks-cdr.lst file in this Quickstart
- refers to 2 resource URIs, both of which are classpath based. It also has a commented
- out listing for accessing Transformation Configurations managed by the JBoss ESB
- Administration Conosle (see below).
-
- smooks-res.xml: This file defines the Transformations for the Quickstart. This time, there are a number of
- transformation configurations, all "targeted" at the same message.
-
- OrderDate.java: (In the src tree). This is just a simple POJO class. It gets populated by JBoss ESB
- Transformation (via Smooks) and is used by the XSLT (defined in smooks-res.xml)
- to generate the new OrderDate element in the output message. This class uses the standard
- Java SimpleDateFormat class for decoding the orderDate value and extracting the components of
- the date from it (day, month, zone etc). This means you avoid having to do this in your XSLT
- code, which would be very ugly and difficult to maintain.
+ jbossesb.xml:
+ The ESB configuration file in this Quickstart simply defines a JMS Listener
+ for receiving the contents of the SampleOrder.xml file located in this
+ folder (line 31). The listener configuration then executes the
+ "SmooksTransformer" action for the Message Exchange between "A" and "B".
+ smooks-cdr.lst:
+ This file is used by the JBoss ESB Transformation Service to list the
+ Transformation resource configuration URIs. Out of the box, the
+ smoooks-cdr.lst file in this Quickstart refers to 2 resource URIs, both of
+ which are classpath based. It also has a commented out listing for
+ accessing Transformation Configurations managed by the JBoss ESB
+ Administration Console (see below).
+ smooks-res.xml:
+ This file defines the Transformations for the Quickstart. This time, there
+ are a number of transformation configurations, all "targeted" at the same
+ message.
+
+ OrderDate.java: (In the src tree).
+ This is just a simple POJO class. It gets populated by JBoss ESB
+ Transformation (via Smooks) and is used by the XSLT (defined in
+ smooks-res.xml) to generate the new OrderDate element in the output message.
+ This class uses the standard Java SimpleDateFormat class for decoding the
+ orderDate value and extracting the components of the date from it (day,
+ month, zone etc). This means you avoid having to do this in your XSLT code,
+ which would be very ugly and difficult to maintain.
+
Playing with this Transformation through the Administration Console:
====================================================================
- To load the Transformation Configurations defined in smooks-res.xml into the Admin Console, and have them
- managed from the Admin Console, do the following:
-
- 1. Deploy the console as outlined in MessageTransformation.pdf.
- 2. Edit the smooks-cdr.lst file in this folder, commenting out both the classpath based listings and
- uncommenting out the listing for the console HTTP URI.
- 3. In the console:
- a) Add "Message Exchange Participants" for "A" and "B" through the "Manage Message Exchange Participants" form.
- b) Add new "Message Contract" against "A" and "B" for "text/xml:messageAtA" and "text/xml:messageAtB" respectively.
- Note: "messageAtA" and "messageAtB" are the Message Namespace values and "text/xml" is the Message Mime in
- both cases.
- c) Import "smooks-res.xml" through the "Import Configurations" form.
- 4. You are now ready to start managing the message transformations through the console. You can add more
- transformations and modify the existing transformations. Be sure to read MessageTransformation.pdf!!!
+ To load the Transformation Configurations defined in smooks-res.xml into the
+ Admin Console, and have them managed from the Admin Console, do the following:
+
+ 1. Deploy the console as outlined in MessageTransformation.pdf.
+ 2. Edit the smooks-cdr.lst file in this folder, commenting out both the
+ classpath based listings and uncommenting out the listing for the console
+ HTTP URI.
+ 3. In the console:
+ a) Add "Message Exchange Participants" for "A" and "B" through the "Manage
+ Message Exchange Participants" form.
+ b) Add new "Message Contract" against "A" and "B" for "text/xml:messageAtA"
+ and "text/xml:messageAtB" respectively.
+ Note: "messageAtA" and "messageAtB" are the Message Namespace values and
+ "text/xml" is the Message Mime in both cases.
+ c) Import "smooks-res.xml" through the "Import Configurations" form.
+ 4. You are now ready to start managing the message transformations through the
+ console. You can add more transformations and modify the existing
+ transformations. Be sure to read MessageTransformation.pdf!!!
Modified: labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/build.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/build.xml 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/build.xml 2007-07-19 12:58:21 UTC (rev 13633)
@@ -10,9 +10,6 @@
<!-- Import the base Ant build script... -->
<import file="../conf/base-build.xml"/>
- <!-- The ESB itself is started by the default "run" target - defined in base-build.xml -->
-
- <!-- Target for injecting the sample order message for transformation... -->
<target name="runtest" depends="compile"
description="runs Test JMS Sender">
<echo>Runs Test JMS Sender</echo>
Modified: labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_simple/build.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_simple/build.xml 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_simple/build.xml 2007-07-19 12:58:21 UTC (rev 13633)
@@ -9,9 +9,6 @@
<!-- Import the base Ant build script... -->
<import file="../conf/base-build.xml"/>
- <!-- The ESB itself is started by the default "run" target - defined in base-build.xml -->
-
- <!-- Target for injecting the sample order message for transformation... -->
<target name="runtest" depends="compile"
description="runs Test JMS Sender">
<echo>Runs Test JMS Sender</echo>
Modified: labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_simple/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_simple/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_simple/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,74 +1,84 @@
Overview:
=========
- This is a very basic example of how to manually define and apply a Message Transformation
- within JBoss ESB 4.0GA. It applies a very simple XSLT to a SampleOrder.xml message and prints the
- before and after XML to the console.
-
- This Quickstart does not use the JBoss ESB Administration Console to manage the
- message Transformation configurations to the ESB. See the end of this README for details on how
- to manage this Quickstart's transformations via the Console.
-
- Check out the Administration Console Flash demos at:
- http://labs.jboss.com/portal/jbossesb/resources/tutorials/xformation-demos/console-demos.html
+ This is a very basic example of how to manually define and apply a Message
+ Transformation within JBoss ESB. It applies a very simple XSLT to a
+ SampleOrder.xml message and prints the before and after XML to the console.
+
+ This Quickstart does not use the JBoss ESB Administration Console to manage
+ the message Transformation configurations to the ESB. See the end of this
+ README for details on how to manage this Quickstart's transformations via the
+ Console.
+
+ Check out the Administration Console Flash demos at:
+ http://labs.jboss.com/portal/jbossesb/resources/tutorials/xformation-demos/console-demos.html
+Running this quickstart:
+========================
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
-Before Running:
-===============
- 1. Update the "org.jboss.esb.appserver.home" property in the quickstarts.properties file in "../".
- 2. Make sure to run the the ant script in the "install" folder of the distribution. This
- deploys the required SARs to your JBoss Application Server instance.
- 3. Make sure the JBoss Application server is running.
- 4. It would be a great idea to read MessageTransformation.pdf to fully understand this
- Quickstart. It is located in the docs/services folder.
+ A comprehensive description of message transformation can be found in
+ MessageTransformation.pdf, located in the docs/services folder.
+To Run standalone mode:
+=======================
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 4. Switch back to "Window1" to see the output from the ESB
+ 5. When finished, interrupt the ESB using Ctrl-C and, in this folder
+ ("Window1"), type 'ant undeploy-jms-dests'.
-To Run:
-=======
- 1. In a command terminal window in this folder ("Window1"), type "ant run".
- 2. Open another command terminal window in this folder ("Window2"), type "ant runtest".
- 3. Switch back to "Window1" to see the message transformation before and after.
-
- Note that, as with all these Quickstarts, you can deply and run them through your local
- JBoss Application Server instance. To do this, skip step 1 above and in it's place
- execute the following Ant task:
- "ant deployToSAR"
- This will packagce up this Quickstart and deploy it to your JBoss AS instance. The Quickstart
- "Service" will automatically start then. At that point, continue with steps 2 and 3.
+To Run '.esb' archive mode:
+===========================
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
-
What to look at in this Quickstart:
===================================
- As stated above, a read of MessageTransformation.pdf would be of great benefit in understanding
- JBoss ESB Transformations.
+ As stated above, reading MessageTransformation.pdf would be of great benefit
+ in understanding JBoss ESB Transformations.
- jbossesb.xml: The ESB configuration file in this Quickstart simply defines a JMS Listener for receiving
- the contents of the SampleOrder.xml file located in this folder (line 31). The listener
- configuration then executes the "SmooksTransformer" action for the Message Exchange between
- "A" and "B".
-
- smooks-cdr.lst: This file is used by the JBoss ESB Transformation Service to list the Transformation
- resource configuration URIs. Out of the box, the smoooks-cdr.lst file in this Quickstart
- refers to 2 resource URIs, both of which are classpath based. It also has a commented
- out listing for accessing Transformation Configurations managed by the JBoss ESB
- Administration Conosle (see below).
-
- smooks-res.xml: This file defines the Transformations for the Quickstart. In this case, it simply defines
- a single XSL transformation for the order line items.
+ jbossesb.xml:
+ The ESB configuration file in this Quickstart simply defines a JMS Listener
+ for receiving the contents of the SampleOrder.xml file located in this
+ folder (line 31). The listener configuration then executes the
+ "SmooksTransformer" action for the Message Exchange between "A" and "B".
+ smooks-cdr.lst:
+ This file is used by the JBoss ESB Transformation Service to list the
+ Transformation resource configuration URIs. Out of the box, the
+ smoooks-cdr.lst file in this Quickstart refers to 2 resource URIs, both of
+ which are classpath based. It also has a commented out listing for
+ accessing Transformation Configurations managed by the JBoss ESB
+ Administration Console (see below).
+ smooks-res.xml:
+ This file defines the Transformations for the Quickstart. In this case, it
+ simply defines a single XSL transformation for the order line items.
+
Playing with this Transformation through the Administration Console:
====================================================================
- To load the Transformation Configurations defined in smooks-res.xml into the Admin Console, and have them
- managed from the Admin Console, do the following:
-
- 1. Deploy the console as outlined in MessageTransformation.pdf.
- 2. Edit the smooks-cdr.lst file in this folder, commenting out both the classpath based listings and
- uncommenting out the listing for the console HTTP URI.
- 3. In the console:
- a) Add "Message Exchange Participants" for "A" and "B" through the "Manage Message Exchange Participants" form.
- b) Add new "Message Contract" against "A" and "B" for "text/xml:messageAtA" and "text/xml:messageAtB" respectively.
- Note: "messageAtA" and "messageAtB" are the Message Namespace values and "text/xml" is the Message Mime in
- both cases.
- c) Import "smooks-res.xml" through the "Import Configurations" form.
- 4. You are now ready to start managing the message transformations through the console. You can add more
- transformations and modify the existing transformations. Be sure to read MessageTransformation.pdf!!!
\ No newline at end of file
+ To load the Transformation Configurations defined in smooks-res.xml into the
+ Admin Console, and have them managed from the Admin Console, do the following:
+
+ 1. Deploy the console as outlined in MessageTransformation.pdf.
+ 2. Edit the smooks-cdr.lst file in this folder, commenting out both the
+ classpath based listings and uncommenting out the listing for the console
+ HTTP URI.
+ 3. In the console:
+ a) Add "Message Exchange Participants" for "A" and "B" through the "Manage
+ Message Exchange Participants" form.
+ b) Add new "Message Contract" against "A" and "B" for "text/xml:messageAtA"
+ and "text/xml:messageAtB" respectively.
+ Note: "messageAtA" and "messageAtB" are the Message Namespace values and
+ "text/xml" is the Message Mime in both cases.
+ c) Import "smooks-res.xml" through the "Import Configurations" form.
+ 4. You are now ready to start managing the message transformations through the
+ console. You can add more transformations and modify the existing
+ transformations.
\ No newline at end of file
Modified: labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/README.TXT
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/README.TXT 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/README.TXT 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,77 +1,62 @@
Overview:
=========
- This Quickstart demonsrates how the ActiveBPEL BPEL Engine can be used to
- orchestrate business process flow through JBoss ESB.
+ This Quickstart demonsrates how the ActiveBPEL BPEL Engine can be used to
+ orchestrate business process flow through JBoss ESB.
- It also demonstrates a number of other features of the ESB:
- 1. Exposing a Webservice interface for a Service that doesn't have a Webservice
- interface (using the JBossWSAdapter action). In this example, the Service being exposed
- is a legacy EJB based Order Management Service.
- 3. How to use a jaxb-intros.xml config to "Introduce" JAXB Annotations on a Java interface/typeset
- that isn't annotated for use with JAXB and how to add this config on a JBossWS
- Webservice endpoint deployment.
- 2. Easily transforming a CSV based notification message into a Java object that's then used
- to populate a SOAP request. See next.
- 3. Making an invocation on an external Webserivce from within an Action Processing
- Pipeline using the SOAPCleint action.
+ It also demonstrates a number of other features of the ESB:
+ 1. Exposing a Webservice interface for a Service that doesn't have a
+ Webservice interface (using the JBossWSAdapter action). In this example,
+ the Service being exposed is a legacy EJB based Order Management Service.
+ 2. How to use a jaxb-intros.xml config to "Introduce" JAXB Annotations on a
+ Java interface/typeset that isn't annotated for use with JAXB and how to
+ add this config on a JBossWS Webservice endpoint deployment.
+ 3. Easily transforming a CSV based notification message into a Java object
+ that's then used to populate a SOAP request. See next.
+ 3. Making an invocation on an external Webserivce from within an Action
+ Processing Pipeline using the SOAPCleint action.
- See docs folder.
+ See docs folder.
+Running this quickstart:
+========================
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
-Before Running:
-===============
- Setting up JBoss App Server (v4.2.0GA):
- 1. Stop the JBoss App Server.
- 2. Update the "org.jboss.esb.server.home" property in the quickstarts.properties
- file in "../conf".
- 3. Make sure you're running the ESB on JBoss AS v4.2.0GA.
- 4. Run the ant script in the install directory of the distribution. After running,
- check that the following ESB components are deployed to your JBoss AS.
- a) jbossesb.esb
- b) jbossesb.sar
- c) soap.esb
- d) soapui-client.sar
- e) smooks.esb
- 5. Download and install JBossWS 2.0.0GA (http://labs.jboss.com/jbossws) on your JBoss AS.
- NOTES:
- a) Once deployed, go to jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml on your
- App Server and add the following bean configuration:
- "<bean name="WSEndpointJAXBIntrosCustomizationsDeployer"
- class="org.jboss.wsf.spi.deployment.JAXBIntrosCustomizationsDeployer" />"
- b) Again in jboss-beans.xml, add a reference to the above bean config in the
- deployer list configured on the "WSMainDeployerManager" bean. E.g.:
- "<inject bean="WSEndpointJAXBIntrosCustomizationsDeployer"/>"
- Add this before the "inject" element for the "WSEndpointHandlerDeployer" bean.
- c) Copy "jbossesb/extras/jaxbintros/jboss-jaxb-intros.jar" to the root of the jbossws.sar
- service on your JBoss App Server. Note that if you haven't already done this you'll
- need to stop and restart the the App Server.
- d) Again in jboss-beans.xml, modify the "WSWebMetaDataAdapter" bean class to be
- "org.jboss.soa.esb.jbossws.ESBWebMetaDataAdapter".
- e) Copy soap.esb/jbossesb-soap.jar to jbossws.sar.
- 6. Start the JBoss App Server.
+ Note, this quickstart requires an ESB and JBossWS installation into
+ JBoss AS 4.2.0.GA. Installation instructions for both can be found in the
+ install/readme.txt.
- Setting up ActiveBPEL:
- 1. Ensure that the value of the 'directory' attribute on the 'notificationChannel' (jboss-esb.xml)
- matches the value of the 'order.approval.drop.location' property in
- 'webservice_bpel/services/order-manager/order-manager.properties'.
- 2. Make sure your Tomcat deployment at '${env.CATALINA_HOME}' is configured such that it's ports
- do not clash with those of your running JBoss AS. See '${env.CATALINA_HOME}/conf/server.xml'.
- 3. Make sure your Tomcat deployment at '${env.CATALINA_HOME}' is configured to listen for HTTP traffic
- on port 18080. See '${env.CATALINA_HOME}/conf/server.xml'.
- 4. Start your Tomcat deployment at '${env.CATALINA_HOME}'.
- 5. Goto 'Deployed Processes' on the BPEL Console (http://localhost:18080/BpelAdmin) and confirm that
- the 'Customer' and 'OrderProcess' BPEL processes are deployed.
+ Setting up ActiveBPEL:
+ 1. Ensure that the value of the 'directory' attribute on the
+ 'notificationChannel' (jboss-esb.xml) matches the value of the
+ 'order.approval.drop.location' property in
+ 'webservice_bpel/services/order-manager/order-manager.properties'.
+ 2. Make sure your Tomcat deployment at '${env.CATALINA_HOME}' is configured
+ such that it's ports do not clash with those of your running JBoss AS. See
+ '${env.CATALINA_HOME}/conf/server.xml'.
+ 3. Make sure your Tomcat deployment at '${env.CATALINA_HOME}' is configured to
+ listen for HTTP traffic on port 18080. See
+ '${env.CATALINA_HOME}/conf/server.xml'.
+ 4. Start your Tomcat deployment at '${env.CATALINA_HOME}'.
+ 5. Goto 'Deployed Processes' on the BPEL Console
+ (http://localhost:18080/BpelAdmin) and confirm that the 'Customer' and
+ 'OrderProcess' BPEL processes are deployed.
-
To Run:
=======
- 1. Run "ant clean deploy" from this folder and follow the instructions printed to the
- console at the end of the deploy.
- 2. Wait for the quickstart's .esb application to deploy on the App Server - watch the console.
- 3. Start your favorite SOAP client (e.g. SOAPUI) and load the 'RetailerService' WSDL (http://localhost:18080/active-bpel/services/RetailerService?wsdl).
- 4. Load the SOAP client with the sample order in 'bpel/resources/sampleData/submit-order-01.xml'.
- 5. Submit the new order using the SOAP UI client.
- 6. View the state of the new process in 'Active Processes' on the BPEL Console. Will appear as 'Running'.
- 7. Drill into the 'Running' OrderProcess process (select it).
- 8. Drill down, you will see that the process is waiting on an acknowledgement/notification from the OrderManager service (WaitForNotificationFromOrderManager).
- 9. Goto http://localhost:8080/order-manager/ (note, not port '18080'). From here, you can approve the order.
+ 1. In a command terminal window in this folder, type 'ant deploy'.
+ 2. Start your favorite SOAP client (e.g. SOAPUI) and load the
+ 'RetailerService' WSDL (http://localhost:18080/active-bpel/services/RetailerService?wsdl).
+ 3. Load the SOAP client with the sample order in
+ 'bpel/resources/sampleData/submit-order-01.xml'.
+ 4. Submit the new order using the SOAP UI client.
+ 5. View the state of the new process in 'Active Processes' on the BPEL
+ Console. Will appear as 'Running'.
+ 6. Drill into the 'Running' OrderProcess process (select it).
+ 7. Drill down, you will see that the process is waiting on an
+ acknowledgement/notification from the OrderManager service
+ (WaitForNotificationFromOrderManager).
+ 8 Goto http://localhost:8080/order-manager/ (note, not port '18080').
+ From here, you can approve the order.
+ 9. When finished, undeploy the application by typing 'ant undeploy'.
+
\ No newline at end of file
Modified: labs/jbossesb/trunk/product/samples/quickstarts/webservice_producer/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/webservice_producer/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/webservice_producer/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,45 +1,21 @@
Overview:
=========
- This sample demonstrates how to deploy a JSR181 Webservice endpoint on JBossESB
- using the SOAPProcessor action.
+ This sample demonstrates how to deploy a JSR181 Webservice endpoint on
+ JBossESB using the SOAPProcessor action.
+Running this quickstart:
+========================
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
-Before Running:
-===============
-1. Update the "org.jboss.esb.server.home" property in the quickstarts.properties
- file in "../conf".
-2. Make sure you're running the ESB on JBoss AS v4.2.0GA.
-3. Run the ant script in the install directory of the distribution. After running,
- check that the following ESB components are deployed to your JBoss AS.
- a) jbossesb.esb
- b) jbossesb.sar
- c) soap.esb
-4. Download and install JBossWS 2.0.0GA (http://labs.jboss.com/jbossws)
- jbossws-native-2.0.0.GA.zip on your JBoss AS. The instructions for JBossWS 2.0.0.GA
- deployment can be found at jbossws-native-2.0.0.GA\docs\Install.txt
- NOTES:
- a) Once deployed, go to jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml on your
- App Server and add the following bean configuration:
- "<bean name="WSEndpointJAXBIntrosCustomizationsDeployer"
- class="org.jboss.wsf.spi.deployment.JAXBIntrosCustomizationsDeployer" />"
- b) Again in jboss-beans.xml, add a reference to the above bean config in the
- deployer list configured on the "WSMainDeployerManager" bean. E.g.:
- "<inject bean="WSEndpointJAXBIntrosCustomizationsDeployer"/>"
- Add this before the "inject" element for the "WSEndpointHandlerDeployer" bean.
- c) Copy "jbossesb/extras/jaxbintros/jboss-jaxb-intros.jar" to the root of the jbossws.sar
- service on your JBoss App Server. Note that if you haven't already done this you'll
- need to stop and restart the the App Server.
- d) Again in jboss-beans.xml, modify the "WSWebMetaDataAdapter" bean class to be
- "org.jboss.soa.esb.jbossws.ESBWebMetaDataAdapter".
- e) Copy soap.esb/jbossesb-soap.jar to jbossws.sar.
-5. Start the JBoss App Server.
+ Note, this quickstart requires an ESB and JBossWS installation into
+ JBoss AS 4.2.0.GA. Installation instructions for both can be found in the
+ install/readme.txt.
-
To Run:
=======
-1. In the first command window, execute "ant clean deploy". This will compile the project, build
- the needed jars and deploy the ESB archive component to the Application Server.
-
-2. Run "ant runtest". You will see the message being processed on the App Server
- Java console window.
-
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant runtest'.
+ 3. Switch back to Application Server console to see the output from the ESB
+ 4. In this folder ("Window1"), type 'ant undeploy'.
Modified: labs/jbossesb/trunk/product/samples/quickstarts/wiretap/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/wiretap/readme.txt 2007-07-19 11:56:11 UTC (rev 13632)
+++ labs/jbossesb/trunk/product/samples/quickstarts/wiretap/readme.txt 2007-07-19 12:58:21 UTC (rev 13633)
@@ -1,161 +1,89 @@
Overview:
=========
- The purpose of the wiretap quickstart sample is demonstrate
- the wiretap J2EE pattern (as defined here:
- http://www.enterpriseintegrationpatterns.com/WireTap.html) using a
- static router as implemented in org.jboss.soa.esb.actions.StaticRouter
- and a content based router (CBR) as implemented in
- org.jboss.soa.esb.actions.ContentBasedRouter
+ The purpose of the wiretap quickstart sample is demonstrate the wiretap J2EE
+ pattern (http://www.enterpriseintegrationpatterns.com/WireTap.html) using a
+ static router as implemented in org.jboss.soa.esb.actions.StaticRouter and a
+ content based router (CBR) as implemented in
+ org.jboss.soa.esb.actions.ContentBasedRouter
Running this quickstart:
========================
- Please refer to 'ant help-quickstarts' for prerequisites about the
- quickstarts and a more detailed descripton of the different ways to
- run the quickstarts.
+ Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
+ and a more detailed descripton of the different ways to run the quickstarts.
To Run standalone mode:
=======================
- 1. In a command terminal window in the quickstart folder type 'ant deploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
- 3. Open another command terminal window in this folder (Window2"), type ant receive-destination'
- 4. Open another command terminal window in this folder (Window3"), type ant receive-wiretap'
- 5. Open another command terminal window in this folder ("Window4"), type 'ant runtest-cbr'.
- (Note the other ant targets listed below.)
- 6. Switch back to "Window1", "Window2", and "Window3" to see the output from the ESB
+ 1. In a command terminal window in the quickstart folder type
+ 'ant deploy-jms-dests'.
+ 2. In a command terminal window in this folder ("Window1"), type 'ant run'.
+ 3. Open another command terminal window in this folder ("Window2"), type
+ 'ant receive-destination'.
+ 4. Open another command terminal window in this folder ("Window3"), type
+ 'ant receive-wiretap'.
+ 5. Open another command terminal window in this folder ("Window4"), type
+ 'ant runtest-cbr'.
+ 6. Switch back to "Window1", "Window2" and "Window3" to see the output from
+ the ESB
+ 7. When finished, interrupt the ESB and receivers using Ctrl-C.
+ 8. Undeploy the JMS configuration, type 'ant undeploy-jms-dests'.
+
To Run '.esb' archive mode:
===========================
- 1. In a command terminal window in this folder ("Window1"), type 'ant undeploy-jms-dests'.
- 2. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
- 3. Open another command terminal window in this folder (Window2"), type ant receive-destination'
- 4. Open another command terminal window in this folder (Window3"), type ant receive-wiretap'
- 5. Open another command terminal window in this folder ("Window4"), type 'ant runtest-cbr'.
- (Note the other ant targets listed below.) You can modify the "routeToFollow" element
- value in SampleOrder.xml to control the path that is followed thru the CBR. The valid
- values are: "regular,", "wiretap," and "both."
- 6. Switch back to "Window1", "Window2", and "Window3" to see the output from the ESB
+ 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
+ 2. Open another command terminal window in this folder ("Window2"), type
+ 'ant receive-destination'.
+ 3. Open another command terminal window in this folder ("Window3"), type
+ 'ant receive-wiretap'.
+ 4. run the test ("Window1"), type 'ant runtest-cbr'.
+ 5. Switch back to Application Server, "Window2" and "Window3" to see the output from
+ the ESB
+ 6. When finished, interrupt the receivers using Ctrl-C.
+ 7. Undeploy the esb archive, type 'ant undeploy'.
- The quickstart makes use of the queues illustrated (the queues are shown
- in boxes) in the following diagram. You might review the build.xml file to
- see how it is setup. More details on the build.xml can be found later in
- this document. You can modify the build.xmlto change the phrase sent in the messages.
+Things to Consider:
+===================
+ The quickstart makes use of the queues illustrated (the queues are shown
+ in boxes) in the following diagram. You might review the build.xml file to
+ see how it is setup. More details on the build.xml can be found later in
+ this document. You can modify the build.xmlto change the phrase sent in the
+ messages.
- application initiated
- |
- |
- V
- -------------------------- ----------------------------
- |qswiretap_wire_GWRequest| ---> |qswiretap_wire_out_Request|---> wiretap output
- -------------------------- ----------------------------
- |
- |
- V
- ---------------------------
- |qswiretap_regular_Request|
- ---------------------------
- |
- |
- V
- destination output
+ application initiated
+ |
+ |
+ V
+ -------------------------- ----------------------------
+ |qswiretap_wire_GWRequest| --> |qswiretap_wire_out_Request|--> wiretap output
+ -------------------------- ----------------------------
+ |
+ |
+ V
+ ---------------------------
+ |qswiretap_regular_Request|
+ ---------------------------
+ |
+ |
+ V
+ destination output
Project File Descriptions
=========================
-
- * jbossesb.xml - the JMS gateway and ESB configuration file.
+ You can modify the "routeToFollow" element value in SampleOrder.xml to control
+ the path that is followed thru the CBR. The valid values are: "regular,",
+ "wiretap," and "both."
- * jbossesb-properties.xml - also needed by jUDDI and needs to
- be at the head of the classpath. Both juddi.properties and
- jbossesb-properties.xml are used when the service first
- boots up for self-registration based upon the
- service-category and service-name found in the
- esb-config.xml file.
+ * build.xml - The following targets are also supported
+ * runtest - send message through the gateway listener in MyJMSListener
+ directly to destination queue, bypasses wiretap completely.
- * jndi.properties - needed primarily for
- quickstart.test.SendJMSMessage that is fired by ant runtest.
+ * wiretap - send message through the gateway listener MyJMSWiretapListener
+ to wiretap output queue
- * log4j.xml - needed to configure log4J used by both the
- quickstart and the ESB itself. A listener needs a place to
- log.
+ * static-router - send message through the static router gateway in
+ org.jboss.soa.esb.actions.StaticRouter to both wiretap output queue and
+ destination queue
- * src\quickstart\staticrouter\test\SendJMSMessage.java -
- shoots in the string passed in via the command line or in
- this case the arg attribute in the ant runtest task.
-
- * src\quickstart\staticrouter\test\SendWireJMSMessage.java -
- shoots in the string to the wiretap passed in via the
- command line or in this case the arg attribute in the ant
- wiretap task.
-
- * src\quickstart\staticrouter\test\SendTestJMSMessage.java -
- shoots in the string to the static router passed in via the
- command line or in this case the arg attribute in the ant
- static-router task.
-
- * src\quickstart\staticrouter\test\SendCBRJMSMessage.java -
- shoots in the string to the CBR router in the ant
- runtest-cbr task.
-
- * src\quickstart\staticrouter\test\ReceiveJMSMessage.java -
- reads the output queues and displays the messages.
-
- * src\quickstart\services\rules\MyESBRules-XPath.drl - JBoss
- Rules definition file
-
- * build.xml - This quickstart implements the following tasks:
-
- * runtest - send message thru gateway listener in
- MyJMSListener directly to destination queue,
- bypasses wiretap completely
-
- * wiretap - send message thru gateway listener in
- MyJMSWiretapListener to wiretap output queue
-
- * static-router - send message thru static router
- gateway in org.jboss.soa.esb.actions.StaticRouter to
- both wiretap output queue and destination queue
-
- * runtest-cbr - send message thru CBR router gateway
- in org.jboss.soa.esb.actions.ContentBasedRouter to
- both wiretap output queue and destination queue
-
- * config - copies the JBoss Rules file into
- /build/classes
-
- * quickstart-specific-deploys - creates the JBoss
- Rules jar file
-
- * the echoCP task is useful for making sure what you
- think is in your classpath is actually in your
- classpath Usage is: ant echoCP > myclasspath.txt
- This generates a file called myclasspath.txt which
- can be reviewed in a text editor
-
- In order to run the tests, you must first run these
- ant tasks - in this order:
-
- * ant compile
- * ant config
- * ant quickstart-specific-deploys
- * ant deploy
-
- This quickstart uses the queues called:
-
- * qswiretap_static_router_Request - Where the
- message enters the wiretap static router
-
- * qswiretap_regular_Request - The application
- destination for the message
-
- * qswiretap_wire_GWRequest - Where the message
- enters the wiretap via a gateway listener
-
- * qswiretap_wire_out_Request - Where the message
- exits the wiretap and can be processed by wiretap
- processes
-
- * qswiretap_cbr_Request - Where the message enters
- the wiretap CBR router
-
- * the classpath property pulls the
- jbossesb-properties.xml file and the
- juddi.properties file to the front of the list
+ * runtest-cbr - send message throught the CBR router gateway in
+ org.jboss.soa.esb.actions.ContentBasedRouter to both wiretap output queue
+ and destination queue
More information about the jboss-svn-commits
mailing list