<wild eyed, covered in blood from the entrails of the deployers> 1- since the deployers are now unified the distinction between deploy and deploy/lib is a bit artificial. It used to be (since this summer so it is not that established either) that applications and classes and services would be deployed in different places. I put that in, I am ripping it out everybode in deploy. Jars/sars/schmars and their "directory versions". This is as simple as it can get...
2- deploying *classes* from these deploy. If you want to dynamically add a class jar to the server you could drop it in the deploy/ directory and i will happily pick it up and add it as a DeploymentInfo with its own little URLClassLoader. It is also a watched URL so any changes to this jar we will be able to track (class dependency tracking to be added).I have transformed the deployers so much that I can't remember if this class behavior was already there or not. Could be. FYI marcf "Racism is an instrument of order" -- Steve Frisco, Z Source -- ______________________________________________________________________ View this jboss-dev thread in the online forums: http://jboss.org/forums/thread.jsp?forum=66&thread=6272 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
