Github user PhantomYdn commented on the pull request:
https://github.com/apache/wicket/pull/164#issuecomment-217636415
@klopfdreh , first of all let me mention that I used javassist, but I
haven't try yet to use IClassResolver. If we are talking just about javassist -
it can definitely to exactly the same and even more rather that AspectJ - just
because it's more low level in bytecode manipulations rather then AspectJ. But
if we are talking about wicket IClassResolver capabilities: I don't have much
experience in that, but according to sources it's being used for every
requested page and assuming that requests have small amount of intersections -
it looks pretty OK just in runtime instrument page for one request and do not
instrument it for another.
How to measure. There is brief description:
http://www.ibm.com/developerworks/library/j-dyn0916/
http://jboss-javassist.github.io/javassist/tutorial/tutorial.html
Let me actually try to implement what I'm saying and comeback with some
PoC. It will be much more fair:)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
