[jboss-svn-commits] JBL Code SVN: r16164 - in labs/jbossesb/trunk/product/samples/quickstarts: jms_topic and 5 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Tue Oct 30 11:15:25 EDT 2007
Author: kurt.stam at jboss.com
Date: 2007-10-30 11:15:25 -0400 (Tue, 30 Oct 2007)
New Revision: 16164
Added:
labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/oracle-aq/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/jms_topic/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/webservice_mtom/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/webservice_wsaddressing/readme.txt
labs/jbossesb/trunk/product/samples/quickstarts/webservice_wssecurity/readme.txt
Removed:
labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/oracle-aq/README.txt.tmp
labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/README.txt.tmp
labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/README.TXT.tmp
Log:
JBESB-1232, adding readme.txt (all lowercase) files for every QS
Deleted: labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/oracle-aq/README.txt.tmp
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/oracle-aq/README.txt.tmp 2007-10-30 15:02:39 UTC (rev 16163)
+++ labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/oracle-aq/README.txt.tmp 2007-10-30 15:15:25 UTC (rev 16164)
@@ -1,34 +0,0 @@
-To run with Oracle AQ as your JMS provider you will need to follow the following steps:
-
-1. Using the Oracle Enterprise Manager Console create 3 queues named:
- ACTION_REQUEST, B and HELLO_WORLD_ACTION, make sure to set
- the payload type to Object: SYS, AQ$_JMS_MESSAGE.
-
-2. Edit the jndi.properties file to reflect your database connection settings
-
-3. Copy the jndi.properties and the jboss-esb.xml in the helloworld_action directory.
-
-4. From the lib/ext/jms/oracleaq directory copy the following jars in to the
- helloworld_action/lib directory
-
- 26747 Mar 18 18:16 asm.jar
- 286330 Mar 18 18:16 cglib-2.1_2jboss.jar
- 120342 Aug 4 2006 mockejb.jar
- 8757 Apr 4 14:13 org.jboss.soa.esb.oracle.aq-4.2.MR2.jar
-
- and obtain the following jars from your Oracle DB install:
-
- 772466 Mar 27 11:14 aqapi13.jar (from oracle)
-1397543 Mar 27 11:13 ojdbc14.jar (from oracle)
-
-
-Note that
-
-1. Oracle AQ is using a database connection as it's JMS connection.
-2. Oracle AQ does not have a JNDI provider and it is common to register
- Queues in an LDAP. Here we chose to register the Queues to MockContext
- which is why you need the mockejb.jar, as well as the asm and cglib jars
- that it depends on. The org.jboss.soa.esb.oracle.aq-4.2.MR2.jar plugin
- does the actual work of registering. Registering to JNP proved not
- possible because of code in the Oracle API to support option 1, the LDAP
- registration.
\ No newline at end of file
Copied: labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/oracle-aq/readme.txt (from rev 16163, labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/oracle-aq/README.txt.tmp)
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/oracle-aq/readme.txt (rev 0)
+++ labs/jbossesb/trunk/product/samples/quickstarts/helloworld_action/oracle-aq/readme.txt 2007-10-30 15:15:25 UTC (rev 16164)
@@ -0,0 +1,34 @@
+To run with Oracle AQ as your JMS provider you will need to follow the following steps:
+
+1. Using the Oracle Enterprise Manager Console create 3 queues named:
+ ACTION_REQUEST, B and HELLO_WORLD_ACTION, make sure to set
+ the payload type to Object: SYS, AQ$_JMS_MESSAGE.
+
+2. Edit the jndi.properties file to reflect your database connection settings
+
+3. Copy the jndi.properties and the jboss-esb.xml in the helloworld_action directory.
+
+4. From the lib/ext/jms/oracleaq directory copy the following jars in to the
+ helloworld_action/lib directory
+
+ 26747 Mar 18 18:16 asm.jar
+ 286330 Mar 18 18:16 cglib-2.1_2jboss.jar
+ 120342 Aug 4 2006 mockejb.jar
+ 8757 Apr 4 14:13 org.jboss.soa.esb.oracle.aq-4.2.MR2.jar
+
+ and obtain the following jars from your Oracle DB install:
+
+ 772466 Mar 27 11:14 aqapi13.jar (from oracle)
+1397543 Mar 27 11:13 ojdbc14.jar (from oracle)
+
+
+Note that
+
+1. Oracle AQ is using a database connection as it's JMS connection.
+2. Oracle AQ does not have a JNDI provider and it is common to register
+ Queues in an LDAP. Here we chose to register the Queues to MockContext
+ which is why you need the mockejb.jar, as well as the asm and cglib jars
+ that it depends on. The org.jboss.soa.esb.oracle.aq-4.2.MR2.jar plugin
+ does the actual work of registering. Registering to JNP proved not
+ possible because of code in the Oracle API to support option 1, the LDAP
+ registration.
\ No newline at end of file
Added: labs/jbossesb/trunk/product/samples/quickstarts/jms_topic/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/jms_topic/readme.txt (rev 0)
+++ labs/jbossesb/trunk/product/samples/quickstarts/jms_topic/readme.txt 2007-10-30 15:15:25 UTC (rev 16164)
@@ -0,0 +1 @@
+Please see the README.html
\ No newline at end of file
Deleted: labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/README.txt.tmp
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/README.txt.tmp 2007-10-30 15:02:39 UTC (rev 16163)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/README.txt.tmp 2007-10-30 15:15:25 UTC (rev 16164)
@@ -1,93 +0,0 @@
-Overview:
-=========
- 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).
-
- 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.
-
- 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, 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-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!!!
Copied: labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/readme.txt (from rev 16163, labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/README.txt.tmp)
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/readme.txt (rev 0)
+++ labs/jbossesb/trunk/product/samples/quickstarts/transform_XML2XML_date_manipulation/readme.txt 2007-10-30 15:15:25 UTC (rev 16164)
@@ -0,0 +1,93 @@
+Overview:
+=========
+ 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).
+
+ 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.
+
+ 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, 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-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!!!
Deleted: labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/README.TXT.tmp
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/README.TXT.tmp 2007-10-30 15:02:39 UTC (rev 16163)
+++ labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/README.TXT.tmp 2007-10-30 15:15:25 UTC (rev 16164)
@@ -1,72 +0,0 @@
-Overview:
-=========
- 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.
- 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.
-
-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.1.GA. Installation instructions for both can be found in the
- install/readme.txt.
-
- NOTE: This Quickstart DOES NOT run Standalone, or on the ESB Server. It only runs on the
- JBoss Application Server (v4.2.xGA).
-
- The ActiveBPEL Engine (v3.1) must now be installed on an instance of Tomcat on your
- system. The processes in this Quickstart are pre-built to run on version 3.1 of
- the ActiveBPEl Engine. If you are running on a newer version of the ActiveBPEL
- Engine, you may need to redeploy these processes. Version 3.1 of the ActiveBpel Engine
- can be downloaded from:
- http://www.active-endpoints.com/active-bpel-engine-download.htm#final31
-
- 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. 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 (RetailerServiceBinding/SubmitOrder) 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
Copied: labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/readme.txt (from rev 16163, labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/README.TXT.tmp)
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/readme.txt (rev 0)
+++ labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/readme.txt 2007-10-30 15:15:25 UTC (rev 16164)
@@ -0,0 +1,72 @@
+Overview:
+=========
+ 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.
+ 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.
+
+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.1.GA. Installation instructions for both can be found in the
+ install/readme.txt.
+
+ NOTE: This Quickstart DOES NOT run Standalone, or on the ESB Server. It only runs on the
+ JBoss Application Server (v4.2.xGA).
+
+ The ActiveBPEL Engine (v3.1) must now be installed on an instance of Tomcat on your
+ system. The processes in this Quickstart are pre-built to run on version 3.1 of
+ the ActiveBPEl Engine. If you are running on a newer version of the ActiveBPEL
+ Engine, you may need to redeploy these processes. Version 3.1 of the ActiveBpel Engine
+ can be downloaded from:
+ http://www.active-endpoints.com/active-bpel-engine-download.htm#final31
+
+ 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. 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 (RetailerServiceBinding/SubmitOrder) 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
Added: labs/jbossesb/trunk/product/samples/quickstarts/webservice_mtom/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/webservice_mtom/readme.txt (rev 0)
+++ labs/jbossesb/trunk/product/samples/quickstarts/webservice_mtom/readme.txt 2007-10-30 15:15:25 UTC (rev 16164)
@@ -0,0 +1 @@
+Please see the README.html
\ No newline at end of file
Added: labs/jbossesb/trunk/product/samples/quickstarts/webservice_wsaddressing/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/webservice_wsaddressing/readme.txt (rev 0)
+++ labs/jbossesb/trunk/product/samples/quickstarts/webservice_wsaddressing/readme.txt 2007-10-30 15:15:25 UTC (rev 16164)
@@ -0,0 +1 @@
+Please see the README.html
\ No newline at end of file
Added: labs/jbossesb/trunk/product/samples/quickstarts/webservice_wssecurity/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/webservice_wssecurity/readme.txt (rev 0)
+++ labs/jbossesb/trunk/product/samples/quickstarts/webservice_wssecurity/readme.txt 2007-10-30 15:15:25 UTC (rev 16164)
@@ -0,0 +1 @@
+Please see the README.html
\ No newline at end of file
More information about the jboss-svn-commits
mailing list