[ https://issues.apache.org/jira/browse/OPENJPA-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790603#comment-13790603 ]
Mark Struberg commented on OPENJPA-2283: ---------------------------------------- [~kwsutter] oki, gonna fix the ordering to xbean-asm4, xbean-asm3, spring-asm, asm-native [~rgcurtis] I think the wrong ClassLoader comes from the fact that the input class byte array comes from the BCClass instance in the PCEnhancer. So you will most probably always get the ClassLoader which loads OpenJPA itself. But this is wrong for nested ClassLoaders. We need the ClassLoader from the Class which gets enhanced at all. Please note that this will most probably only have an impact if the enhancement gets done at runtime. Doing further debugging atm and try to create a unit test. Gonna fix this in 2.3.x and trunk. > Upgrade to ASM 4 dependency > --------------------------- > > Key: OPENJPA-2283 > URL: https://issues.apache.org/jira/browse/OPENJPA-2283 > Project: OpenJPA > Issue Type: New Feature > Components: Enhance > Affects Versions: 2.3.0 > Reporter: Kevin Sutter > Fix For: 2.3.0 > > Attachments: openjpa-2283.problem.patch > > > OpenJPA currently has a dependency on ASM 3.2 for some post-enhancement > processing to fix up the stack map tables (Java 7 requirement). The latest > release of ASM is 4.1, which just came out last week. The immediate need is > to move up to ASM 4.0. We can entertain 4.1 at a later date. -- This message was sent by Atlassian JIRA (v6.1#6144)