[jboss-jira] [JBoss JIRA] Resolved: (JBAS-7288) AnnotationMetaDataDeployer failing with NoClassDefFoundError

Thomas Diesler (JIRA) jira-events at lists.jboss.org
Thu Sep 24 16:47:49 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBAS-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler resolved JBAS-7288.
----------------------------------

    Resolution: Done


Done

	  // Allow deployment units to say that they are metadata complete
	  // in terms of annotation processing
      if (isComplete == false)
      {
    	  Boolean unitComplete = unit.getAttachment(ANNOTATION_META_DATA_COMPLETE, Boolean.class);
    	  isComplete = Boolean.TRUE.equals(unitComplete);
      }


> AnnotationMetaDataDeployer failing with NoClassDefFoundError
> ------------------------------------------------------------
>
>                 Key: JBAS-7288
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7288
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: JBossAS-5.2.0.Beta1
>
>
> OSGi bundle deployments fail related to unwanted annotation processing
> Caused by: java.lang.NoClassDefFoundError: javax/persistence/PersistenceContext
> 	at org.jboss.metadata.annotation.creator.AbstractPersistenceContextProcessor.getAnnotationTypes(AbstractPersistenceContextProcessor.java:107)
> 	at org.jboss.metadata.annotation.creator.AbstractProcessor.getProcessorMetaDataType(AbstractProcessor.java:322)
> 	at org.jboss.metadata.annotation.creator.AbstractProcessor.addFieldProcessor(AbstractProcessor.java:92)
> 	at org.jboss.metadata.annotation.creator.jboss.AbstractComponentProcessor.<init>(AbstractComponentProcessor.java:85)
> 	at org.jboss.metadata.annotation.creator.ejb.jboss.AbstractEnterpriseBeanProcessor.<init>(AbstractEnterpriseBeanProcessor.java:60)
> 	at org.jboss.metadata.annotation.creator.ejb.jboss.AbstractSessionBeanProcessor.<init>(AbstractSessionBeanProcessor.java:52)
> 	at org.jboss.metadata.annotation.creator.ejb.jboss.StatefulProcessor.<init>(StatefulProcessor.java:49)
> 	at org.jboss.metadata.annotation.creator.ejb.jboss.JBoss50Creator.<init>(JBoss50Creator.java:74)
> 	at org.jboss.metadata.annotation.creator.ejb.jboss.JBoss50Creator.<init>(JBoss50Creator.java:84)
> 	at org.jboss.deployment.OptAnnotationMetaDataDeployer.processJBossMetaData(OptAnnotationMetaDataDeployer.java:132)
> 	at org.jboss.deployment.OptAnnotationMetaDataDeployer.processMetaData(OptAnnotationMetaDataDeployer.java:84)
> 	at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:177)
> 	at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:93)
> 	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)

-- 
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

        



More information about the jboss-jira mailing list