[Design of JBoss Deployment Framework] - Re: Designing of jain-slee deployers for Jboss5.
by alesj
"alexandrem" wrote : Shouldn't the DU's that were not "accepted" by any deployer be given "another chance" when a new deployer comes in?
|
There is no such mechanism in new deployers.
Since they work on a totally different system of what we used to have.
Before if was (mostly) single deployer that did it all,
not it's a chain of unrelated deployers that are metadata driven.
So, even if some deployer is 'missing' that doesn't mean deployment wasn't deployed.
It just might be that that particualr deployer didn't provide it's input/output,
but that's hard/costly to fix - it would mean you have to re-deploy all deployments.
But I agree, it make sense to do this for those deployments which we know weren't 'touched' by any deployer.
Perhaps a MC/Deployers 2.2 feature. ;-)
"alexandrem" wrote : Is there any way of fixing this?
|
In your case I see two options.
1) put SLEE into deployers
- conceptually ugly/wrong and not hot-re-deployable
2) use jboss-dependency.xml
- http://www.jboss.org/community/docs/DOC-13178
e.g. some pseudo xml code
| <dependency xmlns="urn:jboss:dependency:1.0">
| <item whenRequired="Describe">SLEEDeployer</item>
| </dependency>
|
Where your SLEEDeployer gets SLEE injected.
The only issue here is in which phase your SLEEDeployer kicks in?
If it's before Describe, this won't work, since we're already past that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192930#4192930
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192930
16 years, 1 month