3 comments
Comment actions Permalink

How are you deploying, remote debugging, etc.


I use both Jboss 2.4.6 and JBoss 3 RC2 with IDEA.

RUNNING JBOSS
=============
For both, I made seperate run.bat and debug.bat files (debug.bat is the same
as run.bat, but with JPDA options enabled...debugging mode slows down JBoss
considerably, so I don't use it often.) I set up JBoss 3 run/debug/shutdown
as 3 External tools, and use them to run the program inside IDEA. As
there's no way to break JBoss neatly from within IDEA, you have to use
shutdown.bat to close it, thus its inclusion as a tool. Since JBoss2 lacks
this file, I just use a DOS window for it, so that I can trigger a shutdown
with ctrl-C. Then I just set up IDEA for remote debugging with the
appropriate port and localhost and I'm good to go - works fine for both
versions.

DEPLOYMENT
==========
We use ant to build and deploy the jars regardless of dev environment, just
use the jboss(3).home property, and set that in IDEA from the ant window to
the appropriate location, then copy the built ear to
{jboss3.home}/server/default/deploy, or whatever the appropriate place is
for JBoss2, I forgot. Works great; when running, JBoss picks up updates and
redeploys, so I only need to restart the server program occasionally.

-Walter Mundt



0
Comment actions Permalink

Thanks! I'll try out your suggestion.

Walter Mundt wrote:

>>How are you deploying, remote debugging, etc.
>>


I use both Jboss 2.4.6 and JBoss 3 RC2 with IDEA.

RUNNING JBOSS
=============
For both, I made seperate run.bat and debug.bat files (debug.bat is the same
as run.bat, but with JPDA options enabled...debugging mode slows down JBoss
considerably, so I don't use it often.) I set up JBoss 3 run/debug/shutdown
as 3 External tools, and use them to run the program inside IDEA. As
there's no way to break JBoss neatly from within IDEA, you have to use
shutdown.bat to close it, thus its inclusion as a tool. Since JBoss2 lacks
this file, I just use a DOS window for it, so that I can trigger a shutdown
with ctrl-C. Then I just set up IDEA for remote debugging with the
appropriate port and localhost and I'm good to go - works fine for both
versions.

DEPLOYMENT
==========
We use ant to build and deploy the jars regardless of dev environment, just
use the jboss(3).home property, and set that in IDEA from the ant window to
the appropriate location, then copy the built ear to
{jboss3.home}/server/default/deploy, or whatever the appropriate place is
for JBoss2, I forgot. Works great; when running, JBoss picks up updates and
redeploys, so I only need to restart the server program occasionally.

-Walter Mundt




0
Comment actions Permalink

>How are you deploying, remote debugging, etc.

Just a thought about "etc".

When you browse JBoss sources, I believe IDEA is a perfect IDE.
JBoss architecture is based on JMX and it has many invoke() calls in the sources(eg. 3310 occurences in JBoss 3.0.1).
With IDEA, you could search them effectively by "Find Usages".
For example I get 8 usages in 5 files for Container::invoke(). :)

0

Please sign in to leave a comment.