"adrian(a)jboss.org" wrote :
| At the vfs level this is either a parameter on the initial url a failing that or a
different protocol
| type to support the legacy unpacking mechanism and the return of a "jar:"
url
| from the VirtualFile.toURL().
|
| For programmatic deployment its easy to decide what the URL upfront should be.
|
Is there a better way to do this than this:
| URL url = getResource("/vfs/context/" + name);
| URI uri = new URI(url.toExternalForm() + "?useCopyJarHandler=true");
|
"adrian(a)jboss.org" wrote :
| Other more automatic rules should be in the Structure Deployers. They're the ones
that know a context is a war and can decide based on some metadata in the deployment or an
external rule that a paricular war or all wars should be unpacked when they are
subdeployments.
Then it could be too late.
e.g. a War Structure deployer is already going inside war file, checking for WEB-INF and
web.xml, by such caching the handler on its parent.
And we already used what we actually wanted to set - we either created the copy, but the
policy would say not to create them, or vice versa.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144191#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...