• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Must not use ssubclass of Java Serialization Protocol.

 
Bartender
Posts: 2419
13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.)
 
I'm doing laundry! Look how clean this tiny ad is:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic