the problem is that the classloader is still holding on the jar and thus under windows you
will get such errors.
we are working on getting jboss to actually undeploy the app before we start removing the
files - that should avoid this windows only issue.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123874#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...