[castor-dev] castor jdo in compnent framework [pooling]

[Jakob Praher]

hi all,

I've developed a system based on avalon, and have one component for
database persistence like:

class CastorJDOComponent implements Disposable, ..{
        public Database getDatabase( ) { ... }

        public void dispose( ) { 
                
        }
}

my clients look something like this:

CastorJDOComponent jdo = (CastorJDOCompnent )myManager.lookup(
"CastorJDOComponent" );

/* use the jdo here */

myManager.release( jdo );


now I am successfully using the above system, but want to make the best
use out of the CastorJDOCompnent

If I am right castor internally opens the JDBC connection at 
        db.begin( ) 
time and closes it at 
        db.commit( ) 


should there be an org.exolab.castor.jdo.Database [Database] per VM, as
Connections are internally opened for each transactions or should I
implement some kind of pooling.

does anybody have experiences of running Castor in a Component Framework
( EJB, ... ).

thanks

-- Jakob

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev