签名罐的AspectJ加载时编织 [英] AspectJ load-time weaving for signed jars

问题描述

有人在将签名的jars与AspectJ加载时编织一起使用时是否成功?

Does anybody success in using AspectJ load-time weaving with signed jars?

我有一个异常，不知道如何解决(已通过AspectJ 1.6.8-16.10测试):

I got an exception and have no idea how to fix it (tested with AspectJ 1.6.8-16.10):

Exception in thread "main" java.lang.NoClassDefFoundError: com/package/clazz$AjcClosure1
    at com.package.test.main(test.java:55)
Caused by: java.lang.ClassNotFoundException: com.package.clazz$AjcClosure1
    at java.net.URLClassLoader$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    ... 1 more

坦率地说，我不确定在技术上是否可行，但我知道Hibernate项目(使用Javassist代替CGLIB)也发生了类似的问题(使用来自签名的Java类的动态生成的Java代码).详细信息在此处.

Frankly speaking I event not sure if it's technically possible, but I know that similar issue (using dynamically generated java code from signed java classes) was done for Hibernate project (i.e. using Javassist instead of CGLIB). Details are here.

推荐答案

https://bugs.eclipse.org/bugs/show_bug.cgi?id=328099 ，并在AspectJ 1.6.12中进行了修复. AspectJ有时在编织过程中生成闭包类，并且必须使用与引起它们的jar相同的保护域来定义它们.在1.6.12.M1中，现在应该可以正常工作了.

The simular problem is described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=328099 and fixed in AspectJ 1.6.12. AspectJ sometimes generates closure classes during weaving and these must be defined with the same protection domain as the jar that gave rise to them. In 1.6.12.M1 this should now work correctly.

这篇关于签名罐的AspectJ加载时编织的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！