]
Benoit Reverbel commented on JBAS-6152:
---------------------------------------
It seems that only the deploy folder is watched and sorted by the URLDeploymentScanner.
Archives in deploy are deployed in the right order but not archives which are in farm
folder.
URLComparator PrefixDeploymentSorter doesn't work for instance
all in jboss 4.2.3GA only with instance "all"
------------------------------------------------------------------------------------------------------------
Key: JBAS-6152
URL:
https://jira.jboss.org/jira/browse/JBAS-6152
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-4.2.3.GA
Environment: Windows XP Pro/Linux Red Hat
Reporter: Benoit Reverbel
Assignee: Ales Justin
I used so far the PrefixDeploymentSorter to select in which order my archives would be
deployed.
It worked fine in JBoss AS 4.2.0GA. Now I am upgrading to JBoss AS 4.2.3GA and it seems
not to work anymore (only for instance "all").
When I use instance "default", the deployer follows number prefixes of my
archives:
1) 010-myear.ear
2) 020-myjar.jar
3) 030-mywar.war
When using instance "all", it seems to use the default DeploymentSorter by
deploying first service.xml, then my jars, after that my wars and at the end ears.
1) 020-myjar.jar
2) 030-mywar.war
3) 010-myear.ear
As I need to use JBoss 4.2.3GA in cluster mode, it is mandatory for me to start from
"all" instance.
Is there any workaround or any special configuration to do ?
Best Regards,
Benoit Reverbel
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: