[weld-issues] [JBoss JIRA] Commented: (CDITCK-56) mispackaged application caused deployment failure on glassfish v3
[
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.
mispackaged application caused deployment failure on glassfish v3
-----------------------------------------------------------------
Key: CDITCK-56
URL: https://jira.jboss.org/jira/browse/CDITCK-56
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Tests
Affects Versions: 1.0.0.GA
Environment: Ubuntu/X86
Reporter: Hong Zhang
Priority: Critical
Fix For: 1.0.1.CR1
During test run,
org.jboss.jsr299.tck.tests.implementation.simple.definition.SimpleBeanDefinitionTest.ear
failed to deploy on glassfish v3.
Looking at the ear packaging, it seems this application was mispackaged which caused the
deployment failure:
SimpleBeanDefinitionTest.jar is declared as an ejb jar in application.xml. But the
ejb-jar.xml inside this jar does not define any EJBs, and none of the packaged classes in
this jar contain any ejb component annotations (@Stateless, @Stateful, @MessageDriven,
@Singleton).
--
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