[jboss-jira] [JBoss JIRA] Created: (SECURITY-26) Legacy MBeans move back to JBAS/security project for porting

[Anil Saldhana (JIRA)]

Legacy MBeans move back to JBAS/security project for porting
------------------------------------------------------------

                 Key: SECURITY-26
                 URL: http://jira.jboss.com/jira/browse/SECURITY-26
             Project: JBoss Security
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: JBossSX
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0


The legacy mbean services like jaassecuritymanagerservice etc need to be retained in the security module of the jbas build for porting customers. This is according to Scott.

===
The security mbeans really should be back in the jbossas/security as integration code so that the security project is a mc/pojo based set of security aspects. 
I'm talking about the legacy mbeans which we should keep for porting.
===

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira