Ulrich Mayring wrote:
Berin Loritsch wrote:
During initialize() the component stores information and it does
matter in which order you call the lifecycle methods :)
Yes but all that is done within the same thread (if the component has to
be initialized). By the time the *client* receives the component, it is
already fully initialized. THere is no opportunity for more than one
thread to call lifecycle methods on the same component at the same time.
The container can easily manage concurrency for that purpose.
Ok, so the client cannot call the lifecycle methods, even though they're
declared public?
Many containers will proxy the components anyway. That means that only
the components published interface is available to the client--and no
lifecycle methods.
No client *should ever* call lifecycle members. Ever. The client is
not responsible for the lifecycle of the component, the container is.
It is a violation of contracts for that to happen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
