Forums Register Login

Must not use ssubclass of Java Serialization Protocol.

+Pie Number of slices to send: Send
On p. 600 of the spec,

The enterprise bean must not attempt to use the subclass and object substitution features of the Java Serialization Protocol.



But on p. 73,

While the container is not required to use the Serialization protocol for Java Programming language to store the state of a passivated session instance.....



The first quote says the bean cannot use object substitution of Java Serialization Protocol.
The second quote says the container is not required to use the Java Serialization Protocol for @PrePassivate and @PostActivate.

Are these two conflicting each other ?

(source: EPractice Lab asks about EJB restrictions.)
moose poop looks like football shaped elk poop. About the size of this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 577 times.
Similar Threads
Programming restrictions of Bean Provider
Passing a Session Bean's Object Reference
Two questions on the EJB programming restrictions.
Transient field
Questions regarding EJB Overview
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 29, 2024 04:42:14.