| JBoss and WTP [message #153167] |
Wed, 21 December 2005 13:57  |
Eclipse User |
|
|
|
Originally posted by: jtesser.bju.edu
ok I am using WTP 1.0(RC5) and connecting to a JBoss 4.03sp1 server. I am
using the JBoss jar that was posted to this newsgroup last week. All is
working well except for one thing.
In Websphere I use to be able to deploy my app to the local server and
change a jsp and it would be a live change. I wouldn't have to restart
the server. I cannot get this to work with Jboss. Should it work? If so
how do I set it up to work? Thanks
|
|
|
| Re: JBoss and WTP [message #153220 is a reply to message #153167] |
Wed, 21 December 2005 15:58  |
| Eclipse User |
|
|
|
Originally posted by: tuomas_kiviaho.hotmail.com
Jason wrote:
> ok I am using WTP 1.0(RC5) and connecting to a JBoss 4.03sp1 server. I
> am using the JBoss jar that was posted to this newsgroup last week. All
> is working well except for one thing.
>
> In Websphere I use to be able to deploy my app to the local server and
> change a jsp and it would be a live change. I wouldn't have to restart
> the server. I cannot get this to work with Jboss. Should it work? If
> so how do I set it up to work? Thanks
I'm struggling with the same scenario. I've been a WebSphere user for
past years as well as. What you're asking is not that simple.
I have a feeling that IBM JDK doesn't hot-swap as often as Sun JDK, but
I really need the 5.0 functionality as does JBoss, but I could not find
a compatible from IBM pages.
But what you're after is hot deployment with exploded packages.
< http://wiki.jboss.org/wiki/Wiki.jsp?page=DeployTipsAndBuildS ampleScripts>
Now the system is making .jar, .ear .war files every time you publish
forcing JBoss to redeploy the whole application.
The option 1 doesn't work very nicely, since DeploymentScanner will try
to deploy every file that's in your workspace unless it's a filtered
out. Then there's a recursive search which shouldn't be turned off. That
means that you gain much from writing your own java.io.Filter. I tried
to rename the WebContent to mycontextroot.war and point the deploy
scanner directly to that. Now the hot deployment triggering didn't work
anymore when I touched web.xml? If you prefix all your source folders
with '.' then you have evaded the recursive search, but there's no way
to bring dependent modules into this process, since they are built to
other location than your desktop.
The option 2 is otherwise acceptable, but it misses WTP functionality
completely. Also if you don't touch files with eclipse that is you are
doing it directly to the files, WTP publishing requires you to refresh
the project before letting you to continue.
Combining option 2 so that WTP does all the copying what ant scripts are
doing and modifying the mentioned files with eclipse whenever
redeployment is required a working solution can be found. Then it's all
up to WTP build process (I hope you're developing web app and not
enterprise app) and JBoss.
There is a location
..metadata\.plugins\org.eclipse.core.resources\.projects under your
workspace where publishing process generates unpacked deployments. You
have to declare each project location to the jboss-service.xml
separately. Then you have to modify the jboss.jar plugin and remove from
ant buildscript everything inside deploy.j2ee.* targets so that you
don't get duplicate deployments to your JBoss.
I myself hate the idea of messing with DeploymentScanner since every
project has to be separately declared for it. There is a JMX MBean for
this to be automated, but still the project naming would have to follow
JBoss exploded deployment syntax.
I'm currently rsyncing the publishing folders to the jboss deployment
folder which detaches me from WTP temp folder events, but not entirely
though.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03559 seconds
] 
Search
Help
Register
Login
Home
