Igor Drobiazko
added a comment - 05/Aug/10 14:27 - edited There are even more problems: if you have an abstract service class containing protected or package private abstract methods, your app will fail with a java.lang.AbstractMethodError.

The "class loading" umbrella has been extended in such a way that inner classes and other classes within the same package should now be loaded correctly, with the same class loader. This issue can be re-opened (or cloned, after 5.2.1 is released) if new use cases come up.

Howard M. Lewis Ship
added a comment - 01/Sep/10 00:06 The "class loading" umbrella has been extended in such a way that inner classes and other classes within the same package should now be loaded correctly, with the same class loader. This issue can be re-opened (or cloned, after 5.2.1 is released) if new use cases come up.

Antal van Kalleveen
added a comment - 11/Oct/11 12:16 I've found that there is still an issue that is closely related to this one:
Detailed info and code to reproduce can be found here: http://tapestry.1045711.n5.nabble.com/TAP5-1233-re-open-java-lang-IllegalAccessError-td4864790.html
Still could be a 'feature' but it is not clearly documented , otherwise i think its a bug.