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

Bahata Mukhopadhyay (JIRA) jira-events at lists.jboss.org
Wed Mar 26 21:57:49 EDT 2008


    [ http://jira.jboss.com/jira/browse/JBAOP-548?page=comments#action_12405006 ] 
            
Bahata Mukhopadhyay commented on JBAOP-548:
-------------------------------------------

Hi
Using the Habanero Pojo Cache , load time instrumentaiton with JDK 1.5 and hibernate , I am getting the same 2 warnings.

> 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
>             Fix For: 1.3.5
>
>
> 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

        



More information about the jboss-jira mailing list