Zip deployers and deployment aliases

[mwringe]

I have a directory that I deploy on JBoss AS5 that contains various different deployables (mostly sars and wars). We use an alias file in a sar for dependency management.

Everything works fine when the directory is deployed, but if its packaged as a zip then deployables outside the zip can't find the alias dependency (deployables inside the zip appear to find the dependency without issue).

Are zip deployables suppose to work exactly the same as if was unzipped? Or I am making assumptions about how it should be used.

[alesj]

You mean alias.txt or bean's alias?
There should be no diff between zip/unzip.

[alesj]

The only diff I can think of is recursion check for new deployments in SerializableDeploymentRepository::addedDeployments.

[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.

[alesj]

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

[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.

[alesj]

"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.