Hi Klaasjan, there is no need to use the 'managed' implementation. OJB never pools datasource, thus you could use the default ConnectionFactroy (ConnectionFactoryPooledImpl). (Unless your servlet container supports JTS/JTA).
regards, Armin ----- Original Message ----- From: "Klaasjan Brand" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, February 03, 2003 4:06 PM Subject: transactions and managed connection pools question > Hi there, > > We're trying to use OJB in a scenario where the servlet container > provides a JNDI datasource (just that, and not a full-fledged > application server like JBoss, Websphere etc). > OJB was configured for JNDI and a "ConnectionFactoryManagedImpl", since > the server will do connection pooling. > > Our problem: OJB seems to expect transactions will be committed by an > application server and connections are wrapped in a "ByPassConnection", > which means to us that transactions will no longer be committed to the > database... > > Q: is it possible to use the managed connection factory _and_ have OJB > commit our data? > > -- > Klaasjan Brand <[EMAIL PROTECTED]> > Topicus B.V. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
