[jboss-dev-forums] [Design the new POJO MicroContainer] - StructureDeployers

[adrian@jboss.org]

These haven't changed all that much (at least in princple). The changes are:

1) Factory for DeploymentContext

The StructuralDeployers implementation is now a factory for the DeploymentContext
so it can choose the implementation

2) StructureMetaData

The StructureMetaData can now handle StructureMetaData in subcontexts
so you can specify the structure at subdeployment level.
Previously this was only available at the top level deployment level

3) Root file and ClassPath

I tried to modify the StructureMetaData such that the paths are relative
to the current context (rather than the root).
But, I haven't suceeded for the ClassPath part.
The issue is that manifest references are actually equivalent to

  | addClassPath("../some.jar");
  | 
and so are not really a part of the context.

To make this work consistently, all classpath references are relative
to the root of the top level file.
Part of this change required passing the root/top-level file and parent file
in the StructureDeployer api.

IF the VFS was changed such

  | virtualFile.findChild("../some.jar");
  | 
worked, then we can remove this "cognitive dissonance". 
All classpath references could be relative to the current context
with manifest references translated to add ../ in front them.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058828#4058828

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058828