URLDeploymentScanner.scan calls MainDeployer.checkIncompleteDeployments
to validate unsatisfied dependencies on each scan so check that.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Tuesday, March 07, 2006 3:17 PM
To:
What I found was that unless the *top* DeploymentInfo has the unready
mbean listed in its member variable DeploymentInfo.mbeans, then there
is no error message printed.
So, I added the created mbeans to the EAR's DI.mbeans variable and got
the error message. Then I jarred the EAR in a .jar
The deployment check should be traversing the nested dependency state
then.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Tuesday, March 07, 2006 5:09 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] no dependency
] On Behalf Of Bill
Burke
Sent: Tuesday, March 07, 2006 5:09 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] no dependency error message
What I found was that unless the *top* DeploymentInfo has the unready
mbean listed in its member variable DeploymentInfo.mbeans
