You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Todor Boev <t....@prosyst.bg> on 2008/11/02 18:04:26 UTC
iPojo - instance becomes immediate?
Hello,
As I was playing with the Hello example the following warning kept popping up until I declared the
as immediate.
[HelloClient] WARNING: The component HelloClient becomes immediate
HelloClient is the component running a thread that calls Hello.sayHello(). Curiously when I declared
immediate=false everything kept working but with no warning. And when I set
immediate=true....everything kept working but with no warning. What does this all mean? :)
Regards,
Todor
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: iPojo - instance becomes immediate?
Posted by clement escoffier <cl...@gmail.com>.
2008/11/2 Karl Pauls <ka...@gmail.com>
> On Sun, Nov 2, 2008 at 7:05 PM, Clement Escoffier
> <cl...@gmail.com> wrote:
> > Hi,
> >
> > This message just informs
>
> Maybe it should be an INFO then rather then a WARNING :-)
I agree, I changed it in the trunk.
Regards,
Clement
>
> > that the instance was detected and set as
> > 'immediate'. An immediate instance creates a POJO object as soon as the
> > instance becomes valid, i.e. call the POJO's constructor.
> >
> > iPOJO set an instance to immediate, when the immediate attribute is not
> set,
> > and if the instance does not provide services.
> >
> > It does not change anything if your component type has a validate
> lifecycle
> > callback. In fact, to call the validate callback, the POJO's constructor
> is
> > called if no objects were already created, and the callback is invoked on
> > the created object.
> >
> > Regards,
> >
> > Clement
> >
> > -----Original Message-----
> > From: Todor Boev [mailto:t.boev@prosyst.bg]
> > Sent: dimanche 2 novembre 2008 18:04
> > To: users@felix.apache.org
> > Subject: iPojo - instance becomes immediate?
> >
> > Hello,
> > As I was playing with the Hello example the following warning kept
> popping
> > up until I declared the
> > as immediate.
> >
> > [HelloClient] WARNING: The component HelloClient becomes immediate
> >
> > HelloClient is the component running a thread that calls
> Hello.sayHello().
> > Curiously when I declared
> > immediate=false everything kept working but with no warning. And when I
> set
> > immediate=true....everything kept working but with no warning. What does
> > this all mean? :)
> >
> > Regards,
> > Todor
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
>
>
> --
> Karl Pauls
> karlpauls@gmail.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
Re: iPojo - instance becomes immediate?
Posted by Karl Pauls <ka...@gmail.com>.
On Sun, Nov 2, 2008 at 7:05 PM, Clement Escoffier
<cl...@gmail.com> wrote:
> Hi,
>
> This message just informs
Maybe it should be an INFO then rather then a WARNING :-)
regards,
Karl
> that the instance was detected and set as
> 'immediate'. An immediate instance creates a POJO object as soon as the
> instance becomes valid, i.e. call the POJO's constructor.
>
> iPOJO set an instance to immediate, when the immediate attribute is not set,
> and if the instance does not provide services.
>
> It does not change anything if your component type has a validate lifecycle
> callback. In fact, to call the validate callback, the POJO's constructor is
> called if no objects were already created, and the callback is invoked on
> the created object.
>
> Regards,
>
> Clement
>
> -----Original Message-----
> From: Todor Boev [mailto:t.boev@prosyst.bg]
> Sent: dimanche 2 novembre 2008 18:04
> To: users@felix.apache.org
> Subject: iPojo - instance becomes immediate?
>
> Hello,
> As I was playing with the Hello example the following warning kept popping
> up until I declared the
> as immediate.
>
> [HelloClient] WARNING: The component HelloClient becomes immediate
>
> HelloClient is the component running a thread that calls Hello.sayHello().
> Curiously when I declared
> immediate=false everything kept working but with no warning. And when I set
> immediate=true....everything kept working but with no warning. What does
> this all mean? :)
>
> Regards,
> Todor
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
--
Karl Pauls
karlpauls@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
RE: iPojo - instance becomes immediate?
Posted by Clement Escoffier <cl...@gmail.com>.
Hi,
This message just informs that the instance was detected and set as
'immediate'. An immediate instance creates a POJO object as soon as the
instance becomes valid, i.e. call the POJO's constructor.
iPOJO set an instance to immediate, when the immediate attribute is not set,
and if the instance does not provide services.
It does not change anything if your component type has a validate lifecycle
callback. In fact, to call the validate callback, the POJO's constructor is
called if no objects were already created, and the callback is invoked on
the created object.
Regards,
Clement
-----Original Message-----
From: Todor Boev [mailto:t.boev@prosyst.bg]
Sent: dimanche 2 novembre 2008 18:04
To: users@felix.apache.org
Subject: iPojo - instance becomes immediate?
Hello,
As I was playing with the Hello example the following warning kept popping
up until I declared the
as immediate.
[HelloClient] WARNING: The component HelloClient becomes immediate
HelloClient is the component running a thread that calls Hello.sayHello().
Curiously when I declared
immediate=false everything kept working but with no warning. And when I set
immediate=true....everything kept working but with no warning. What does
this all mean? :)
Regards,
Todor
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org