[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-861) class not found error javax.interceptor.InvocationContext when running hibernate2 example on head

youngm (JIRA) jira-events at lists.jboss.org
Fri Feb 16 15:37:39 EST 2007


    [ http://jira.jboss.com/jira/browse/JBSEAM-861?page=comments#action_12353405 ] 
            
youngm commented on JBSEAM-861:
-------------------------------

Ya, I'm baffled.  The exception is being thrown when JavaBeanInterceptor is first loaded by the classloader.  I'm not too experienced with classloaders and bytecode but when java loads a class and it's dependencies can it selectively only load classes that it thinks is goinig to eventually be executed?  If java just loads all dependent classes then how was this working in 1.1.6?

Ya, this issue is officially out of my league. :)

This may be a dumb question but where there any dependency changes?  Was the EE5 jars somehow accidentally making it into the war in 1.1.6?

Mike

> class not found error javax.interceptor.InvocationContext when running hibernate2 example on head
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-861
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-861
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.7.GA
>            Reporter: youngm
>             Fix For: 1.1.7.GA
>
>
> class not found error javax.interceptor.InvocationContext when running hibernate2 example in jboss.
> The source of the problem appears to be the addition of "new EE5SeamInvocationContext" in RootInterceptor:145.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list