This makes more sense to me, although I still don't believe isArchive is sufficiently
different from isLeaf == false to warrant an attribute. Its essentially isLeaf == false +
a suffix pattern to indicate this is a special non-leaf. The suggested change of the
VFScanner defines such a special non-leaf such that only archives can contain deployable
content. Its not clear that the vfs really has sufficient knowledge of a non-leaf to make
this distinction. Examples include:
- jars referenced via Class-Path manifest references are not to be considered as
deployments.
- we need to support a virtual war/ejb-jar that is directory, that does not have to end in
.war/.jar, containing war/ejb-jar contents.
I think we need a basic vfs notion, and an attributed vfs notion where the attributed vfs
is a result of metadata coming from the structural analysis. In the attributed vfs I can
ask is a non-leaf a deployment container or not.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974879#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...