Hi!
Section 6.6 states that
A bean is called passivation capable if the container is able to
temporarily
transfer the state of any idle instance to secondary storage.
To me it is still not always clear if the term bean is now solely meant as terminus
technicus for Bean<T> or if it's still sometimes used for it's contextual
intances.
For the sentence above: does 'bean ... any idle instance' mean that it's in
question whether the Bean<T> is serializable or it's contextual instances shall
be?
As far as I've seen in the RI sources, the interface PassivationCapable has nothing to
do with your 'passivation capable' criteria used throughout 6.6 since RIBean
implements PassivationCapable indicates that all your internal beans are passivation
capable. Instead you have internal functions to handle that. But how do portable
extensions (like a custom context implementation) access this information?
txs 4 clarifying,
strub
__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen
Massenmails.
http://mail.yahoo.com