[jboss-jira] [JBoss JIRA] (WFLY-4698) Expose EJB3 deployment information at runtime

[Bilge Ozpeynirci (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bilge Ozpeynirci moved PRODMGT-1255 to WFLY-4698:
-------------------------------------------------

                        Project: WildFly  (was: Product Management)
                            Key: WFLY-4698  (was: PRODMGT-1255)
                       Workflow: GIT Pull Request workflow   (was: JBoss Platforms RFE Workflow v2)
              Affects Version/s:     (was: 6)
         Background and Context:   (was: Re-openning it to execute the "Engineering Triage" as per the custom workflow in this JIRA.)
                    Component/s: EJB
                                     (was: Enterprise Application Platform (EAP))
    Product Management Response:   (was: Deferred for consideration in EAP 7.)


> Expose EJB3 deployment information at runtime
> ---------------------------------------------
>
>                 Key: WFLY-4698
>                 URL: https://issues.jboss.org/browse/WFLY-4698
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EJB
>            Reporter: Bilge Ozpeynirci
>            Assignee: Jimmy Wilson
>              Labels: lodh
>
> User will be able to get information on EJB Deployment Information for the following areas:
>     - Class name
>     - Local JNDI name
>     - Remote JNDI name
>     - Security roles
>     - Bean statistics (beans in use, access count, idle count, ...)
>     - Destination JNDI (for MDBs)
>     - Activation config properties
> A lot of this information were previously (EAP 5) obtained from the deployment descriptor that was published by the bean ("deploymentDescriptor" attribute). In the past, this metadata could be retrieved from EAP 5 via jmx which no longer exists in EAP 6+ (JBoss AS 7+). Now with EJB 3, users put those informations through annotations (and also through the Deployment Descriptor file), so users need means to get those informations at runtime.
> The goal of this is not only for MDB but for all kinds of EJB (session, stateful, MDB, ...)
> MORE INFO:
> The local and remote JNDI are related to Session EJBs.
> However we need to access the JNDI of the destination configured for the MDB.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)