Since we are not going to get too far on this for the 5.0.0.GA, I want to continue to talk
about what the server contents might look like in the canonical distribution paradigm.
The server contents would probably be something like:
| jboss-5.1/bin
| jboss-5.1/repository
| jboss-5.1/server/default/profile.xml
| jboss-5.1/server/all/profile.xml
| ...
|
The repository has deployment bundles, be they library jars or deployer contents, along
with metadata about each deployment that includes things like version, capabilities and
requirements. See the OSGi OBR spec
http://www.osgi.org/Download/File?url=/download/rfc-0112_BundleRepository... for an idea
of capabilities/requirements.
A profile.xml should actually only be a statement of requirements that are matched up to
content in the repository:
| <profile name="default">
| <requirement>ejb3-core</requirement>
| <requirement>ejb3-ext</requirement>
| <requirement>ejb2</requirement>
| <requirement>ejb2</requirement>
| <requirement>JMS</requirement>
| <requirement>jmx-console.war</requirement>
| <requirement>ROOT.war</requirement>
| <requirement>JSR77 MEJB</requirement>
| ...
| </profile>
|
We may need to include library version range requirements as well for applications that
will be added dynamically via hot deploy.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185782#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...