The lib folder is not for hot deployment.
Can't you package the jar with your app and redeploy it?
Why do you need to replace it so frequently?
>The lib folder is not for hot deployment.
>Can't you package the jar with your app and redeploy it?
>Why do you need to replace it so frequently?
The Jar file contains Security classes that I'm trying to customize
for my application (ClientLoginModule, DatabaseServerLoginModule
and so on...).
It's used client side (when I run my standalone client application
I have the jar file in CLASSPATH) and server side (in another forum
I was said to put the jar file in lib directory).
I need to replace it so frequently only in the testing phase.
I'm stuck wasting a lot of time waiting for JBoss to restart everytime. I really want to know how to do this. Moreno, did you find any solution to this. Please reply.
Why don't you package that jar in your own application and then just redeploy your application every time you want the jar to be changed?