[
https://issues.apache.org/jira/browse/WICKET-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov updated WICKET-4064:
------------------------------------
Fix Version/s: 1.6.0
Issue Type: New Feature (was: Bug)
This has been discussed many times. The problem is that if Wicket-Guice
supports it then Wicket-Spring should support it too. But Spring does scanning
and collisions may happen between Wicket Injector and Spring's one.
For Wicket.next we are planning to add integration with CDI and it will work
with javax.inject.Inject so we will reconsider the implementations.
Another problem to not be able to use it in 1.4/1.5 is that JEE6 classes are
compiled with JDK6 and Wicket is currently compiled with JDK5.
> Guice 3.0 integration does not support JSR-330 @javax.inject.Inject
> annotations
> -------------------------------------------------------------------------------
>
> Key: WICKET-4064
> URL: https://issues.apache.org/jira/browse/WICKET-4064
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-guice
> Affects Versions: 1.4.18, 1.5.0
> Reporter: Lasse Lindgård
> Priority: Minor
> Fix For: 1.6.0
>
>
> GuiceComponentInjector only checks for com.google.inject.Inject annotations,
> but Guice 3.0 also supports the JSR-330 javax.inject.Inject annotation.
> http://code.google.com/p/google-guice/wiki/JSR330
> It would be nice if the wicket integration also supported the standard
> annotations.
> http://svn.apache.org/viewvc/wicket/trunk/wicket-guice/src/main/java/org/apache/wicket/guice/GuiceComponentInjector.java?revision=1062356&view=markup
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
