Ales Justin wrote:
> 2) redeployment issues
>
http://jira.jboss.com/jira/browse/JBAS-4220 - Hot deployment of jars
> does not always work
> related to
>
http://jira.jboss.com/jira/browse/JBVFS-7 - JarEntryHandler entryMap
> is not being refreshed
I don't really see when people are modifying their jars @ runtime.
The workaround here is of course exploded dir. :-)
I've seen folks use this in development when they don't have proper
dependency declarations (ie. JAR A depends on JAR B, JAR B is removed,
then put in place again). So the development build instead keeps the
existing JAR, but modifies internal contents. Yes, hacky, but worked
best for their setup (they should have been using an EAR or exploded
directory).