[jboss-jira] [JBoss JIRA] Updated: (JBAOP-548) CLONE -JBoss AOP load-time classloader doesn't work with Hibernate

[Kabir Khan (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAOP-548?page=all ]

Kabir Khan updated JBAOP-548:
-----------------------------

    Fix Version/s:     (was: 1.3.5)

1.3.x is out of date. Please try 1.5.6 or the upcoming 2.0.0.CR8.

The error you are describing is not really a problem, here are some links explaining why
http://www.jboss.com/?module=bb&op=viewtopic&t=86988
http://www.jboss.com/?module=bb&op=viewtopic&t=127489

In general, unless you are an expert user who knows the project quite well :-), please discuss these things on our user forum before creating JIRA issues

> CLONE -JBoss AOP load-time classloader doesn't work with Hibernate
> ------------------------------------------------------------------
>
>                 Key: JBAOP-548
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-548
>             Project: JBoss AOP
>          Issue Type: Bug
>    Affects Versions: 1.3.4
>            Reporter: Bahata Mukhopadhyay
>            Priority: Blocker
>
> Using latest H3 and JBoss AOP release on JDK 1.4. I'm trying to get the custom boot classloader to work. Followed the instructions. Exceptions at runtime:
> ------------- Standard Error -----------------
> [warn] Could not find class org.jaxen.VariableContext that org.dom4j.DocumentFactory references.  It may not be in your classpath and you may not be getting field and constructor weaving for this class.
> [warn] Could not find class org.objectweb.asm.util.TraceClassVisitor that net.sf.cglib.core.DebuggingClassWriter$1 references.  It may not be in your classpath and you may not be getting field and constructor weaving for this class.
> [error] null.. Do verbose mode if you want full stack trace.   
> I might very well be the first person to try to use the combination of JBoss AOP, load-time enhancement in JDK 1.4, and Hibernate. I'd say this is the most popular combination. Adding dom4j and CGLIB to the bootclasspath solves the issues here. However, I get a different useless exception with no message then. 
> I've attached a small project that includes everything to reproduce this problem. You can modify the build file to toy with the boothclasspath.

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