1:30 p.m.
Thomas Diesler created AS7-5147:
-----------------------------------
Summary: @Resource injection of BundleContext into ManagedBean fails
Key: AS7-5147
URL: https://issues.jboss.org/browse/AS7-5147
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Web
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.3.0.Alpha1
{code}
Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective information
for class org.jboss.as.test.integration.osgi.resource.SimpleServlet with ClassLoader
ModuleClassLoader for Module "deployment.war-example.war:main" from Service
Module Loader
at
org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:72)
[jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:58)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:85)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:70)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:55)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116)
[jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
... 5 more
Caused by: java.lang.NoClassDefFoundError: Lorg/osgi/framework/BundleContext;
at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.6.0_33]
at java.lang.Class.privateGetDeclaredFields(Class.java:2291) [rt.jar:1.6.0_33]
at java.lang.Class.getDeclaredFields(Class.java:1743) [rt.jar:1.6.0_33]
at
org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:57)
[jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:68)
[jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
{code}
--
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
2:06 p.m.
[
https://issues.jboss.org/browse/AS7-5147?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-5147:
--------------------------------
Description:
{code}
21:04:12,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.ear"
21:04:12,987 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.jar"
21:04:12,988 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876:
Starting deployment of "managed-bean.war"
21:04:13,066 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002:
Processing weld deployment managed-bean.ear
21:04:13,097 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002:
Processing weld deployment managed-bean.war
21:04:13,099 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002:
Processing weld deployment managed-bean.jar
21:04:13,114 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005: Starting
Services for CDI deployment: managed-bean.ear
21:04:13,137 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear:main" from Service Module Loader
21:04:13,141 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting
weld service for deployment managed-bean.ear
21:04:13,187 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.war:main" from Service
Module Loader
21:04:52,328 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.jar:main" from Service
Module Loader
21:04:52,402 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web
context: /managed-bean.war
21:04:52,607 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS015870:
Deploy of deployment "managed-bean.ear" was rolled back with failure message
{"JBAS014771: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".env.\"org.jboss.as.test.integration.osgi.resource.SimpleManagedBean\".context
Missing[jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".BundleContext]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".jndiDependencyService
Missing[JBAS014861: <one or more transitive
dependencies>]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".component.SimpleManagedBean.START
Missing[JBAS014861: <one or more transitive dependencies>]"]}
{code}
was:
{code}
Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective information
for class org.jboss.as.test.integration.osgi.resource.SimpleServlet with ClassLoader
ModuleClassLoader for Module "deployment.war-example.war:main" from Service
Module Loader
at
org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:72)
[jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:58)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:85)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:70)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:55)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116)
[jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
... 5 more
Caused by: java.lang.NoClassDefFoundError: Lorg/osgi/framework/BundleContext;
at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.6.0_33]
at java.lang.Class.privateGetDeclaredFields(Class.java:2291) [rt.jar:1.6.0_33]
at java.lang.Class.getDeclaredFields(Class.java:1743) [rt.jar:1.6.0_33]
at
org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:57)
[jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:68)
[jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
{code}
@Resource injection of BundleContext into ManagedBean fails
-----------------------------------------------------------
Key: AS7-5147
URL: https://issues.jboss.org/browse/AS7-5147
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Web
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.3.0.Alpha1
{code}
21:04:12,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.ear"
21:04:12,987 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.jar"
21:04:12,988 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876:
Starting deployment of "managed-bean.war"
21:04:13,066 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002:
Processing weld deployment managed-bean.ear
21:04:13,097 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002:
Processing weld deployment managed-bean.war
21:04:13,099 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002:
Processing weld deployment managed-bean.jar
21:04:13,114 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005:
Starting Services for CDI deployment: managed-bean.ear
21:04:13,137 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear:main" from Service Module Loader
21:04:13,141 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008:
Starting weld service for deployment managed-bean.ear
21:04:13,187 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.war:main" from Service
Module Loader
21:04:52,328 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.jar:main" from Service
Module Loader
21:04:52,402 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web
context: /managed-bean.war
21:04:52,607 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS015870:
Deploy of deployment "managed-bean.ear" was rolled back with failure message
{"JBAS014771: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".env.\"org.jboss.as.test.integration.osgi.resource.SimpleManagedBean\".context
Missing[jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".BundleContext]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".jndiDependencyService
Missing[JBAS014861: <one or more transitive
dependencies>]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".component.SimpleManagedBean.START
Missing[JBAS014861: <one or more transitive dependencies>]"]}
{code}
--
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
2:10 p.m.
[
https://issues.jboss.org/browse/AS7-5147?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-5147:
--------------------------------
Description:
@Resource BundleContext injection fails with
{code}
21:04:12,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.ear"
21:04:12,987 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.jar"
21:04:12,988 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876:
Starting deployment of "managed-bean.war"
21:04:13,066 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002:
Processing weld deployment managed-bean.ear
21:04:13,097 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002:
Processing weld deployment managed-bean.war
21:04:13,099 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002:
Processing weld deployment managed-bean.jar
21:04:13,114 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005: Starting
Services for CDI deployment: managed-bean.ear
21:04:13,137 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear:main" from Service Module Loader
21:04:13,141 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting
weld service for deployment managed-bean.ear
21:04:13,187 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.war:main" from Service
Module Loader
21:04:52,328 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.jar:main" from Service
Module Loader
21:04:52,402 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web
context: /managed-bean.war
21:04:52,607 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS015870:
Deploy of deployment "managed-bean.ear" was rolled back with failure message
{"JBAS014771: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".env.\"org.jboss.as.test.integration.osgi.resource.SimpleManagedBean\".context
Missing[jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".BundleContext]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".jndiDependencyService
Missing[JBAS014861: <one or more transitive
dependencies>]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".component.SimpleManagedBean.START
Missing[JBAS014861: <one or more transitive dependencies>]"]}
{code}
This is probably because of this code in BundleContextBindingProcessor
{code}
if (comp.getNamingMode() == ComponentNamingMode.CREATE) {
ServiceName serviceName =
contextServiceNameOfComponent(moduleDesc.getApplicationName(), moduleDesc.getModuleName(),
comp.getComponentName());
bindServices(depUnit, serviceTarget, moduleDesc, comp.getComponentName(),
serviceName);
}
{code}
The namingMode == USE_MODULE and the BundleContextdoes not get bound.
Is this binding logic correct?
was:
{code}
21:04:12,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.ear"
21:04:12,987 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.jar"
21:04:12,988 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876:
Starting deployment of "managed-bean.war"
21:04:13,066 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002:
Processing weld deployment managed-bean.ear
21:04:13,097 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002:
Processing weld deployment managed-bean.war
21:04:13,099 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002:
Processing weld deployment managed-bean.jar
21:04:13,114 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005: Starting
Services for CDI deployment: managed-bean.ear
21:04:13,137 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear:main" from Service Module Loader
21:04:13,141 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting
weld service for deployment managed-bean.ear
21:04:13,187 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.war:main" from Service
Module Loader
21:04:52,328 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.jar:main" from Service
Module Loader
21:04:52,402 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web
context: /managed-bean.war
21:04:52,607 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS015870:
Deploy of deployment "managed-bean.ear" was rolled back with failure message
{"JBAS014771: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".env.\"org.jboss.as.test.integration.osgi.resource.SimpleManagedBean\".context
Missing[jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".BundleContext]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".jndiDependencyService
Missing[JBAS014861: <one or more transitive
dependencies>]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".component.SimpleManagedBean.START
Missing[JBAS014861: <one or more transitive dependencies>]"]}
{code}
@Resource injection of BundleContext into ManagedBean fails
-----------------------------------------------------------
Key: AS7-5147
URL: https://issues.jboss.org/browse/AS7-5147
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Web
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.3.0.Alpha1
@Resource BundleContext injection fails with
{code}
21:04:12,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.ear"
21:04:12,987 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.jar"
21:04:12,988 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876:
Starting deployment of "managed-bean.war"
21:04:13,066 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002:
Processing weld deployment managed-bean.ear
21:04:13,097 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002:
Processing weld deployment managed-bean.war
21:04:13,099 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002:
Processing weld deployment managed-bean.jar
21:04:13,114 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005:
Starting Services for CDI deployment: managed-bean.ear
21:04:13,137 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear:main" from Service Module Loader
21:04:13,141 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008:
Starting weld service for deployment managed-bean.ear
21:04:13,187 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.war:main" from Service
Module Loader
21:04:52,328 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.jar:main" from Service
Module Loader
21:04:52,402 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web
context: /managed-bean.war
21:04:52,607 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS015870:
Deploy of deployment "managed-bean.ear" was rolled back with failure message
{"JBAS014771: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".env.\"org.jboss.as.test.integration.osgi.resource.SimpleManagedBean\".context
Missing[jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".BundleContext]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".jndiDependencyService
Missing[JBAS014861: <one or more transitive
dependencies>]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".component.SimpleManagedBean.START
Missing[JBAS014861: <one or more transitive dependencies>]"]}
{code}
This is probably because of this code in BundleContextBindingProcessor
{code}
if (comp.getNamingMode() == ComponentNamingMode.CREATE) {
ServiceName serviceName =
contextServiceNameOfComponent(moduleDesc.getApplicationName(), moduleDesc.getModuleName(),
comp.getComponentName());
bindServices(depUnit, serviceTarget, moduleDesc, comp.getComponentName(),
serviceName);
}
{code}
The namingMode == USE_MODULE and the BundleContextdoes not get bound.
Is this binding logic correct?
--
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
2:26 p.m.
[
https://issues.jboss.org/browse/AS7-5147?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-5147:
-------------------------------------
See BundleContextManagedBeanInjectionTestCase in branch
[as5147|https://github.com/tdiesler/jboss-as/tree/as5147]
@Resource injection of BundleContext into ManagedBean fails
-----------------------------------------------------------
Key: AS7-5147
URL: https://issues.jboss.org/browse/AS7-5147
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Web
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.3.0.Alpha1
@Resource BundleContext injection fails with
{code}
21:04:12,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.ear"
21:04:12,987 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.jar"
21:04:12,988 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876:
Starting deployment of "managed-bean.war"
21:04:13,066 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002:
Processing weld deployment managed-bean.ear
21:04:13,097 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002:
Processing weld deployment managed-bean.war
21:04:13,099 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002:
Processing weld deployment managed-bean.jar
21:04:13,114 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005:
Starting Services for CDI deployment: managed-bean.ear
21:04:13,137 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear:main" from Service Module Loader
21:04:13,141 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008:
Starting weld service for deployment managed-bean.ear
21:04:13,187 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.war:main" from Service
Module Loader
21:04:52,328 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.jar:main" from Service
Module Loader
21:04:52,402 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web
context: /managed-bean.war
21:04:52,607 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS015870:
Deploy of deployment "managed-bean.ear" was rolled back with failure message
{"JBAS014771: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".env.\"org.jboss.as.test.integration.osgi.resource.SimpleManagedBean\".context
Missing[jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".BundleContext]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".jndiDependencyService
Missing[JBAS014861: <one or more transitive
dependencies>]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".component.SimpleManagedBean.START
Missing[JBAS014861: <one or more transitive dependencies>]"]}
{code}
This is probably because of this code in BundleContextBindingProcessor
{code}
if (comp.getNamingMode() == ComponentNamingMode.CREATE) {
ServiceName serviceName =
contextServiceNameOfComponent(moduleDesc.getApplicationName(), moduleDesc.getModuleName(),
comp.getComponentName());
bindServices(depUnit, serviceTarget, moduleDesc, comp.getComponentName(),
serviceName);
}
{code}
The namingMode == USE_MODULE and the BundleContextdoes not get bound.
Is this binding logic correct?
--
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
3:29 p.m.
[
https://issues.jboss.org/browse/AS7-5147?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-5147:
--------------------------------
Fix Version/s: 7.2.0.CR1
(was: 7.3.0.Alpha1)
@Resource injection of BundleContext into ManagedBean fails
-----------------------------------------------------------
Key: AS7-5147
URL: https://issues.jboss.org/browse/AS7-5147
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Web
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.CR1
@Resource BundleContext injection fails with
{code}
21:04:12,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.ear"
21:04:12,987 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.jar"
21:04:12,988 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876:
Starting deployment of "managed-bean.war"
21:04:13,066 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002:
Processing weld deployment managed-bean.ear
21:04:13,097 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002:
Processing weld deployment managed-bean.war
21:04:13,099 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002:
Processing weld deployment managed-bean.jar
21:04:13,114 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005:
Starting Services for CDI deployment: managed-bean.ear
21:04:13,137 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear:main" from Service Module Loader
21:04:13,141 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008:
Starting weld service for deployment managed-bean.ear
21:04:13,187 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.war:main" from Service
Module Loader
21:04:52,328 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.jar:main" from Service
Module Loader
21:04:52,402 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web
context: /managed-bean.war
21:04:52,607 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS015870:
Deploy of deployment "managed-bean.ear" was rolled back with failure message
{"JBAS014771: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".env.\"org.jboss.as.test.integration.osgi.resource.SimpleManagedBean\".context
Missing[jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".BundleContext]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".jndiDependencyService
Missing[JBAS014861: <one or more transitive
dependencies>]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".component.SimpleManagedBean.START
Missing[JBAS014861: <one or more transitive dependencies>]"]}
{code}
This is probably because of this code in BundleContextBindingProcessor
{code}
if (comp.getNamingMode() == ComponentNamingMode.CREATE) {
ServiceName serviceName =
contextServiceNameOfComponent(moduleDesc.getApplicationName(), moduleDesc.getModuleName(),
comp.getComponentName());
bindServices(depUnit, serviceTarget, moduleDesc, comp.getComponentName(),
serviceName);
}
{code}
The namingMode == USE_MODULE and the BundleContextdoes not get bound.
Is this binding logic correct?
--
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
3:59 a.m.
[
https://issues.jboss.org/browse/AS7-5147?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-5147:
--------------------------------
Fix Version/s: 7.2.0.Alpha1
(was: 7.2.0.CR1)
Git Pull Request: https://github.com/jbossas/jboss-as/pull/2651 (was:
https://github.com/jbossas/jboss-as/pull/2651)
@Resource injection of BundleContext into ManagedBean fails
-----------------------------------------------------------
Key: AS7-5147
URL: https://issues.jboss.org/browse/AS7-5147
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Web
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
@Resource BundleContext injection fails with
{code}
21:04:12,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.ear"
21:04:12,987 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "managed-bean.jar"
21:04:12,988 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876:
Starting deployment of "managed-bean.war"
21:04:13,066 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002:
Processing weld deployment managed-bean.ear
21:04:13,097 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002:
Processing weld deployment managed-bean.war
21:04:13,099 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002:
Processing weld deployment managed-bean.jar
21:04:13,114 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005:
Starting Services for CDI deployment: managed-bean.ear
21:04:13,137 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear:main" from Service Module Loader
21:04:13,141 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008:
Starting weld service for deployment managed-bean.ear
21:04:13,187 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.war:main" from Service
Module Loader
21:04:52,328 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register
module: Module "deployment.managed-bean.ear.managed-bean.jar:main" from Service
Module Loader
21:04:52,402 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web
context: /managed-bean.war
21:04:52,607 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS015870:
Deploy of deployment "managed-bean.ear" was rolled back with failure message
{"JBAS014771: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".env.\"org.jboss.as.test.integration.osgi.resource.SimpleManagedBean\".context
Missing[jboss.naming.context.java.module.managed-bean.\"managed-bean.jar\".BundleContext]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".jndiDependencyService
Missing[JBAS014861: <one or more transitive
dependencies>]","jboss.deployment.subunit.\"managed-bean.ear\".\"managed-bean.jar\".component.SimpleManagedBean.START
Missing[JBAS014861: <one or more transitive dependencies>]"]}
{code}
This is probably because of this code in BundleContextBindingProcessor
{code}
if (comp.getNamingMode() == ComponentNamingMode.CREATE) {
ServiceName serviceName =
contextServiceNameOfComponent(moduleDesc.getApplicationName(), moduleDesc.getModuleName(),
comp.getComponentName());
bindServices(depUnit, serviceTarget, moduleDesc, comp.getComponentName(),
serviceName);
}
{code}
The namingMode == USE_MODULE and the BundleContextdoes not get bound.
Is this binding logic correct?
--
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
4566
days inactive
4567
days old
5 comments
1 participants
participants (1)
-
Thomas Diesler (JIRA)