User: jwalters Date: 02/02/04 19:30:14 Modified: src/xdocs/howto howtonetbeansdebug.xml Log: Updated to JBoss 2.4 (somehow previous update was lost). Revision Changes Path 3.2 +30 -28 manual/src/xdocs/howto/howtonetbeansdebug.xml Index: howtonetbeansdebug.xml =================================================================== RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtonetbeansdebug.xml,v retrieving revision 3.1 retrieving revision 3.2 diff -u -r3.1 -r3.2 --- howtonetbeansdebug.xml 2001/12/08 03:54:46 3.1 +++ howtonetbeansdebug.xml 2002/02/05 03:30:14 3.2 @@ -24,15 +24,17 @@ <title>Install the JBoss Server</title> <para> For the purpose of this howto, I installed the JBossTomcat release version -2.2.2 into d:\JBoss-2.2.2_Tomcat-3.2.2. Download it from -http://www.jboss.org and select the binary link from the page. Don't worry -about downloading a binary package, when all you want is the source code; -the binary package also contains the source code used for building. +2.4.4/3.2.3 into /opt/appserver on my linux box. If you translate the steps +into Windows NT/2000 you can also debug JBoss apps using Netbeans there. +Download it from http://www.jboss.org and select the binary link from the +page. Don't worry about downloading a binary package, when all you want is +the source code; the binary package also contains the source code used for +building. </para> </section> <section> <title>Create a NetBeans Project</title> -<para>Start NetBeans, I used NetBeans 3.2 while writing this howto. The first +<para>Start NetBeans, I used NetBeans 3.3 while writing this howto. The first step is to create a new project or open an existing project. You create a new project from the Project -> Project Manager menu selection. This dialog will show a list of your projects like: @@ -48,14 +50,14 @@ project you should go to the explorer window and select the FileSystems tab. Either right click on the FileSystems entry in the explorer window, or choose File -> Mount Filesystem and pick mount jar. Use the browser or type in the -path for the following jar files: jboss/lib/jdbc2_0-stdext.jar and -jboss/lib/ext/ejb.jar. If you use bean managed transactions you will need to -add jboss/lib/ext/jta-spec1_0_1.jar. If you are using JBossSX security then -you'll also need to add additional jar files jboss/lib/jaas.jar, jboss/lib/jboss-jaas.jar and jboss/lib/ext/jbosssx.jar. If you are using JMS from your -client you'll also need to add jboss/lib/ext/jms.jar and -jboss/lib/ext/jbossmq-client.jar. Once you have -added all these jar files if you don't want them to show in the explorer you can -right click on them one by one and from the properties panel select hidden=true. +path for the following jar files: jboss/lib/ext/jboss-j2ee.jar and +jboss/lib/jboss-jdbc_ext.jar. If you are using JBossSX security then you'll +also need to add additional jar files jboss/lib/jaas.jar, +jboss/lib/jboss-jaas.jar and jboss/lib/ext/jbosssx.jar. +If you are using JMS from your client you'll also need to add +jboss/lib/ext/jbossmq-client.jar. Once you have added all these jar files a +if you don't want them to show in the explorer you can right click on them +one by one and from the properties panel select hidden=true. </para> <para> At this point you need to add any other jar files specific to your app which @@ -140,14 +142,6 @@ </imageobject></mediaobject> </section> <section> -<title>Sprinkle breakpoints throughout your EJB and or Client Code</title> -<para> -First it is necessary to put breakpoints in your ejb's. As outlined -previously project settings should point to the source of your beans. Open -up a typical bean implementation and place breakpoints whereever desired. -</para> -</section> -<section> <title>Start the JBoss server</title> <para> Start JBoss using the debug script which you previously created. Deploy the @@ -158,12 +152,18 @@ </para> </section> <section> -<title>Deploy the Beans</title> +<title>Sprinkle breakpoints throughout your EJB and or Client Code</title> <para> -Copy or drag/drop (for windoze fans) the ejb jar file containing the -ejb-jar.xml and jboss.xml (optional) to the deploy folder. If you have set -breakpoints in stateless session ejb's these should cause the debugger to -stop in your code! Hurrah! +Before you can debug, it is necessary to put breakpoints into your code. On +the client side you can just open up your source files and toggle breakpoints +as in any other Netbeans debugging effort. To put breakpoins into your ejb's +is different. You will need to use the loaded classes menus to select the +class and method you would like to break on. Once you have hit a break point +within the class, and the source code is displayed, then you can add +additional breakpoints. This seems to be an artifact of the class loading +scheme used by JBoss, and a problem within NetBeans where it puts a breakpoint +on the system classloader when you just open the source file and toggle a +breakpoint. </para> </section> <section> @@ -176,9 +176,11 @@ are somewhat short so if you spend too much time in a method within the EJB you may find that transactions are rolled back. </para> +</section> +<section> +<title>Feedback</title> <para> If anyone has suggestions of feedback please let me know, I can be contacted -via email at [EMAIL PROTECTED] +via email at [EMAIL PROTECTED] </para> -</section> </section>
_______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
