• Post Reply Bookmark Topic Watch Topic
  • New Topic

Is there no way for AS to detect EJB has changed ?

 
Mike Skorik
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello, All,
I've implemented a sample enterprise application with a set of
O/R mapping EJBs inside. All is pretty straightforward but there
is a thing I'm puzzled about:
Why EJBs are storing their own state (at the end of its life cycle)
either if I've not changed them ?
No transactions were defined in deployment descriptor.
How to turn off this behavior ?
Or is it impossible indeed for AS to detect EJB has changed ?

P.S.
I'm using Oracle9iAS (former Orion).
 
Thomas Paul
mister krabs
Ranch Hand
Posts: 13974
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mikhail Skorik:
Why EJBs are storing their own state (at the end of its life cycle)
either if I've not changed them ?
And what makes you think that they are?
 
Tim Holloway
Bartender
Posts: 18408
58
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Simpleminded appservers do. They take the conservative approach. A lot of real-world appservers pay closer attention and only write out changed beans to reduce overhead, but in some cases they require a little help (like an isModified() method in the EJB)
 
Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!