Any updates on this issue? Will there be a fix?
Check this out:
https://issues.apache.org/jira/browse/WICKET-2737
1.4.7 will have that fix, in the meantime you can patch your wicket-spring
by yourself.
--
View this message in context:
Thanks for the fix, zbigniew. However, IMO it isn't complete:
https://issues.apache.org/jira/browse/WICKET-2737?focusedCommentId=12834859page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12834859
what do you think?
On Wed, Feb 17, 2010 at 1:20 AM, zbigniew
Any updates on this issue? Will there be a fix?
Igor Vaynberg igor.vaynb...@gmail.com
02/10/2010 06:15 PM
Please respond to
users@wicket.apache.org
To
users@wicket.apache.org
cc
Subject
Re: @SpringBean injection expensive - a bug?
create a jira issue and a quickstart. thanks.
-igor
FWIW, explicitly specifying a name with @SpringBean worked around the
problem
On Tue, Feb 9, 2010 at 11:34 AM, Nikita Tovstoles
nikita.tovsto...@gmail.com wrote:
Wicket's SpringWebApplication is deprecated and the javadoc advocates
using @SpringBean to inject dependencies at component level.
create a jira issue and a quickstart. thanks.
-igor
On Tue, Feb 9, 2010 at 11:34 AM, Nikita Tovstoles
nikita.tovsto...@gmail.com wrote:
Wicket's SpringWebApplication is deprecated and the javadoc advocates
using @SpringBean to inject dependencies at component level. However,
that appears to
Wicket's SpringWebApplication is deprecated and the javadoc advocates
using @SpringBean to inject dependencies at component level. However,
that appears to be an expensive proposition:
I have a listView component that renders a (new) ExternalLink subclass
per item. That subclass uses a service (a
