Hi,
I have a strange problem that I can't explain. I don't know if this is a bug
or a limitation.
When I inject Spring dependency of a service inside a Wicket web page,
everything works fine but when I inject this dependency in a separate class
(in the following code example, the class
InjectorHolder.getInjector().inject(this); //do this in dataprovider
constructor
--
regards,
Vineet Semwal
On Wed, Sep 9, 2009 at 1:50 PM, Charles Moulliard cmoulli...@gmail.comwrote:
Hi,
I have a strange problem that I can't explain. I don't know if this is a
bug
or a limitation.
Hi Charles
@SpringBean only seems to work in some wicket base classes. In your own
separate classes, noone will actively inject your content.
What I do (maybe there's a better possibility) is to add this line to
that classes constructor to force injection:
Obligatory salve plug goes here :-)
It helps to understand what happens by stepping through some
construction logic of your components. If you follow that path you'll
venture along the registered IComponentInstantiationListener objects,
typically only your Spring component injector.
This doesn't
