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

[Brad Maxwell (JIRA)]

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

Brad Maxwell updated WFLY-4699:
-------------------------------
    Description: 
User will be able to get EJB Deployment Information at runtime 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
    - EJB timeout (Stateful Timeouts , and Stateless Instance timeout)

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 provide that information 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.


  was:
User will be able to get EJB Deployment Information at runtime 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 provide that information 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.




> Expose EJB3 deployment information at runtime
> ---------------------------------------------
>
>                 Key: WFLY-4699
>                 URL: https://issues.jboss.org/browse/WFLY-4699
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EJB
>            Reporter: Bilge Ozpeynirci
>            Assignee: David Lloyd
>            Priority: Minor
>
> User will be able to get EJB Deployment Information at runtime 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
>     - EJB timeout (Stateful Timeouts , and Stateless Instance timeout)
> 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 provide that information 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
(v7.2.3#72005)