An exploded ear can be redeployed by touching application.xml but the constituent wars and ejb jars cannot be independently reloaded - seems like reasonable behavior. Also note that although vanilla beans can hot deploy you will still get class not found errors because the ejbs load first. That is where adding Class-Path entries to the MANIFEST.MF file of an ejb jar would come in handy but those settings do not appear to have any effect. The same problem existed in weblogic. Still looking for a definitive statement on hot deploy of shared classes that are used by ejbs or wars.
------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
