Win a copy of TDD for a Shopping Website LiveProject this week in the Testing forum!
  • 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 ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
  • Piet Souris
  • Himai Minh

Must not use ssubclass of Java Serialization Protocol.

Posts: 2162
  • 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.)
Hold that thought. Tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss
    Bookmark Topic Watch Topic
  • New Topic