[
https://issues.apache.org/jira/browse/WICKET-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007727#comment-13007727
]
Igor Vaynberg commented on WICKET-3542:
---------------------------------------
this may be a dangerous thing, using a custom annotation has its advantages.
for example, if we use the standard @Inject and the spring project is using
aspect then wicket components will be instrumented by aspectj instead of
wicket. obviously, this is undesirable. users will have to add exclusions into
their package-scanning config, etc.
> Support for JSR 330 annotations (@Inject, @Named)
> -------------------------------------------------
>
> Key: WICKET-3542
> URL: https://issues.apache.org/jira/browse/WICKET-3542
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-spring
> Reporter: Steve Jones
> Attachments: WICKET-3542.patch
>
>
> Currently wicket supports injection of dependencies using the SpringBean
> annotation. It would be nice to have an option to use JSR 330 annotations
> instead.
> Not much would need to change for this, just some changes in
> AnnotProxyFieldValueFactory.
> The SpringBean annotation would map directly to Inject and the "name" value
> could map to the Named annotation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
