Yes, it comes from metadata. The tests fail to deploy. Emanuel is going
to look into it.
Caused by: java.lang.IllegalArgumentException: Can't find interface null
in
org.jboss.metadata.ejb.jboss.JBossSessionBeanMetaData@af9ed402{AuditSessionEJB}
at
org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.determineResolvedJndiName(JBossEnterpriseBeanMetaData.java:702)
at
org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.mapEjbs(MappedReferenceMetaDataResolverDeployer.java:332)
at
org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.mapEndpoints(MappedReferenceMetaDataResolverDeployer.java:219)
at
org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.internalDeploy(MappedReferenceMetaDataResolverDeployer.java:140)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
Dimitris Andreadis wrote:
I suspect this huge regression (+1162 failures) is related to the
recent
jboss-metadata update:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...