| Can override/debug a deployed ear? [message #12313] |
Fri, 02 May 2003 09:57  |
Eclipse User |
|
|
|
Originally posted by: Joseph.Herbers.eds.com
Question: can I update/debug class files in Eclipse without rebuilding and
redeploying the EAR file in JBoss? I've been unsuccessful with both the
JBoss IDE and the EASIE plugins. FYI this worked for us when using
Together.
Using the EASIE JBoss plugin for Eclipse: I got it installed and mostly
working. I can debug my deployed EAR ok as long as I don't change the
source (can't seem to do even that in JBoss IDE). If I'm in 1.4.1 and
change the source, hot deploy works and I can continue running or debugging.
However, if I restart JBoss, it doesn't pick up any of the source changes
compiled in Eclipse.
I assumed it would load newer classes from Eclipses' output directory in
place of the older ones in the EAR (this works by default in Together) But
it doesn't seem to. If I explicitly put Eclipse's output classes dir in
EASIE's JBoss->Paths list, then the EAR won't deploy (EJB class loading
problem, which is the same thing that happens if I try this with JBoss-IDE
plugin)
Our external build process is very slow at building an updated EAR file.
This is one reason we had been using Together with JBoss before. But I'd
rather use Eclipse. I guess it's possible I can get this to work by
creating an exploded EAR and trying to make Eclipse output classes on top of
the ones in that, but I'd rather not go that route (new EAR files from our
external build would be a pain to deploy) Any help is appreciated.
|
|
|
| Re: Can override/debug a deployed ear? [message #16543 is a reply to message #12313] |
Wed, 07 May 2003 09:18  |
| Eclipse User |
|
|
|
Originally posted by: Joseph.Herbers.eds.com
I found a way to make this work, though it's not the nicest. I exploded my
EAR file in the JBoss deploy directory - I created a foo.ear dir in deploy,
and inside it a foo.war and a foo.jar I extracted the appropriate files
from my EAR into these three dirs. At this point, you can start JBoss
(inside or outside eclipse) and verify that it deploys just like the EAR
did.
Then I created an eclipse project in foo.ear so that I could direct the
output classes from eclipse's builds into the foo.jar dir (eclipse won't let
you direct output classes outside of the dirs that are in the "project dir"
which is very annoying) Thus I override the original classes with the
changes I make while editing source in eclipse. This config causes any
changed files to get included in deployment on a restart. [I also switched
to JDK 1.4.1 so changed classes are hot-deployed and immediately visible in
the running web app]
"Joe Herbers" <Joseph.Herbers@eds.com> wrote in message
news:b8ttg2$q2q$1@rogue.oti.com...
Question: can I update/debug class files in Eclipse without rebuilding and
redeploying the EAR file in JBoss? I've been unsuccessful with both the
JBoss IDE and the EASIE plugins. FYI this worked for us when using
Together.
Using the EASIE JBoss plugin for Eclipse: I got it installed and mostly
working. I can debug my deployed EAR ok as long as I don't change the
source (can't seem to do even that in JBoss IDE). If I'm in 1.4.1 and
change the source, hot deploy works and I can continue running or debugging.
However, if I restart JBoss, it doesn't pick up any of the source changes
compiled in Eclipse.
I assumed it would load newer classes from Eclipses' output directory in
place of the older ones in the EAR (this works by default in Together) But
it doesn't seem to. If I explicitly put Eclipse's output classes dir in
EASIE's JBoss->Paths list, then the EAR won't deploy (EJB class loading
problem, which is the same thing that happens if I try this with JBoss-IDE
plugin)
Our external build process is very slow at building an updated EAR file.
This is one reason we had been using Together with JBoss before. But I'd
rather use Eclipse. I guess it's possible I can get this to work by
creating an exploded EAR and trying to make Eclipse output classes on top of
the ones in that, but I'd rather not go that route (new EAR files from our
external build would be a pain to deploy) Any help is appreciated.
|
|
|
Powered by
FUDForum. Page generated in 0.04245 seconds
Home