[avajrd]

Environment:

WinXP
Eclipse 3.0.1
MyElipse 3.8.3
JBoss 3.2.3

I just began using 3.8.3 for a new Struts / Hibernate based project. I noticed the “Library Deployment Policies” settings and thought this might just be the ticket solve problems I have with redeployments to JBoss 3.

My prior problems were that jar files become locked and the redeployment fails. Hot deployment appears to work fine, but sometimes a redeployment is required. When it fails I have to stop JBoss and restart. Very time consuming.

It appeared to me that if I unchecked all the options in the properties of the Web Project, then none of the jars would be deployed. I could then just put the jar files into the JBoss server lib directory. Redeployment would then proceed every time without incident.

Trouble is, the jars get deployed anyways. I noticed that when I look at the project in Resource Perspective, the jars are under WEB-INF/lib. I guess they got installed there when I added the struts and hibernate capabilities.

Is there an easy way to just add the jars to the build path and not to the class path of the deployment?

Thanks, Mike

[avajrd]

Nevermind, I’ve worked around it.

[Author]

Posts