[seam-issues] [JBoss JIRA] (JBSEAM-4840) ProxyFactory with old Javassist bugs

[Marek Novotny (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBSEAM-4840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638398#comment-12638398 ] 

Marek Novotny commented on JBSEAM-4840:
---------------------------------------

It seems, that this issue requires to update javassist bundled in JBoss Embedded beta3.SP10.

Error Message

javassist.util.proxy.RuntimeSupport.find2Methods(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/reflect/Method;)V

Stacktrace

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(org.jboss.seam.Component:1461)
	at org.jboss.seam.Component.postConstruct(org.jboss.seam.Component:1379)
	at org.jboss.seam.Component.newInstance(org.jboss.seam.Component:2155)
	at org.jboss.seam.contexts.Contexts.startup(org.jboss.seam.contexts.Contexts:304)
	at org.jboss.seam.contexts.Contexts.startup(org.jboss.seam.contexts.Contexts:278)
	at org.jboss.seam.contexts.ServletLifecycle.endInitialization(org.jboss.seam.contexts.ServletLifecycle:143)
	at org.jboss.seam.init.Initialization.init(org.jboss.seam.init.Initialization:744)
	at org.jboss.seam.mock.AbstractSeamTest.startSeam(org.jboss.seam.mock.AbstractSeamTest:929)
	at org.jboss.seam.mock.SeamTest.startSeam(org.jboss.seam.mock.SeamTest:69)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:609)
	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:421)
	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:158)
	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:89)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:284)
	at org.testng.SuiteRunner.run(SuiteRunner.java:204)
	at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:912)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:876)
	at org.testng.TestNG.run(TestNG.java:784)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:73)
	at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:94)
	at org.apache.maven.surefire.Surefire.run(Surefire.java:169)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)

                
> ProxyFactory with old Javassist bugs
> ------------------------------------
>
>                 Key: JBSEAM-4840
>                 URL: https://issues.jboss.org/browse/JBSEAM-4840
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.2.2.Final
>            Reporter: Martin Höller
>            Assignee: Marek Novotny
>              Labels: javassist, nullpointerexception
>             Fix For: 2.3.0.BETA1
>
>
> Seam brings its own copy of Javassist's ProxyFactory class. Thus bugfixes from the javassist can survive in Seam for a long time.
> The concrete problem is a NullPointerException that was reported as JASSIST-66 and fixed in 2008.
> See the linked forum article for a more detailed description.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira