Github user klopfdreh commented on the pull request:
https://github.com/apache/wicket/pull/164#issuecomment-217790358
I just googled a bit about javassist and aspectj and a good page which
describes the dis-/advantages of both frameworks is:
https://theholyjava.wordpress.com/2011/09/07/practical-introduction-into-code-injection-with-aspectj-javassist-and-java-proxy/
> Javassist has no tools to perform the injection and you thus have to
implement your own injection code â including that there isnât support for
injecting the code automatically based on a pattern
I think this may increase the work to do, because every single annotation
provided by the different metrics have to be implemented in a programmatic way.
GluonJ requires an Agent if you don't want to compile classes again and want to
use some annotations to hook into.
So my point still exists:
If you don't want to compile the classes again - also core classes (which
is actually a code manipulation and might influence the existing behavior) you
have to use an agent and this is something we don't want to with metrics.
In your example you only used your own classes and not core classes like
Component - I think you will not be able to apply the programmatic javassist
metrics there.
---
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.
---
