[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-4001) Wicket Instrumentation Annotation

[Clint Popetz (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clint Popetz closed JBSEAM-4001.
--------------------------------

    Fix Version/s: 2.1.2.CR1
       Resolution: Done


Committed r10147.

There is now a "SeamWicketComponent" annotation.  Any class annotated with this, as well as its non-static inner classes, will be instrumented, controlled in the following way:

(a) The ant task now takes an optional "useAnnotations" attribute, which defaults to false for backwards compatibility.  You still have to pass it a set of classes, but you can now pass the entire set of built classes and set this attribute, and then annotate the classes you want instrumented.

(b) The runtime -javaagent approach still needs a set of packages to examine, for efficiency, but it will only instrument classes in these packages which are annotated if the system property -Dorg.jboss.seam.wicket.scanAnnotations=true is set.

(c) The WEB-INF/wicket approach does not respect the annotation, as it is assumed that if you are able to select which classes go in WEB-INF/wicket, you'll select the right ones.

(d) The maven plugin will be updated shortly to be configured for the annotation.

> 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
>             Fix For: 2.1.2.CR1
>
>
> 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