This content has been marked as final.
Show 2 replies
-
1. Re: all files that make up a deployment unit
adrian.brock Oct 5, 2006 4:58 AM (in response to bill.burke)Do what you want, I'll fix it later.
This needs to work on the classpath notion.
A visitor on the classpath (a concept that doesn't exist
but I suggested you write on an earlier thread)
should not be recursing into nested deployments.
The notion of archive will be removed from the VFS
to the deployers anyway, see the other thread where
Scott and I were arguing about this.
Manifest/Non-Manifest or more accurately (external/non-external)
would be an attribute on the classpath visit. -
2. Re: all files that make up a deployment unit
bill.burke Oct 5, 2006 9:54 AM (in response to bill.burke)"adrian@jboss.org" wrote:
Do what you want, I'll fix it later.
This needs to work on the classpath notion.
A visitor on the classpath (a concept that doesn't exist
but I suggested you write on an earlier thread)
should not be recursing into nested deployments.
I'm fine with using DeploymentUnit.getDeploymentContext().getClassPath() as long as this classpath is equivalent to the notion of a resource loader in the old container.
So for instance, a jar within a WAR would be its own DeploymentUnit with a context with a classpath of only that jar (and its manifest references).
Bill