Github user PhantomYdn commented on the pull request:
https://github.com/apache/wicket/pull/164#issuecomment-217772405
Yes - that's also possible. Regarding changing of a technology: that was
NOT my main point. There are just few additional requirements which will be
good to cover and I just see/know how to do that with the aid of javassist. If
you can do that with AspectJ: it would be also great.
Requirements:
1) No Java agent required for gathering metrics
2) Metrics can be enabled:
a) for everyone
b) just for designated user's sessions
c) for all pages and component
d) for selective set of component
3) Bouncing of a server is not required after configuration change
4) Metrics reporting might be plugable
Yea - when I will have more time - will try to replace AspectJ. (As I said
before, I think that everything which AspectJ have - can be covered by
Javassist - just because last one is more low level and both have the same
inner nature.)
---
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.
---
