[jta-dev] readOnly transactions feature on JTS/OTS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jta-dev] readOnly transactions feature on JTS/OTS

From: Aiden Zhang <aidentzhang@xxxxxxxxx>
Date: Fri, 26 Jun 2026 16:30:17 -0400
Arc-authentication-results: i=1; mx.google.com; arc=none
Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=to:subject:message-id:date:from:mime-version:dkim-signature; bh=3/0BSs3zjLqvNbvmYXIQTQyNhdXPrvH8jsU6TkSRDCs=; fh=qF5OXj0x2obbY4aheNI9MyUlAxPU5Li9XSgBD+XW/GI=; b=YMoiXv/nu7yBNn0NyWIxAh4D3l4PyG/D4ZXnudVD5EKJ8b/++4Je86STZAvHf2HdZ6 3022cHSqv2MbrmtF1o0BGq0xUkqQpBCkkCGW+WO60so8ccubu1MHPs0fzBEDMA+01qt7 NY6IEtffHNoR4W7BP8skaRq5G/bPyj1dsGj4XoXKPqGUh4NAiiiSHjcAme/AeKfukEvO E5CyiyhqXDWdYJespSGraZvLpoJDAhlwf2uRLTq/RydOD+Z39f9FBjSm/mhEzANg9blr VUqLHevOnoz2PfjvPJSG//kkiCRpjinO+uXTij/i8mDePJw0xuHIefdoxjn9fnw+neJA Vb0g==; darn=eclipse.org
Arc-seal: i=1; a=rsa-sha256; t=1782505830; cv=none; d=google.com; s=arc-20260327; b=SbpDsX8AjIheBC85CyhKxqknkrithm/fXvjrHJPLSsMBKrcXRA1VE3Cq3G8WTAGchX M6yCgTQeZndg7SGRmZJlL4JOIRxG9sllE4rONdf2qXSBvj9MdD0a/KYtMjvI6+gZBQTQ F95kHxNse5wOr0fhLYjCb6Lh1bUzPJYykreLyS37ktCofhvSQ+q324/SIio/E3sNyRDu cN8VetHj30xBB0LyzVhbwjlWlmyO03yrHQ/OrPIinLJNH1oL+zJ4XsZF8Rp1bE82emcx ysKM1W/FO4/U5hNnbIY6X0andvvtCZpDVfpfQ6ZCzz16iagLD8spLB51QzzT2BaWuCBX K2Vg==
Delivered-to: jta-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jta-dev/>
List-help: <mailto:jta-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jta-dev>, <mailto:jta-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jta-dev>, <mailto:jta-dev-request@eclipse.org?subject=unsubscribe>

Hello all,

Since OTS does not support the readOnly flag, and JTS relies on a CORBA mapping between OTS and JTA, propagating the readOnly flag isn't possible. To address this issue, the spec should define that read-only behavior is undefined for remotely propagated transactions.

I submitted this PR: https://github.com/jakartaee/transactions/pull/253, which addresses https://github.com/jakartaee/transactions/issues/252.

Please let me know if you have any thoughts or feedback on this adjustment!

Aiden Zhang

Prev by Date: [jta-dev] Looking for a volunteer to help with developing a TCK test for a proposed wording change in the specification
Previous by thread: [jta-dev] Looking for a volunteer to help with developing a TCK test for a proposed wording change in the specification
Index(es):
- Date
- Thread

Breadcrumbs