[
http://jira.jboss.com/jira/browse/JBSEAM-861?page=comments#action_12353407 ]
Gavin King commented on JBSEAM-861:
-----------------------------------
"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?"
Yes it can, but I'm not sure exactly what the rules are.
One obvious way to fix this is to use reflection to instantiate EE5InvocationContext. But
it seems strange that this is necessary....
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