Clement Escoffier wrote:
Exactly,
A temporal dependency will never be 'null' (except if the onTimeout policy
is 'null' of course). By default, an exception will be thrown (once the
timeout is reached).
Temporal dependencies will also never be null if you set the timeout to
be infinite, but if the service never comes back, then you won't make
much progress. :-)
-> richard
'Regular' (i.e. non temporal) optional dependency cannot be 'null' too. By
default a nullable object (or a default-implementation object) is injected
when the field accesses to an unavailable service.
Regards,
Clement
-----Original Message-----
From: Todor Boev [mailto:[EMAIL PROTECTED]
Sent: lundi 27 octobre 2008 16:40
To: [email protected]
Subject: Re: IPojo - ServiceUnavailableException?
Clement Escoffier wrote:
When a thread try to use a temporal dependency...
You mean a thread simply uses the reference stored in the respective
component field to make a call to the dependency object? I.e. I can
count on temporal dependencies to never be null. I.e. you do proxy the
temporal dependencies (not that it matters how exactly this is
implemented :)
Cheers,
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
