unix and linux operating commands

Basic Java Persistence API Best Practices


 
Thread Tools Search this Thread
# 1  
Old 09-11-2008
Basic Java Persistence API Best Practices

Consider and employ these simple approaches to make your Java Persistence API applications more maintainable.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Solaris

Java api/sample code for sftp

I'm trying to find an api for Java to send/receive files via sftp. There are some available for purchase out there such as JScape, but I was hoping to find a free one. Does anyone know of one? I would also like to find an open source java example application that can send files via sftp. ... (2 Replies)
Discussion started by: JohnRodey
2 Replies

2. Programming

Java UI does not come up using txtContent.setLineWrap(true) API

Hello , I have code which runs on solaris using java 1.2.2 .. UI will not come up when i use the command "txtContent.setLineWrap(true);".. UI gets displayed if do not use it... ______________________________________________________ txtContent = new JTextArea(20,30); ... (0 Replies)
Discussion started by: shafi2all
0 Replies
Login or Register to Ask a Question
ost::BaseObject(3)					     Library Functions Manual						ost::BaseObject(3)

NAME
ost::BaseObject - BaseObject. SYNOPSIS
#include <persist.h> Public Member Functions BaseObject () This constructor is used in serialisation processes. virtual ~BaseObject () Default destructor. virtual const char * getPersistenceID () const This returns the ID of the persistent object (Its type) virtual bool write (Engine &archive) const This method is used to write to the Persistence::Engine It is not equivalent to the << operator as it writes only the data and not the object type etc. virtual bool read (Engine &archive) This method is used to read from a Persistence::Engine It is not equivalent to the >> operator as it does no typesafety or anything. Detailed Description BaseObject. This object is the base for all Persistent data which is not natively serialised by the Persistence::Engine It registers itself with the Persistence::TypeManager using a global constructor function. A matching deregister call is made in a global destructor, to allow DLL's to use the Persistence::Engine in a main executable. Persistable objects must never maintain bad pointers. If a pointer doesn't point to something valid, it must be NULL. This is so the persistence engine knows whether to allocate memory for an object or whether the memory has been pre-allocated. Author: Daniel Silverstone Base class for classes that will be persistent. Constructor &; Destructor Documentation ost::BaseObject::BaseObject () This constructor is used in serialisation processes. It is called in CreateNewInstance in order to create an instance of the class to have Read() called on it. virtual ost::BaseObject::~BaseObject () [virtual] Default destructor. Member Function Documentation virtual const char* ost::BaseObject::getPersistenceID () const [virtual] This returns the ID of the persistent object (Its type) virtual bool ost::BaseObject::read (Engine &archive) [virtual] This method is used to read from a Persistence::Engine It is not equivalent to the >> operator as it does no typesafety or anything. virtual bool ost::BaseObject::write (Engine &archive) const [virtual] This method is used to write to the Persistence::Engine It is not equivalent to the << operator as it writes only the data and not the object type etc. Author Generated automatically by Doxygen for GNU CommonC++ from the source code. GNU CommonC++ Sat Jun 23 2012 ost::BaseObject(3)