All my problems with your idea of lexical ordering of deployment would go
away if it was optional, per directory. I can see that sometimes it will
be convenient. I don't want to have to number all the more-or-less
required packages in deploy, however.
How about if the deployment scanner mbean config looked like this:
<mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
name="jboss.deployment:type=DeploymentScanner,flavor=URL">
<!-- Uncomment (and comment/remove version below) to enable usage of
the DeploymentCache
<depends
optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache</depends>
-->
<depends
optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
<attribute name="ScanPeriod">5000</attribute>
<!--
| Unprefixed arguments are considered
| file URLs and resolve relative to server home unless the given
path
| is absolute.
-->
<attribute name="URLs">
<dir name="./deploy/core" order="type"/> <!-- 01.jar, 04.ear,
03.war, 02.sar -->
<dir name="./deploy/app" order="lexical"/> <!-- 01.jar, 02.sar,
03.war -->
<url name=".deploy/other/jar1.jar"/>
<url name=".deploy/other/sar2.sar"/>
<url name=".deploy/other/war3.war"/>
</attribute>
</mbean>
To deploy an exploded package, include it as an url.
What do you think? Seems to me that it avoids problems with both extremes.
thanks
david jencks
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
