Here's how I'm using JB 4.0 Foundation:
1. I'm using 3 projects
1 to edit/compile EJBs. This project is used because JBuilder
adds the project's target class directory to the classpath, which I am
afraid would screw up JBoss because it loads the EJB classes using an
different classloader. Perhaps a misunderstanding on my part, but it works.
1 to run JBoss and, hence, my EJB beans
1 to run the client (either a standalone client or a servlet engine)
2. The EJB edit/compile project is set up as follows:
- Required libraries contain the following classes :
<jboss-home>/dist/conf/default, <jboss-home>/dist/bin/run.jar,
<jboss-home>/dist/lib/jdbc2_0stdext.jar,
<jboss-home>/dist/lib/jboss-jaas.jar, jaas.jar,
<jboss-home>/dist/lib/ext/ejb.jar
3. The JBossServer project is set up as follows:
- Working directory: <jboss-home>/dist/bin
- Run tab/Main class: org.jboss.Main
- VM parameters: -classic -Xms64m -Xmx96m
-Duser.dir=d:\cvs-root\jboss\dist\bin
- Required libraries contain the following classes :
<jboss-home>/dist/conf/default, <jboss-home>/dist/bin/run.jar,
<jboss-home>/dist/lib/jdbc2_0stdext.jar,
<jboss-home>/dist/lib/jboss-jaas.jar, jaas.jar,
<jboss-home>/dist/lib/ext/ejb.jar
...in addition, add a JB required library that contains
the sources (not the classes) of your EJB beans. This will allow you to
set breakpoints, etc. in those beans.
4. Client application (here's my standalone client setup):
- Required libraries (classes): all the jars in JBoss client
directory, and your EJB Bean interface files (note, you can include all the
EJB files here, it won't hurt you)
Once you have the applications set up, you can edit/compile your EJBs in
the first project. When they compile correctly, JAR them with appropriate
JBoss and EJB descriptor files and copy the JAR to the JBoss deploy
directory to deploy. Then you can start up the JBoss server (your second
project) in the JB debugger. This should start up without errors, and
should deploy your beans. Assuming they deploy successfully, you can start
up the 3rd project in the debugger. You should now be able to set
breakpoints in both the client and server and debug. Also, if you want to
debug into the JBoss code, add the JBoss source files to your JBossServer
required library's sources tab.
Hope this helps,
Rick
At 05:58 PM 12/14/00 -0500, you wrote:
>If any one has managed to successfully used an IDE like CodeGuide or
>Jbuilder to debug an app running in Jboss, I would sure appreciate it if
>you could provide a detailed cookbook. I've refered to the documentation
>page on using Jbuilder 3.5 (I have 4.0) but haven't been able to make
>headway.
>
>I would imagine that there are others out there who would appreciate it
>also.
>
>Thanx
>
>chaz
>--
>Charles E Brault
>[EMAIL PROTECTED]
>202-342-8070x238 202-342-8078 (f) 301-351-9186 (c)
>
>
>--
>--------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Problems?: [EMAIL PROTECTED]
--------------------
Rick Horowitz
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
