Author Topic: Why should not container-managed field be declared transient  (Read 74 times)

0 Members and 1 Guest are viewing this topic.

Offline Corps

  • Sr. Member
  • *
  • Posts: 276
  • Karma: +0/-0
    • View Profile
Why should not container-managed field be declared transient
« on: January 06, 2009, 07:51:18 AM »
Why should not a container-managed field be declared transient?


The modifier “transient” is used only when the data member value is not to be stored in a file, or persistent storage.  Since the values of the container-managed fields need to be written on to persistent storage, these fields cannot be declared transient.

Techronnati | where technology never sleeps

Why should not container-managed field be declared transient
« on: January 06, 2009, 07:51:18 AM »

Mountain View

 

Related Topics

  Subject / Started by Replies Last post
0 Replies
96 Views
Last post November 28, 2008, 07:32:33 AM
by Berto
0 Replies
111 Views
Last post April 25, 2010, 08:27:40 PM
by MrSpecialist
3 Replies
1665 Views
Last post February 17, 2015, 08:37:22 AM
by GBTalk
0 Replies
597 Views
Last post July 21, 2015, 01:55:14 AM
by JusticeLeague
1 Replies
199 Views
Last post September 09, 2016, 12:58:24 AM
by GBTalk

Posting Disclaimer: Any individual may post a message in this forum and may do so anonymously. Therefore, the sole author is exclusively and entirely responsible for all opinions in that message. They do not represent the official opinions of Techronnati, its administrators or moderators or the Techronnati Management. Techronnati is merely acting as an impartial conduit for constitutionally protected free speech and is not responsible and will not be held liable for the content of such messages. All images and service logos are trademarks of their respective owners.