This content has been marked as final.
Show 6 replies
-
1. Re: Zip deployers and deployment aliases
alesj Mar 16, 2009 11:18 AM (in response to mwringe)You mean alias.txt or bean's alias?
There should be no diff between zip/unzip. -
2. Re: Zip deployers and deployment aliases
alesj Mar 16, 2009 12:01 PM (in response to mwringe)The only diff I can think of is recursion check for new deployments in SerializableDeploymentRepository::addedDeployments.
-
3. Re: Zip deployers and deployment aliases
mwringe Mar 16, 2009 2:38 PM (in response to mwringe)"alesj" wrote:
You mean alias.txt or bean's alias?
aliases.txt"alesj" wrote:
There should be no diff between zip/unzip.
Ok, thats what I thought, but between this issue and http://jira.jboss.org/jira/browse/JBAS-6617 I was beginning to wonder if a zip deployable was something more special. -
4. Re: Zip deployers and deployment aliases
alesj Mar 16, 2009 4:28 PM (in response to mwringe)alias.txt only works in top deployment:
- http://anonsvn.jboss.org/repos/jbossas/projects/jboss-deployers/trunk/deployers-vfs/src/main/java/org/jboss/deployers/vfs/plugins/dependency/AliasesParserDeployer.java -
5. Re: Zip deployers and deployment aliases
mwringe Mar 16, 2009 4:34 PM (in response to mwringe)"alesj" wrote:
alias.txt only works in top deployment:
- http://anonsvn.jboss.org/repos/jbossas/projects/jboss-deployers/trunk/deployers-vfs/src/main/java/org/jboss/deployers/vfs/plugins/dependency/AliasesParserDeployer.java
So in other words, a zipped deployment isn't support to work the same as an unzipped deployment. -
6. Re: Zip deployers and deployment aliases
alesj Mar 16, 2009 5:13 PM (in response to mwringe)"mwringe" wrote:
"alesj" wrote:
alias.txt only works in top deployment:
- http://anonsvn.jboss.org/repos/jbossas/projects/jboss-deployers/trunk/deployers-vfs/src/main/java/org/jboss/deployers/vfs/plugins/dependency/AliasesParserDeployer.java
So in other words, a zipped deployment isn't support to work the same as an unzipped deployment.
Doh? Why? What?
My guess is next:
Your unzipped deployment has no '.' in the name,
hence it's considered as 'grouping' directory - the recursion I mentioned kicks in.
And then each sub dir is an actual top deployment.
In the zipped case the archive is top deployment.