This content has been marked as final.
Show 1 reply
-
1. Re: Potential Duplicate services defined by JBoss projects
starksm64 Mar 17, 2006 12:57 PM (in response to anil.saldhana)Overriding is certainly the wrong thing to do. What is needed is the notion of a default configuration if a dependency is not satisfied. This is the ${x:y} system property reference equivalent of a service dependency. The main problem with this exact form of dependency specification is lack of stability with the current jmx service object names. This could be addressed with a service name alias service we have mentioned from time to time for a long time now. Anyway, what is needed is:
<mbean name="jboss.portal:serivce=portal-container"> ... <depends>jboss.security:service=JACCSecurityMgr <default>jboss.portal:service=JACCSecurityMgr</default> </depends> </mbean> <mbean name="jboss.portal:service=JACCSecurityMgr" mode="onDmand"> ... </mbean>
so that if there is a jboss.security:service=JACCSecurityMgr, its used, otherwise the portal local definition is used. I don't know exactly what support the mc has for this yet.