On Sun, Nov 2, 2008 at 7:05 PM, Clement Escoffier <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED] > Sent: dimanche 2 novembre 2008 18:04 > To: [email protected] > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Karl Pauls [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
