[
https://issues.jboss.org/browse/JBJCA-1137?page=com.atlassian.jira.plugin...
]
Darryl Miles commented on JBJCA-1137:
-------------------------------------
Fair enough, but it is an NPE.
The CNFE is handled gracefully further up the stack trace (by annotation lookup). It is
gracefully handled by returning null.
The code in o.j.j.c.CommonBundle.Annotations#processConfigProperty() line:765 then tried
to dereference this null. Which is an error.
Regardless of "class loading issues".
NPE in o.j.j.c.CommonBundle.Annotations#processConfigProperty()
line:765
------------------------------------------------------------------------
Key: JBJCA-1137
URL:
https://issues.jboss.org/browse/JBJCA-1137
Project: IronJacamar
Issue Type: Bug
Components: Common
Affects Versions: 1.1.2.Final
Reporter: Darryl Miles
Assignee: Jesper Pedersen
org.jboss.jca.common.CommonBundle.Annotations
Map<Metadatas, ArrayList<ConfigProperty16>>
processConfigProperty(AnnotationRepository annotationRepository, ClassLoader classLoader)
for (Annotation annotation : values)
{
javax.resource.spi.ConfigProperty configPropertyAnnotation =
(javax.resource.spi.ConfigProperty) annotation
.getAnnotation();
if (trace)
log.trace("Processing: " + configPropertyAnnotation);
XsdString configPropertyValue = XsdString.NULL_XSDSTRING;
if (configPropertyAnnotation.defaultValue() != null &&
!configPropertyAnnotation.defaultValue().equals(""))
configPropertyValue = new
XsdString(configPropertyAnnotation.defaultValue(), null);
javax.resource.spi.ConfigProperty configPropertyAnnotation =
(javax.resource.spi.ConfigProperty) annotation.getAnnotation();
can return null when there is ClassNotFoundException for the class with the annotation in
it.
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166)
[wildfly-server-8.0.0.CR1.jar:8.0.0.CR1]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
[jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
[jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
Caused by: java.lang.IllegalArgumentException: JBAS017220: Class not found
at org.jboss.as.service.ReflectionUtils.getClass(ReflectionUtils.java:115)
at org.jboss.as.service.ReflectionUtils.getClassHierarchy(ReflectionUtils.java:122)
at
org.jboss.as.service.ParsedServiceDeploymentProcessor.addServices(ParsedServiceDeploymentProcessor.java:113)
at
org.jboss.as.service.ParsedServiceDeploymentProcessor.deploy(ParsedServiceDeploymentProcessor.java:104)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159)
[wildfly-server-8.0.0.CR1.jar:8.0.0.CR1]
... 5 more
Caused by: java.lang.ClassNotFoundException: com.domain.project.ejb.mbean.Monitor from
[Module
"deployment.com.domain.project.ear.ear.com-domain-project.ejb-0.0.1-SNAPSHOT.jar:main"
from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197)
[jboss-modules.jar:1.3.0.Final]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
[jboss-modules.jar:1.3.0.Final]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
[jboss-modules.jar:1.3.0.Final]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
[jboss-modules.jar:1.3.0.Final]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
[jboss-modules.jar:1.3.0.Final]
at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_25]
at java.lang.Class.forName(Class.java:270) [rt.jar:1.7.0_25]
at org.jboss.as.service.ReflectionUtils.getClass(ReflectionUtils.java:113)
... 9 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira