|
-----Original Message-----
From: Kiran Kumar [mailto:kkumar@xxxxxxxxxxxxx]
Sent: Thursday, June 26, 2008 11:38 AM
To: Gary L Peskin
Cc: Java Programming on and around the iSeries / AS400
Subject: RE: Commitment control
We are planning to use Web Sphere as application server for Java
technology and currently we are confused as how to deal with
transactionality. A series of transactions are spread across multiple
slave COBOL programs exposed as web services. We would like call set of
COBOL web services and commit if all of them are successful.
Right now, we do not have any idea as how to proceed to handle this
problem.
-----Original Message-----
From: Gary L Peskin [mailto:garyp@xxxxxxxxxxxx]
Sent: Thursday, June 26, 2008 2:24 PM
To: Kiran Kumar
Cc: 'Java Programming on and around the iSeries / AS400'
Subject: RE: Commitment control
Kiran --
You need to be careful about the job that you're talking about. If you
expose things as web services, what container are you using? That will
determine how to deal with transactionality. I was talking about a
straight
java application.
Gary
-----Original Message-----If
From: Kiran Kumar [mailto:kkumar@xxxxxxxxxxxxx]
Sent: Thursday, June 26, 2008 7:39 AM
To: Gary L Peskin
Cc: Java Programming on and around the iSeries / AS400
Subject: RE: Commitment control
Thanks, we can use this internally for building internal application.
We are also planning to expose slave COBOL programs as web services.
so, how the requestor using our slave web services should manage thehe
commitment control.
The requestor may be calling suite of various web services. How can
achieve the commitment boundary across web services?
Thanks
Kiran
=======================================================================
===============
Notice: This message is intended only for use by the person or entity
to which it is addressed. Because it may contain confidential
information intended solely for the addressee, you are notified that
any disclosing, copying, downloading, distributing, or retaining of
this message, and any attached files, is prohibited and may be a
violation of state or federal law. If you received this message in
error, please notify the sender by reply mail, and delete the message
and all attached files.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.