Not really related to the @JMX issue,
but these services shouldn't be in the deployers.
The consumers (EJB and Web Deployers) shouldn't be referencing
the services directly, they should be injecting them
onto their MBeans using the names.
Wrong:
<!-- Specify a SecurityManagement Wrapper -->
<property name="securityManagement">
<inject bean="JNDIBasedSecurityManagement"/>
</property>
Correct:
<property
name="securityManagementName">JNDIBasedSecurityManagement"</property>
On Wed, 2008-03-12 at 16:38 +0100, Adrian Brock wrote:
I'm seeing a total different issue:
*** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required
State:Actual State}
SecurityConfig
-> jboss.security:service=XMLLoginConfig{Start:** NOT FOUND **}
-> jboss.security:service=XMLLoginConfig{Create:** NOT FOUND **}
*** CONTEXTS IN ERROR: Name -> Error
jboss.security:service=XMLLoginConfig -> ** NOT FOUND **
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx