Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Must not use ssubclass of Java Serialization Protocol.

 
Bartender
Posts: 1925
13
  • Mark post as helpful
  • send pies
  • 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.)
 
    Bookmark Topic Watch Topic
  • New Topic