DeploymentScanner usage WAS Re: [jboss-dev] Classloader changes from AS 4.2.2 to AS 4.2.3 affecting launch of Tool built Seam apps

[Adrian Brock]

The issues you are talking about are NOT classloading
they are the DeploymentScanner.

I don't see any changes at all to this in the 4.2.x branch
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/branches/Branch_4_2/system/src/main/org/jboss/deployment/scanner/
and minor irrelevant(?) tweaks to some of the deployers.

In fact, the only major change in the deployers that looks relevant
to your problem is in all 4.2.x versions:
https://jira.jboss.org/jira/browse/JBAS-4037

As usual the clue is probably in the question:
"Exporting ear file works (when ear file copied manually to deploy
folder, along with ds file)"

So to reproduce the problem we need to know what you are doing
different?

Again the clues in the question:

"Anyone got an idea why exploded deployment ... differs from a zipped
deployment"

"WARN [DeploymentInfo] Only the root deployment can set the loader
repository"

So read the bottom of conf/jboss-service.xml on how the
URLDeploymentScanner handles URLs ending with / differently
to those that don't. 

Whether the URL is actually a directory is irrelevant.

You are merely telling the scanner whether to deploy the URL
directly (as a top level deployment) or whether you want it
scanning for deployments.

P.S. Changing the names of the deployments (including the case)
can change the deployment ordering - see DeploymentSorter.
So if this is causing a problem you have a missing 
undeclared dependency.

On Mon, 2009-04-27 at 12:32 +0200, Max Rydahl Andersen wrote:
> Hi,
> 
> I've been trying to get to the bottom of why Seam app's behaves 
> differently dependent on which AS 4.x version they run on.
> 
> But after trying to ping Pete, who relayed to Ales, who relayed to Scott 
> then i'm at a bit of a dead end (I assume Scott is too busy with AS 5.x )
> 
> Anyone got an idea why exploded deployment 
> <https://jira.jboss.org/jira/browse/JBIDE-4166> differs from a zipped 
> deployment ?
> Why does it matter which letters we use in the deployment, i.e. 
> fseam.ear behaves different that seam.ear ?
> Why does it work if all jars are in a /lib folder (JEE 5 style), but not 
> when using Manifest.mf (J2EE 1.4 style) ?
> 
> Any input on how we can solve this would be great. See details (with 
> example ear's, no need for installing tools to help)
> 
> https://jira.jboss.org/jira/browse/JBIDE-4166
> 
> Thanks!
> /max
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx