[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4001) Wicket Instrumentation Annotation
Clint Popetz (JIRA)
jira-events at lists.jboss.org
Thu Mar 12 11:42:22 EDT 2009
[ https://jira.jboss.org/jira/browse/JBSEAM-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12456939#action_12456939 ]
Clint Popetz commented on JBSEAM-4001:
By the way, this annotation can't work at runtime, only at build time. In order to instrument at runtime, we have to keep the classes in question from being loaded by the normal webapp classloader, which we can't do unless they live in their own directory.
As far as not re-instrumented classes that have already been instrumented, that's already fixed: https://jira.jboss.org/jira/browse/JBSEAM-3979
> Wicket Instrumentation Annotation
> Key: JBSEAM-4001
> URL: https://jira.jboss.org/jira/browse/JBSEAM-4001
> Project: Seam
> Issue Type: Feature Request
> Components: Wicket
> Reporter: Paul Mooney
> Assignee: Clint Popetz
> Instrument wicket classes which are annotated with a seam annotation (something like @WicketComponent), as well as all of their non-static nested classes (including anonymous).
> This would be an alternative to the current approach of using filesets or package patterns to determine which classes to pass to the JavassistInstrumentor (either via ant,maven, or javaagent).
> As well, if possible, this may be an alternative to placing wicket classes in WEB-INF/wicket at runtime. In this case some configuration might be needed to enable/disable runtime instrumentation in order to avoid attempts to re-instrument classes which have already been instrumented at buildtime.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues