[
https://issues.jboss.org/browse/AS7-3985?page=com.atlassian.jira.plugin.s...
]
Carlo de Wolf moved EJBTHREE-1732 to AS7-3985:
----------------------------------------------
Project: Application Server 7 (was: EJB 3.0)
Key: AS7-3985 (was: EJBTHREE-1732)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: (was: AS 4.2.3.GA)
(was: 1.0.0-Beta10)
Component/s: EJB
(was: ejb3)
Fix Version/s: (was: TBD EAP 6)
Pooling strategy and configuration information needed at runtime
----------------------------------------------------------------
Key: AS7-3985
URL:
https://issues.jboss.org/browse/AS7-3985
Project: Application Server 7
Issue Type: Feature Request
Components: EJB
Reporter: Galder Zamarreño
Assignee: Carlo de Wolf
There needs to be a way at runtime to see what pooling strategy (including configuration
options) an
EJB3 bean is using. Currently, the only way to see this is by enabling TRACE on
org.jboss.ejb3 and
making an invocation to that EJB3 bean.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira