[jboss-svn-commits] JBL Code SVN: r5591 - labs/jbossesb/trunk/product

[jboss-svn-commits at lists.jboss.org]

Author: mark.little at jboss.com
Date: 2006-08-08 05:01:04 -0400 (Tue, 08 Aug 2006)
New Revision: 5591

Modified:
   labs/jbossesb/trunk/product/Build.txt
Log:


Modified: labs/jbossesb/trunk/product/Build.txt
===================================================================
--- labs/jbossesb/trunk/product/Build.txt	2006-08-08 02:20:20 UTC (rev 5590)
+++ labs/jbossesb/trunk/product/Build.txt	2006-08-08 09:01:04 UTC (rev 5591)
@@ -2,4 +2,72 @@
 in the build can be set for convenience. The lib/ext directory contains the most recently tested
 libs needed to build the system. You are free to use these, or your own versions of the jars
 from a JBossAS 4.0.3SP1 installation. If the latter, then set org.jboss.esb.frominstall to true
-and org.jboss.esb.jboss.home to the root of your JBossAS installation.
\ No newline at end of file
+and org.jboss.esb.jboss.home to the root of your JBossAS installation.
+
+Getting started for the impatient.
+
+1. Download jboss-4.0.4.GA-Patch1-installer.jar.
+
+2. During the install check the ejb3 radio button (important, or you 
+will have no ejb3 support!)
+
+3. Get the JbossESB codebase from SVN. (If you're a JBossIDE fan like me 
+and you want some help setting up the build path
+you can copy the IDE/JBossIDE/.classpath into the root of your project)
+
+4. In the product/config directory copy the deployment.property-example 
+to deployment.properties.
+You can customize the deployment.properties file. If you have commit 
+rights; please don't check
+this file back in as it contains *your* deployment settings not mine :).
+
+5. Now from this config directory run
+
+ant configure.jboss.
+
+This will do *all* the configuration work. Yes it's that easy!
+
+6. Now go back up one level and do
+
+ant deploy
+
+This compiles the code and produces 4 jars and an ear in 
+product/build/dist/lib.
+The ear gets deployed to jboss. (AppServer specified in your 
+deployment.properties).
+
+7. start jboss.
+
+
+
+Getting started with the Trail blazer with JBossIDE..
+
+1. Create a new project by checking out the bankloanbrokerdemo in 
+product/docs/samples/trailblazer.
+Again you can get help with the classpath, see the 
+IDE/JBossIDE/.classpath in the bankloanbrokerdemo dir.
+For this to work you need to set
+- a variable called JBOSS_HOME which points to where you installed JBoss
+- a variable called ESB_HOME which points to the root of your ESB source 
+tree product/build/dist/lib dir.
+
+2. Go to the bankloanbrokerdemo/banks directory and launch the banks:
+
+ant runFileBank
+ant runJMSBank
+
+3. You are now ready to start the JMS listener for the demo by right 
+clicking on LauchDummy.java (can we fix this name??) In the
+src/java/org/jboss/soa/esb/samples/loanbroker/web directory, and 
+selecting 'Run As (or Debug As) Java Application.
+By default it reads it configuration from conf/LoanBrokerConfig.xml.
+
+4. You can send in a WS request, but running the LoanBrokerWS.java. This 
+sends a loan request for John Doe
+as specified in the main() of this class.
+
+5. This is where the demo currently blows up :( boohoo.. The JMS bank 
+receives a  SpyObjectMessage and expects a TextMessage
+We will be working on this tomorrow. Stay tuned for more! I will also 
+work on a
+ant build script to start the demo from the cmdline.