• 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
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

SF session bean ejbPassivation nuance

 
Ranch Hand
Posts: 187
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Container guarantees saving of the following field types during passivation even though they are non-serializable fields as long as they are not transient.
1.Local / remote component and home interfaces (even if the objects / stubs are not serializable)
2.A SessionContext object
3.A bean�s special JNDI context or any of its subcontexts
4.The UserTransaction interface which can be got from the SessionContext
5. A resource manager connection factory like a instance of javax.sql.DataSource

QA) (Does 5 include all resource manager connection factories- [javax.sql.DataSource / javax.jms.QueueConnectionFactory /javax.jms.TopicConnectionFactory / javax.mail.Session / javax.net.URL].

QB) What of Administered objects (resource environment references) or JMS destinations). Are they excluded like java.sql Connection?
 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The answer is Yes for question A. I am not 100% sure on the JMS destinations NOT being passivated on question 2.
 
    Bookmark Topic Watch Topic
  • New Topic