[seam-issues] [JBoss JIRA] Updated: (JBSEAM-4545) Extend wicket instrumentation functionality to support other types of dependency injection

[Kariem Hussein (JIRA)]

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

Kariem Hussein updated JBSEAM-4545:
-----------------------------------

    Attachment: ioc-extensible-instrumentation.patch
                ioc-extensible-instrumentation-mojo.patch


Proposed changes as provided in patches:

* file 1: patch on jboss-seam-wicket module:
Make JavassistInstrumentor implement an interface (ClassInstrumentor) and provide a corresponding factory. Handler and component class names that are the center of instrumentation can be overwritten by subclasses. In addition, change visibility of add(Member) methods in WicketComponent, so that they can be extended by subclasses.

* file 2: patch on seam-instrument-wicket maven mojo
Set the instrumentor class factory via class name (defaults to factory creating JavassistInstrumentor). When creating the instrumentor, this class is used.

> Extend wicket instrumentation functionality to support other types of dependency injection
> ------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4545
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4545
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Wicket
>    Affects Versions: 2.2.0.GA
>            Reporter: Kariem Hussein
>         Attachments: ioc-extensible-instrumentation-mojo.patch, ioc-extensible-instrumentation.patch
>
>
> The current instrumentation provides mechanisms to process @In annotations, but the same infrastructure could be used to handle injection of dependencies provided by frameworks (e.g. Spring, Guice). The motivation is outlined in http://seamframework.org/Community/ExtendWicketInstrumentationToHandleJSR330
> With the support for CDI in Seam 3 such integration efforts might not be necessary, but we are not there yet.

-- 
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