[ https://jira.jboss.org/jira/browse/CDITCK-56?page=com.atlassian.jira.plug... ] Hong Zhang updated CDITCK-56: ----------------------------- Summary: mispackaged application caused deployment failure on glassfish v3 (was: mispackaged application (SimpleBeanDefinitionTest.ear) caused deployment failure on glassfish v3) I am making this issue a more general issue for this type of deployment failure as I discovered a few more similar cases when looking at the test failures from deployment package. The glassfish validates the ejb jar (make sure the declared ejb jar contains at least one EJB) during deployment, and will fail deployment if the ejb jar is not valid. JBoss code probably does not have this validation so application which deploys successfully on JBoss could fail to deploy on glassfish. The mis-packaged applications should be fixed to contain valid ejb jar to be JavaEE compliant. These are the applications I found in the deployment package that failed to deploy due to the invalid ejb jar (no EJB found in the ejb jar): org.jboss.jsr299.tck.tests.deployment.lifecycle.broken.failsDuringBeanDiscovery.DeploymentFailureTest.ear#DeploymentFailureTest.jar org.jboss.jsr299.tck.tests.deployment.packaging.bundledLibrary.LibraryInEarTest.ear#LibraryInEarTest.jar org.jboss.jsr299.tck.tests.deployment.packaging.installedLibrary.EarInstalledLibraryTest.ear#EarInstalledLibraryTest.jar I will make more updates to this issue as I go through other packages. -- 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

[ https://jira.jboss.org/jira/browse/CDITCK-56?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-56: ---------------------------- Issue Type: Bug (was: CTS Challenge) -- 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

[ https://jira.jboss.org/jira/browse/CDITCK-56?page=com.atlassian.jira.plug... ] Hong Zhang commented on CDITCK-56: ---------------------------------- I just talked to Ken Saks who is the EJB3.1 spec lead about this. This is the spec section he pointed to me: 20.1 Packaging: An ejb-jar file produced by the Bean Provider contains one or more enterprise beans that typically do not contain application assembly instructions. And his additional comments on this: The only purpose of an ejb-jar is to define ejb components. The fact that some of its classes may be visible to other modules in the .ear is a separate issue. It's not intended to act purely as a library .jar. -- 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

[ https://jira.jboss.org/jira/browse/CDITCK-56?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-56: ---------------------------- Fix Version/s: 1.1.0.CR1 -- 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