[jboss-dev-forums] [Design of POJO Server] - Re: ProfileService Guidance
scott.stark@jboss.org
do-not-reply at jboss.com
Tue Oct 28 21:47:02 EDT 2008
If we are going to keep the old security objects they really should have a similar management interface to the new beans where it make sense. Beans annotated at the bean class level with @ManagementObject are now showing up and the SecurityManagedObjectsTestCase shows obtaining the SecurityConfig whose component type is "MCBean","Security". There is an annotation on the JNDIBasedSecurityRegistration deployment:
| <bean name="JNDIBasedSecurityRegistration"
| class="org.jboss.security.integration.JNDIBasedSecurityRegistration">
| <!-- This has to be on one line, see JBMDR-49 -->
| <annotation>@org.jboss.managed.api.annotation.ManagementObject(name="JNDIBasedSecurityRegistration",componentType=@org.jboss.managed.api.annotation.ManagementComponent(type="MCBean", subtype="Security"))</annotation>
| <property name="policyRegistration"><inject bean="JBossSecurityPolicyRegistration" /></property>
| <property name="securityManagement"><inject bean="JNDIBasedSecurityManagement" /></property>
| </bean>
|
which should also be showing up, but currently is not as the metadata level annotation is not propagated to the management object factory. I'm looking into what to do about that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185263#4185263
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185263
More information about the jboss-dev-forums
mailing list