[
https://issues.apache.org/jira/browse/WICKET-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007808#comment-13007808
]
Bruno Borges edited comment on WICKET-3542 at 3/17/11 4:47 AM:
---------------------------------------------------------------
Yes, we recently had a discussion about this:
http://apache-wicket.1842946.n4.nabble.com/Spring-Annotations-supoprt-for-IoC-on-WebPages-td3320087.html
And I agree with *not* allowing that.
Although, I would consider renaming @SpringBean to something else that could
easily fit with CDI / Spring / Guice
@WicketInject perhaps.
And the IoC could be switched at WicketApplication class without complication
(I think). It is not usual, and probably not recommended to have more than one
IoC anyway.
was (Author: bruno.borges):
Yes, we recently had a discussion about this:
http://apache-wicket.1842946.n4.nabble.com/Spring-Annotations-supoprt-for-IoC-on-WebPages-td3320087.html
> 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
