Can someone elaborate on this construct?
It is poorly documented.
Lifecycle.NONE
Lifecycle.REQUEST
Lifecycle.RENDER
Lifecycle.PAGE
Was this designed because the designer decided to invent sub life cycles to
REQUEST?
Here is a typical usage...
@Bean(lifecycle = Lifecycle.REQUEST)
public abstract ValidationDelegate getDelegate();
Does this mean that I have cached my delegate for the life of the request?
Why wouldn't it be cached anyway if it were a parameter or property? I am
just thinking that this code is redundant and could have been or already is
modeled in another fashion somewhere else.
So when would I use these?
Lifecycle.NONE
Lifecycle.REQUEST
Lifecycle.RENDER
Lifecycle.PAGE
Do these promote some kind of life cycle work flow of some sort?
Are these just building blocks of some kind... do it yourself?
If someone could elaborate on this that would be terrific.
Best regards
Ken in nashua
_________________________________________________________________
Dont quit your job Take Classes Online and Earn your Degree in 1 year.
Start Today!
http://www.classesusa.com/clickcount.cfm?id=866146&goto=http%3A%2F%2Fwww.classesusa.com%2Ffeaturedschools%2Fonlinedegreesmp%2Fform-dyn1.html%3Fsplovr%3D866144
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
