Re: How does the Java product handle commitment control -- JAVA400-L

Subject: Re: How does the Java product handle commitment control
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 21 May 2015 12:03:56 -0600
List-archive: <http://archive.midrange.com/java400-l/>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the IBM i <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

On Thu, May 21, 2015 at 11:17 AM, <jmoreno@xxxxxxxxxxxxxxxx> wrote:

Please let me know how does the Java product handles this commitment
control scenario

Short answer:

In Java, if you want to do things "by hand", you use the JDBC driver
directly.

If you want real transaction processing in Java, you use Java EE on top of
the JDBC driver.

https://docs.oracle.com/javaee/7/api/

Regards, Jack Woehr

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: How does the Java product handle commitment control , jmoreno

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.