Depending on your deployment timeline and how good your unit tests are, you can also switch to the OTM and keep the PB API. You will need to build your own javadocs as it is specifically undocumented prior to 1.0, but it works very nicely.

-Brian

On Dec 9, 2003, at 11:59 AM, Kim Wegerle wrote:

Which API are you using? If ODMG (or OTM) than maintaining a single
transaction through multiple requests should work fine -- it is an
object transaction, not a database transaction, so the database
resource isn't being tied up the whole time.

Until now I'm using the PB API. But it's no problem to change it because I'm using the DAO pattern. I just wanted to discuss this before implementing unneeded stuff.
_______________________________________________________________________ _______
Horoskop, Comics, VIPs, Wetter, Sport und Lotto im WEB.DE Screensaver1.2
Kostenlos downloaden: http://screensaver.web.de/?mc=021110



--------------------------------------------------------------------- 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]



Reply via email to