[JBoss JIRA] Created: (EJBTHREE-1854) Configure EJB3 MC beans to avoid AOPDependencyBuilder
by jaikiran pai (JIRA)
Configure EJB3 MC beans to avoid AOPDependencyBuilder
-----------------------------------------------------
Key: EJBTHREE-1854
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1854
Project: EJB 3.0
Issue Type: Task
Components: core, deployers
Affects Versions: 1.1.7
Reporter: jaikiran pai
Assignee: jaikiran pai
This task is to keep track of the change(s) required for all EJB3 MC bean (programatic and xml based) to ensure that the AOPDependencyBuilder does not come into picture during deployment. Avoiding AOPDependencyBuilder has shown good performance improvements.
There isn't a final decision yet on how to do this although MC provides @DisableAOP annotation to achieve this. The MC support for this is currently available in AS 5_x branch and needs to be ported to AS trunk before EJB3 can think of using this. Once there's a decision on what's the best approach to accomplish this, we can do the changes in EJB3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 10 months
[JBoss JIRA] Created: (EJBTHREE-1866) EJB deployer require mapped name for SessionContext injection
by Rinat Gareev (JIRA)
EJB deployer require mapped name for SessionContext injection
-------------------------------------------------------------
Key: EJBTHREE-1866
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1866
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: 1.1.5
Reporter: Rinat Gareev
EJB deployer require mapped name for SessionContext injection
EJB class:
@Stateful
@EJBs
({
@EJB (beanInterface = CoreSecurityFacade.class, beanName = "CoreSecurityFacadeBean",
name = "ejb/CoreSecurityFacade"),
@EJB (beanInterface = CoreApplicationsFacade.class, beanName = "CoreApplicationsFacadeBean",
name = "ejb/CoreApplicationsFacade"),
@EJB (beanInterface = CoreConfigFacade.class, beanName = "CoreConfigFacadeBean",
name = "ejb/CoreConfigFacade")
})
public class CoreFacadeFactoryBean implements CoreFacadeFactory, Serializable
{
@Resource
private SessionContext ctx;
....content omitted
}
Root cause:
Caused by: java.lang.RuntimeException: You did not specify a @Resource.mappedName() on private javax.ejb.SessionContext rs.diving.ubcc.core.core.core.CoreFacadeFactoryBean.ctx and there is no binding for enc name env/rs.diving.ubcc.core.core.core.CoreFacadeFactoryBean/ctx in XML
at org.jboss.injection.ResourceHandler.handlePropertyAnnotation(ResourceHandler.java:684)
at org.jboss.injection.ResourceHandler.handleFieldAnnotations(ResourceHandler.java:497)
at org.jboss.injection.InjectionUtil.processFieldAnnotations(InjectionUtil.java:160)
at org.jboss.injection.InjectionUtil.processAnnotations(InjectionUtil.java:197)
at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:590)
at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:418)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:527)
... 35 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 10 months
[JBoss JIRA] Created: (JBBOOT-96) Extract initialization logic
by Andrew Lee Rubinger (JIRA)
Extract initialization logic
----------------------------
Key: JBBOOT-96
URL: https://jira.jboss.org/jira/browse/JBBOOT-96
Project: JBoss Bootstrap
Issue Type: Task
Components: impl-as, impl-base, impl-mc
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Fix For: 2.0.0-beta-1
With JBBOOT-95 we now have pre/post states for server initialization. This means that the initialize() method must be marked final such that its logic containing when to fire the state changes cannot be overridden. We still need to provide a mechanism for subclasses of AbstractServer to carry out their own initialization logic, so extract this into a "doInitialize()", much like we have a "doStart()".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 10 months