[jboss-dev-forums] [Design of POJO Server] - Deployment Structure

[adrian@jboss.org]

This is a summary to try to end the discussions that are currently going
around in circles.

The basic idea follows the "do one thing well principle".

There are three components:
1) VFS - responsible for presenting the different protocols as a
single consistent file system, and abstracting away things like
unpacked directories pretending to be jars or unpacking nested jars.

2) StructureDeployers - responsible for determining the structure
of deployments, i.e. what is the classpath, metadata location
and subdeployments.

3) Deployers reponsible for working with the above models
to deploy stuff.

In no way should:
1) The VFS be dealing with deployment decisions.
2) The structure deployers be dealing with protocol issues.
3) The real deployers be dealing with protocol or structural issues.

I can think of one current exception to this rule where the
jboss-service.xml has an
<archives/>
that adds additional elements to the classpath.

In future, there is likely to be some form of aspectized
classloader.xml that will take the place of this element
and the loader-repository-config which can be processed by
the structure deployers such that this can be deprecated
and removed as the legacy mixing of concerns that it is.

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

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