Mailing-List: contact ojb-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Users List" <ojb-user@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <F9017844DF95F047B04B382336E68BEB016F1A10@ad04mexefd4.ad.admin.ch>
From: Claude.Glauser@bit.admin.ch
To: ojb-user@db.apache.org
Subject: AW: CMT and OJB
Date: Mon, 13 Jun 2005 07:30:26 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks a lot for your answer!

Yes, I will appreciate a feature to turn on or off "checkForTx" in
OJB.properties :)

With best regards, Claude

-----Urspr=FCngliche Nachricht-----
Von: Armin Waibel [mailto:arminw@apache.org]=20
Gesendet: Freitag, 10. Juni 2005 20:57
An: OJB Users List
Betreff: Re: CMT and OJB


Hi,

Claude.Glauser@bit.admin.ch wrote:
> Hi,
> =20
> I have an application server WebSphere 5.1 and I must do Container=20
> Managed Transactions (CMT) with OJB. There is only PB-API involved.=20
> Unfortunately, there is very little  documentation on this topic.

Maybe someone is willing to write a howto ;-)


> Now my question:
> =20
> If I don't call the method PersistenceBroker.beginTransaction() and
> PersistenceBroker.commitTransaction() everything seems to work.=20
> Rollbacks work. But there is a warning message similar to: "WARN: No=20
> tx found. Please use tx to avoid side effects...".  What are those=20
> sideeffects? Is there some cleanup OJB does while committing? I've=20
> seen some hashtable activity stuff in the OJB-sourcode. We don't use=20
> OJB-Cache.
>

This warning was introduced to prevent user in non-managed environments =

storing objects without a running tx. Without PB-tx the autocommit =
state=20
of the used connection is on (by default), thus when storing an object=20
with references or a bunch of objects a rollback of all objects is not=20
possible.


> Why has OJB to be "transaction aware" at all, since I don't use=20
> OJB-Cache.
> =20

In managed environments without using a cache it's completely different =

and the warning is needless and confusing.
Should introduce a property 'checkForTx' in OJB.properties to=20
en-/disable this behavior, instead always check for tx?

regards,
Armin


> Thx for your replies!
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org