Joseph Pachod schrieb:
We're using Wicket with Guice.
An issue has just popped up : on some special injected objects, we
access public fields. These public fields are themselves injected
through guice.
However, due to the LazyInitProxyFactory, they're not. Indeed, as far as
I got it, the LazyInitProxyFactory waits for the first method call to do
the actual injection.
To me this does not feel like necessarily the right behaviour. I do not
see a tremendous advantage in this resolving being done lazily.
My suggestion would be to add a switch in some Settings object, that
controls this behaviour and inject as requested without deferrence.
As i don´t like the idea to live with a longterm patch of wickets, would
it be acceptable to include this kind of tweak into the wicket-guice
codebase if i provided an appropriate patch?
And if so, what would be the right place for such a switch?
cu uwe
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
