[JBoss JIRA] (WFLY-4699) Expose EJB3 deployment information at runtime
by Bilge Ozpeynirci (JIRA)
[ https://issues.jboss.org/browse/WFLY-4699?page=com.atlassian.jira.plugin.... ]
Bilge Ozpeynirci 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
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 information on 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
> 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
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4699) Expose EJB3 deployment information at runtime
by Bilge Ozpeynirci (JIRA)
Bilge Ozpeynirci created WFLY-4699:
--------------------------------------
Summary: 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
User will be able to get information on 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 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)
11 years, 1 month
[JBoss JIRA] (WFLY-4699) Expose EJB3 deployment information at runtime
by Bilge Ozpeynirci (JIRA)
[ https://issues.jboss.org/browse/WFLY-4699?page=com.atlassian.jira.plugin.... ]
Bilge Ozpeynirci updated WFLY-4699:
-----------------------------------
Priority: Minor (was: Major)
> 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
> Priority: Minor
>
> User will be able to get information on 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 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)
11 years, 1 month
[JBoss JIRA] (WFLY-4699) Expose EJB3 deployment information at runtime
by Bilge Ozpeynirci (JIRA)
[ https://issues.jboss.org/browse/WFLY-4699?page=com.atlassian.jira.plugin.... ]
Bilge Ozpeynirci reassigned WFLY-4699:
--------------------------------------
Assignee: David Lloyd
> 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 information on 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 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)
11 years, 1 month
[JBoss JIRA] (WFLY-4698) Expose EJB3 deployment information at runtime
by Bilge Ozpeynirci (JIRA)
[ https://issues.jboss.org/browse/WFLY-4698?page=com.atlassian.jira.plugin.... ]
Bilge Ozpeynirci deleted WFLY-4698:
-----------------------------------
> Expose EJB3 deployment information at runtime
> ---------------------------------------------
>
> Key: WFLY-4698
> URL: https://issues.jboss.org/browse/WFLY-4698
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Bilge Ozpeynirci
> Assignee: David Lloyd
>
> 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)
11 years, 1 month
[JBoss JIRA] (WFLY-4698) Expose EJB3 deployment information at runtime
by Bilge Ozpeynirci (JIRA)
[ https://issues.jboss.org/browse/WFLY-4698?page=com.atlassian.jira.plugin.... ]
Bilge Ozpeynirci reassigned WFLY-4698:
--------------------------------------
Assignee: (was: Jimmy Wilson)
> 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
>
> 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)
11 years, 1 month
[JBoss JIRA] (WFLY-4698) Expose EJB3 deployment information at runtime
by Bilge Ozpeynirci (JIRA)
[ https://issues.jboss.org/browse/WFLY-4698?page=com.atlassian.jira.plugin.... ]
Bilge Ozpeynirci reassigned WFLY-4698:
--------------------------------------
Assignee: David Lloyd
> 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: David Lloyd
>
> 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)
11 years, 1 month
[JBoss JIRA] (WFLY-4698) Expose EJB3 deployment information at runtime
by Bilge Ozpeynirci (JIRA)
[ https://issues.jboss.org/browse/WFLY-4698?page=com.atlassian.jira.plugin.... ]
Bilge Ozpeynirci updated WFLY-4698:
-----------------------------------
Labels: (was: lodh)
> 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: David Lloyd
>
> 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)
11 years, 1 month
[JBoss JIRA] (WFLY-4698) Expose EJB3 deployment information at runtime
by Bilge Ozpeynirci (JIRA)
[ https://issues.jboss.org/browse/WFLY-4698?page=com.atlassian.jira.plugin.... ]
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)
11 years, 1 month
[JBoss JIRA] (WFCORE-720) JBoss CLI PowerShell script doesn't match the behavior of the others
by James Perkins (JIRA)
James Perkins created WFCORE-720:
------------------------------------
Summary: JBoss CLI PowerShell script doesn't match the behavior of the others
Key: WFCORE-720
URL: https://issues.jboss.org/browse/WFCORE-720
Project: WildFly Core
Issue Type: Bug
Components: Scripts
Reporter: James Perkins
Assignee: Tomaz Cerar
The {{jboss-cli.ps1}} script doesn't match the behavior of the other {{jboss-cli.xx}} scripts. A startup message is echoed, the wrong logging.properties is used, the Swing packages aren't added for the GUI, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month