| What is the point of running a j2ee server adapter inside eclipse as opposed to [message #521788] |
Thu, 18 March 2010 09:08  |
Eclipse User |
|
|
|
What is the advantage of running a j2ee server from inside eclipse during
development as opposed to running a standalone server and connecting to it
externally to deploy /start/stop and remote debug ?
Do we get any time savings with the development cycle ? I particularly want
to reduce the deployment time that it takes to deploy a war or ear to a
seerver and was hoping that this will offer a better way.
thanks
|
|
|
| Re: What is the point of running a j2ee server adapter inside eclipse as opposed to [message #521793 is a reply to message #521788] |
Thu, 18 March 2010 14:15  |
| Eclipse User |
|
|
|
When running a server from within eclipse, you're able to automatically start it in debug mode, or just run it in normal mode.
The main advantage in running the server in normal mode is that you'll save a lot of memory and sometimes, at development phase, you don't need to debug everything, taking less time to (re)start the server and buying you a lot of time.
It surely helps in the deploy cycle as Eclipse automatically deploy evertyhing to you and refresh the content when you save a file, change buildpath or rebuild.
If you keep the server outside, you always need to export the war/ear file and restart the server so it will redeploy the updated file. You'll have to do this everytime, for each file you change, each jar you add, etc.
|
|
|
| Re: What is the point of running a j2ee server adapter inside eclipse as opposed to [message #521807 is a reply to message #521793] |
Thu, 18 March 2010 14:44 |
| Eclipse User |
|
|
|
Thankyou for taking the time to answer my questions. I have some
followups...
> The main advantage in running the server in normal mode is that you'll
> save a lot of memory and >sometimes, at development phase, you don't need
> to debug everything, taking less time to (re)start the >server and buying
> you a lot of time.
Are you implying that when I start a server outside eclipse in debug mode,
all classes are in debug mode, but when started inside eclipse , somehow
only those classes that I have breakpoints in are in debug mode ? I am not
sure exactly what happens when I start an application in debug mode. I was
under the impression that debug instrumentation is all or none...
> It surely helps in the deploy cycle as Eclipse automatically deploy
> evertyhing to you and refresh the content when you save a file, change
> buildpath or rebuild.
>
> If you keep the server outside, you always need to export the war/ear file
> and restart the server so it will redeploy the updated file. You'll have
> to do this everytime, for each file you change, each jar you add, etc.
Weblogic has autodeploy which is a directory that you can drop an exploded
war into and it will pick it up without having to redeploy. The problem I
have is when I do this I cannot set breakpoints in jsps...
Still a little confused... so many things all similar- hot code replace,
myeclipse's "sync on demand" , weblogic's autodeploy ....
|
|
|
| Re: What is the point of running a j2ee server adapter inside eclipse as opposed to [message #521828 is a reply to message #521807] |
Thu, 18 March 2010 15:52 |
| Eclipse User |
|
|
|
| Quote: | Are you implying that when I start a server outside eclipse in debug mode,
all classes are in debug mode, but when started inside eclipse , somehow
only those classes that I have breakpoints in are in debug mode ? I am not
sure exactly what happens when I start an application in debug mode. I was
under the impression that debug instrumentation is all or none...
|
No, you're right, debug is all or none. And that's what I'm saying. If you start the server in debug mode you'll need to start the whole JVM in debug mode, meaning that the whole server will be debugging, inside or outside eclipse. My point was that, if you need to test the application and don't need debug, you can change that inside eclipse just by clicking another button (the run button, instead of the debug button). Outside eclipse, from what I know, weblogic must be configured to run in debug mode, and toggling that on and off seems to be a much more complex process.
| Quote: | Weblogic has autodeploy which is a directory that you can drop an exploded
war into and it will pick it up without having to redeploy. The problem I
have is when I do this I cannot set breakpoints in jsps...
|
Well.... if when you save a file it will autodeploy the whole application automatically, then you should think about how much JSPs breakpoints are important to you. If they aren't, then you should consider other stuff because you have a draw. 
|
|
|
Powered by
FUDForum. Page generated in 0.04012 seconds
Home