[weld-issues] [JBoss JIRA] Commented: (CDITCK-59) EAR package is not portable

[Santiago Pericas-Geertsen (JIRA)]

    [ https://jira.jboss.org/jira/browse/CDITCK-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12496085#action_12496085 ] 

Santiago Pericas-Geertsen commented on CDITCK-59:
-------------------------------------------------

The error is slightly different, but it appears the following tests are also missing a Class-Path:

*.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest.testCreateSFSB
*.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest.testCreateSLSB
*.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest.testDestroyRemovesSFSB
*.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest.testRemovedEjbIgnored
*.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest.testSerializeSFSB



> EAR package is not portable
> ---------------------------
>
>                 Key: CDITCK-59
>                 URL: https://jira.jboss.org/jira/browse/CDITCK-59
>             Project: CDI TCK
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Tests
>    Affects Versions: 1.0.0.GA
>         Environment: Solaris x86 / JDK 6u16 / GF v3
>            Reporter: Santiago Pericas-Geertsen
>             Fix For: 1.0.1.CR1
>
>
> The following TCK tests,
> testInjectionOfDependentPrimitiveProductIntoNormalBean
> testInjectionOfDependentSerializableProductIntoNormalBean
> testNonSerializableProducerFieldDeclaredPassivatingThrowsIllegalProductException
> testPassivatingScopeProducerMethodReturnsUnserializableObjectNotOk
> related to the EAR,
> org.jboss.jsr299.tck.tests.context.passivating.PassivatingContextTest.ear 
> fail with the following exception in GF v3,
> attached to this wiki [1] which generates the following exception when deployed:
> java.lang.RuntimeException: by java.lang.IllegalAccessError: class org.jboss.jsr299.tck.tests.context.passivating.NumberConsumer_$$_javassist_389 cannot access its superclass org.jboss.jsr299.tck.tests.context.passivating.NumberConsumer
>        at javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:344)
>        at javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:314)
>        at javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:273)
>        at org.jboss.weld.util.Proxies.createProxyClass(Proxies.java:153)
>        at org.jboss.weld.util.Proxies.createProxy(Proxies.java:136)
> The reason for this failure is that the WAR in the EAR above does not include a Class-Path entry in its manifest to be able to load classes from the JAR. This manifest entry is required for portability. Note that GF v3 now uses the TCCL with Javassist.

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