[
https://issues.apache.org/jira/browse/WICKET-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-5482.
-------------------------------------
Resolution: Fixed
Fix Version/s: 7.0.0
6.14.0
OK. That gave me idea what is needed to do the binding.
I think there must be a simpler way but I cannot find any example in the web.
See org.apache.wicket.guice.GuiceInjectorTest#testInjectionAndSerialization and
org.apache.wicket.guice.JavaxInjectTestComponent#named1 for example how to do
it.
> Wicket-guice doesn't support @javax.inject.Named annotations
> ------------------------------------------------------------
>
> Key: WICKET-5482
> URL: https://issues.apache.org/jira/browse/WICKET-5482
> Project: Wicket
> Issue Type: Bug
> Components: wicket-guice
> Affects Versions: 6.13.0
> Reporter: Ilia Naryzhny
> Assignee: Martin Grigorov
> Labels: injection
> Fix For: 6.14.0, 7.0.0
>
> Attachments: WICKET-5482.patch
>
>
> Following annotations in wicket commponent have not been supported now:
> @Inject
> @Named("myproperty")
> private String myproperty;
> And instead of throwing exception, wicket-guice just substitute "" for String
> fields. And that is making debuging of problems quite difficult task.
> The problem, from my point of view, lies in
> org.apache.wicket.guice.GuiceFieldValueFactory.findBindingAnnotation(); or
> can be fixed one level up
> (org.apache.wicket.guice.GuiceFieldValueFactory.getFieldValue())
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
