that is there to give users a chance at test time to override
injection partially, as in
component c=new mycomponent();
c.service1=mock(service.class);
injector.inject(c);
injector will inject everything but service1. key here is to make sure
service doesnt have to be defined in the test's spring context.
-igor
On Tue, Feb 14, 2012 at 8:08 AM, martin.dilger
<martin.dil...@googlemail.com> wrote:
> Hi,
>
> thanks, this is true, but I dont think this is the Point I refer to, since I
> call Injector.get().inject(this) in our Test, so I explicitely request
> SpringBean-injection.
> The Problem is this Line in Class Injector:
>
> if (field.get(object) == null)
> {
>
> Object value =
> factory.getFieldValue(field, object);
>
> if (value != null)
> {
> field.set(object, value);
> }
> }
>
> Injection only happens, if the Field is non-null.
> I can not think of any use-case why this is?
>
> Any comments?
>
> Thanks in advance!
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/SpringComponentInjector-and-non-null-fields-tp4386918p4387511.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> 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
