Yeah. It's mystic. I couldn't find any commit to trunk / release with
this change.
In Jira issue is really open. But i really used an unpatched 1.5.0 version
with SpringBean proxy available. Maybe it was accidently in 1.5.0 :-)
I've use as a workaround wicket-spring 1.5.0 with wicket-core excluded.
It seems to work so far.
Mike
Since you ask... https://issues.apache.org/jira/browse/WICKET-3936 has
never been applied, neither RC, nor 1.5.0, nor 1.5.1
It is still open.
I think we should keep all our -ioc implementations in sync. So if
this feature is applied for Spring then it should be applied for Guice
as well. But I guess this should be discussed further.
On Fri, Sep 30, 2011 at 8:58 AM, Mike Mander<wicket-m...@gmx.de> wrote:
Hi,
call me stupid but with 1.5.0 there was a feature in SpringBean annotation
to set using a proxy or not.
Issue was https://issues.apache.org/jira/browse/WICKET-3936.
Why is it gone with 1.5.1?
Thanks
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org