[seam-dev] Seam 2.x dependency on Javassist and how to check for regressions when using a newer Javassist version...

[Marek Schmidt]

Use

mvn clean install -Darquillian=jbossas-managed-7

(to run on AS7.1.1.Final)

or

mvn clean install -Darquillian=jbossas-remote-7

on an remote AS7/EAP6

On 12/07/13 23:18, Scott Marlow wrote:
> Hi Marek,
>
> Thanks, I was able to recreate after downloading the Seam 2.x latest.  I
> have a potential Javassist change that I'm looking into (seems to get us
> further in the Seam testsuite :-).
>
> When I do "mvn clean install test" from seam dev root, I get a "Seam
> Integration Tests" failure https://gist.github.com/scottmarlow/5987861
>
> I get the same failure, even if I revert the jboss-seam upgrade to use
> the newer Javassist 3.18.0 version, so I suspect its something else
> (maybe an expected error that requires a workaround?).
>
> If the failed test also uses Javassist, I would like to run it also.
>
> Thanks,
> Scott
>
> On 07/11/2013 04:11 PM, Marek Novotny wrote:
>> hey Scott,
>>
>>    thanks for notification.
>>
>> Dne 11.7.2013 16:43, Scott Marlow napsal(a):
>>> https://issues.jboss.org/browse/JASSIST-206 is about a Javassist 3.18.0
>>> signature change that broke Seam 2.x applications.
>>>
>>> Could someone let me know if the Seam 2.x testsuite also hits the same
>>> regression when using Javassist 3.18.0?
>> yes, the latest working javassist version is 3.16.1-GA and the above
>> issue has got correct affected versions which breaks all Seam 2.x versions.
>>
>> pure Seam core unit test shows the failure org.jboss.seam.test.unit.CoreTest
>>
>> Tests run: 120, Failures: 1, Errors: 0, Skipped: 119, Time elapsed:
>> 2.533 sec <<< FAILURE!
>> triggerComponentScan(org.jboss.seam.test.unit.CoreTest)  Time elapsed:
>> 2203 sec  <<< FAILURE!
>> java.lang.NoSuchMethodError:
>> javassist.util.proxy.RuntimeSupport.find2Methods(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/reflect/Method;)V
>> 	at
>> org.jboss.seam.el.JBossELReferenceCache_$$_javassist_seam_0.writeReplace(JBossELReferenceCache_$$_javassist_seam_0.java)
>> 	at org.jboss.seam.Component.postConstructJavaBean(Component.java:1465)
>> 	at org.jboss.seam.Component.postConstruct(Component.java:1382)
>> 	at org.jboss.seam.Component.newInstance(Component.java:2193)
>> 	at org.jboss.seam.contexts.Contexts.startup(Contexts.java:343)
>> 	at org.jboss.seam.contexts.Contexts.startup(Contexts.java:317)
>> 	at
>> org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:143)
>> 	at org.jboss.seam.init.Initialization.init(Initialization.java:813)
>> 	at org.jboss.seam.test.unit.CoreTest.triggerComponentScan(CoreTest.java:22)
>>
>>
>> Results :
>>
>> Failed tests:   triggerComponentScan(org.jboss.seam.test.unit.CoreTest):
>> javassist.util.proxy.RuntimeSupport.find2Methods(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/reflect/Method;)V
>>
>>>
>>> I'm trying to answer a related question about how we can tell if a
>>> patched Javassist 3.15.x still works with Seam 2.x applications.  If
>>> running the Seam 2.x testsuite hits the JASSIST-206, it might be good
>>> for us to run the Seam 2.x testsuite after patching/upgrading Javassist.
>>
>>
>>>
>>> Thanks for your advise.
>>>
>>> Scott
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>
>>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>