You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kandula-dev@ws.apache.org by An...@cognizant.com on 2008/06/20 14:20:29 UTC
Issues while compiling src code
Hi,
I am new to Apache Kandula, I was thinking of evaluating Kandula in
order to know how exactly a transaction management would work in a
distributed web service system.
I downloaded the source code from
http://svn.apache.org/repos/asf/webservices/kandula/branches/Kandula_1/s
rc/java/org/apache/kandula/ and added the dependant jars as mentioned @
http://ws.apache.org/kandula/1/dependencies.html , but when I tried to
build there are many source codes which is not there in the Kandula src
repository.
e.g. org.apache.kandula.wscoor.CreateCoordinationContextType
rg.apache.kandula.wscoor.ActivationPortTypeRPCBindingStub
org.apache.kandula.wscoor.CoordinationContextType
I tried to check whether while downloading my svn client did not
download the specific classes, but I did check the src repository the
package itself is not there.
Please let me know what could be the issue in this.
Thanking you in advance.
Regards,
Anshuk Pal Chaudhuri
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
Re: Issues while compiling src code
Posted by Hannes Erven <he...@apache.org>.
Hi Anshuk,
> I did have a good look at the specifications as you mentioned. I also
> read the following:
> http://www.ibm.com/developerworks/library/ws-wstx1/
> http://www-128.ibm.com/developerworks/library/ws-wstx2/
>
> which actually gives a good understanding about the how the activation,
> registration and coordination service are invoked. But this was specific
> to IBM related product.
> I was trying to align the same flow with Kandula as per the coordination
> services are concerned.
The documents you cite are actually not product-specific but describe
the general flow within a WS-AT or WS-BA transaction.
Kandula (as well as e.g. Websphere) is fully compatible[*] with WS-Coord
and WS-AT, so you can actually create a transaction with participants
and coordinators running on different plattforms.
Best regards,
-hannes
*: By "fully compatible" I mean that both products are built upon the
same protocol standards and should, by design, work perfectly together.
Since the last interoperability test was done a log time ago, I cannot
assess how Kandula and other transaction products will interoperate in
today's reality.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Hi Hannes,
As discussed earlier, I was able to run the testsuite1 sample using
Kandula.
I did have a good look at the specifications as you mentioned. I also
read the following:
http://www.ibm.com/developerworks/library/ws-wstx1/
http://www-128.ibm.com/developerworks/library/ws-wstx2/
which actually gives a good understanding about the how the activation,
registration and coordination service are invoked. But this was specific
to IBM related product.
I was trying to align the same flow with Kandula as per the coordination
services are concerned.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Hannes Erven [mailto:herven@apache.org]
Sent: Sunday, June 29, 2008 4:37 AM
To: kandula-dev@ws.apache.org
Cc: Pal Chaudhuri, Anshuk (Cognizant)
Subject: Re: Issues while compiling src code
Hi Anshuk,
> What I am not clear is the flow how exactly the client creates the
> co-ordination context and so on.
I'm not sure what you are exactly looking for and what you already know
or have read.
As a general starting point, I suggest you have a look at the
WS-Coordination specification and also WS-AtomicTransaction or
WS-BusinessActivity, whatever transaction type you are interested in.
In the source code, at the Kandula server it all starts at
org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
text
, this is where the call from the client is received. From there, the
actual transaction coordinator object is created depending on the
requested type of transaction.
If you have further questions or need reading tips, please reply with
more details what you are interested in.
Best regards and thank you for your interest in Kandula,
-hannes
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Hi Hannes,
I was thinking the testsuite sample could be reused in the below
mentioned scenario which I am trying to achieve.
I was reading http://ws.apache.org/kandula/1/ws-at--how_to_use.html
" This sample application demostrates how to use Kandula to initiate and
terminate transactions using the WS-AtomicTransaction protocol. It also
demostrates the behaviour of Kandula under a number of failure
scenarios. Note that we use pseudo XAResouces instead of actual
applications such as Databases, Messaging etc. to simplify the testing
process. Hence the application explicitly enlists all XAResources used
in operations. This would not be the case with real applications
however. The container would normally takecare of this for you,
transparently."
So in this case, the container would the was app server and that would
take care of the transactions. I have generated the stubs using axis
wsdl2java form the web service wsdl.
But what I am not sure is how to use the Kandula in this specific case.
Please let me know.
Thanking you in advance.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Pal Chaudhuri, Anshuk (Cognizant)
Sent: Wednesday, July 09, 2008 1:04 PM
To: 'Hannes Erven'; kandula-dev@ws.apache.org
Subject: RE: Issues while compiling src code
Hi Hannes,
Thanks for your input.
I did try out using the atomic transaction that comes with the IBM WAS
6.0. The web service would insert some values in a database. The web
service client was built using the stubs generated by the IBM SOAP
Engine WSDL2Java and configured in such a way so that it would send
atomic transaction details in the soap envelope. So, I tested a good
scenario and the values got inserted in the table. While testing the
error scenario, in the web service after the part of the which does the
insertion, I threw a runtime exception explicitly and when I checked the
tables, the values were not inserted.
Now I intend to do a similar scenario using Apache Kandula at the client
side. The same web service (deployed on WAS) would be used, but the
client would now send the soap request using apache Kandula and the
necessary transaction details (within the soap header) would be sent.
I did have a look at the documentation, but I am not exactly sure what
needs to be done.
Can you help/guide me in testing the above.
Thanking you in advance.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Hannes Erven [mailto:herven@apache.org]
Sent: Sunday, June 29, 2008 4:37 AM
To: kandula-dev@ws.apache.org
Cc: Pal Chaudhuri, Anshuk (Cognizant)
Subject: Re: Issues while compiling src code
Hi Anshuk,
> What I am not clear is the flow how exactly the client creates the
> co-ordination context and so on.
I'm not sure what you are exactly looking for and what you already know
or have read.
As a general starting point, I suggest you have a look at the
WS-Coordination specification and also WS-AtomicTransaction or
WS-BusinessActivity, whatever transaction type you are interested in.
In the source code, at the Kandula server it all starts at
org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
text
, this is where the call from the client is received. From there, the
actual transaction coordinator object is created depending on the
requested type of transaction.
If you have further questions or need reading tips, please reply with
more details what you are interested in.
Best regards and thank you for your interest in Kandula,
-hannes
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Hi Hannes,
Thanks for your input.
I did try out using the atomic transaction that comes with the IBM WAS
6.0. The web service would insert some values in a database. The web
service client was built using the stubs generated by the IBM SOAP
Engine WSDL2Java and configured in such a way so that it would send
atomic transaction details in the soap envelope. So, I tested a good
scenario and the values got inserted in the table. While testing the
error scenario, in the web service after the part of the which does the
insertion, I threw a runtime exception explicitly and when I checked the
tables, the values were not inserted.
Now I intend to do a similar scenario using Apache Kandula at the client
side. The same web service (deployed on WAS) would be used, but the
client would now send the soap request using apache Kandula and the
necessary transaction details (within the soap header) would be sent.
I did have a look at the documentation, but I am not exactly sure what
needs to be done.
Can you help/guide me in testing the above.
Thanking you in advance.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Hannes Erven [mailto:herven@apache.org]
Sent: Sunday, June 29, 2008 4:37 AM
To: kandula-dev@ws.apache.org
Cc: Pal Chaudhuri, Anshuk (Cognizant)
Subject: Re: Issues while compiling src code
Hi Anshuk,
> What I am not clear is the flow how exactly the client creates the
> co-ordination context and so on.
I'm not sure what you are exactly looking for and what you already know
or have read.
As a general starting point, I suggest you have a look at the
WS-Coordination specification and also WS-AtomicTransaction or
WS-BusinessActivity, whatever transaction type you are interested in.
In the source code, at the Kandula server it all starts at
org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
text
, this is where the call from the client is received. From there, the
actual transaction coordinator object is created depending on the
requested type of transaction.
If you have further questions or need reading tips, please reply with
more details what you are interested in.
Best regards and thank you for your interest in Kandula,
-hannes
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: Issues while compiling src code
Posted by Hannes Erven <he...@apache.org>.
Hi Anshuk,
> What I am not clear is the flow how exactly the client creates the
> co-ordination context and so on.
I'm not sure what you are exactly looking for and what you already know
or have read.
As a general starting point, I suggest you have a look at the
WS-Coordination specification and also WS-AtomicTransaction or
WS-BusinessActivity, whatever transaction type you are interested in.
In the source code, at the Kandula server it all starts at
org.apache.kandula.coordinator.CoordinationService#createCoordinationContext
, this is where the call from the client is received. From there, the
actual transaction coordinator object is created depending on the
requested type of transaction.
If you have further questions or need reading tips, please reply with
more details what you are interested in.
Best regards and thank you for your interest in Kandula,
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Thanks Hannes for the input. I did try out that and tested the
testsuite1 client I could see the request and responses in the tcpmon.
What I am not clear is the flow how exactly the client creates the
co-ordination context and so on. It would be great that if some document
is provided which would give the how the flow of the code and how it is
working.
Thanking you in advance.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Hannes Erven [mailto:hannes@erven.at]
Sent: Friday, June 20, 2008 6:13 PM
To: kandula-dev@ws.apache.org
Cc: Pal Chaudhuri, Anshuk (Cognizant)
Subject: Re: Issues while compiling src code
Hi Anshuk,
> I downloaded the source code from
>
http://svn.apache.org/repos/asf/webservices/kandula/branches/Kandula_1/s
rc/java/org/apache/kandula/
You need to download more than just the org.apache.kandula java source
code package. Please use svn to checkout from this folder:
http://svn.apache.org/repos/asf/webservices/kandula/branches/Kandula_1
You can then use maven 1.x to build kandula (just run "maven" where you
checked out), and it should automatically download the dependencies for
you.
The "missing" classes you mentioned,
> e.g. org.apache.kandula.wscoor.CreateCoordinationContextType
> org.apache.kandula.wscoor.ActivationPortTypeRPCBindingStub
> org.apache.kandula.wscoor.CoordinationContextType
are created from WSDL files (in Kandula_1/src/schema/ ) in the maven run
and reside in the Kandula_1/target/ directory.
If you'd like to look at Kandula_1 with Eclipse or similar, you also
need to run maven once and add the stuff maven puts into the target
folder to the project (.jar files as library, the src folder als
additional source folder).
The WS-AT Readme (http://ws.apache.org/kandula/1/ws-at--how_to_use.html)
contains more detailed information on how to build Kandula_1 .
Best regards and happy testing,
-hannes
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: Issues while compiling src code
Posted by Hannes Erven <ha...@erven.at>.
Hi Anshuk,
> I downloaded the source code from
> http://svn.apache.org/repos/asf/webservices/kandula/branches/Kandula_1/src/java/org/apache/kandula/
You need to download more than just the org.apache.kandula java source
code package. Please use svn to checkout from this folder:
http://svn.apache.org/repos/asf/webservices/kandula/branches/Kandula_1
You can then use maven 1.x to build kandula (just run "maven" where you
checked out), and it should automatically download the dependencies for you.
The "missing" classes you mentioned,
> e.g. org.apache.kandula.wscoor.CreateCoordinationContextType
> org.apache.kandula.wscoor.ActivationPortTypeRPCBindingStub
> org.apache.kandula.wscoor.CoordinationContextType
are created from WSDL files (in Kandula_1/src/schema/ ) in the maven run
and reside in the Kandula_1/target/ directory.
If you'd like to look at Kandula_1 with Eclipse or similar, you also
need to run maven once and add the stuff maven puts into the target
folder to the project (.jar files as library, the src folder als
additional source folder).
The WS-AT Readme (http://ws.apache.org/kandula/1/ws-at--how_to_use.html)
contains more detailed information on how to build Kandula_1 .
Best regards and happy testing,
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Hi,
As you suggested, I tried the following
public void invoke()
{
TransactionManagerImpl tm = TransactionManagerImpl.getInstance();
try {
tm.begin();
DBUpdateService db = new DBUpdateServiceLocator(); // using the stubs generated from the web service
DBUpdate invoke = db.getDBUpdate(); // using the stubs generated from the web service
invoke.insertTestOne(1,"anshuk"); // using the stubs generated from the web service
tm.commit();
}
catch (Exception e) {
e.printStackTrace();
}
}
But this is not revoking the inserted records from the database; When I checked the soap request in the tcpmon, the coordination context is not in the soap header of the request. Do I need to add any configuration or anything else?
Thanks.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
Sent: Tuesday, July 15, 2008 7:44 PM
To: kandula-dev@ws.apache.org
Cc: Pal Chaudhuri, Anshuk (Cognizant)
Subject: RE: Issues while compiling src code
Quoting Anshuk.PalChaudhuri@cognizant.com:
I don't understand why you have your own client level handler to
create a coordination context and then add it to out going messages!
Kandula already provides that mechanism and much more.
Just deploy Kandula in Axis according to the user guide and then
using a standalone client + the toy TM, invoke your WAS service inside a
transaction: toyTm.begin(); foo.invokeWASService(); toyTm.commit();
Since you are using a standalone client and Kandula only supports asynchornous
port types, tm.commit will not function properly. However, if you try this
inside a container like Axis, things will work as expected.
Thanks,
-- dasarath
> Hi,
>
>
>
> Agreed.
>
>
>
> Let's go step by step.
>
>
>
> I am using the Kandula activation service. The coordination context is being
> created. The coordination context is also being embedded in the soap envelope
> and the web service operation is then invoked.
>
>
>
>
>
> I am using a client level handler which invokes the Kandula activation
> service and creates the context and puts the coordination context in the soap
> header. (similar to what is done in the TM begin() method)
>
>
>
> The client handler has the invoke method which does the same.
>
>
>
> public void invoke(MessageContext mc) throws AxisFault
>
> {
>
> System.out.println("handler");
>
> CoordinationContext ctx;
>
> CoordinationContextType ctxType;
>
> try {
>
> ActivationStub stub = new
> ActivationStub(new EndpointReference(
>
>
> "http://localhost:1234/axis/services/activationCoordinator"));
>
> ctx =
> stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
>
>
> SOAPHeader header =
> mc.getCurrentMessage().getSOAPEnvelope().getHeader();
>
>
> ctx.toSOAPHeaderElement(header);
>
> }catch (Exception re) {
>
> try {
>
> ctx = null;
>
> } catch
> (Exception e) {
>
>
> e.printStackTrace();
>
>
> }
>
> }
>
> }
>
>
>
> (1234 is the tcpmon port monitor directed to 8080 @
> axis/services/activationCoordinator)
>
>
>
> The coordination context which is being in the soap request header while
> invoking the web service operation is:
>
>
>
> <wscoor:CoordinationContext
> soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
> soapenv:mustUnderstand="0"
> xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
>
>
> <wscoor:Identifier>uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</wscoor:Identifier>
>
>
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
>
> <wscoor:RegistrationService>
>
> <wsa:Address
>
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
>
> <wsa:ReferenceProperties
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> <ns4:CallbackRef
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</ns4:CallbackRef>
>
> </wsa:ReferenceProperties>
>
> </wscoor:RegistrationService>
>
> </wscoor:CoordinationContext>
>
>
>
> Now after this is done, you suggested that the WAS should register the
> Kandula registration service (which would be I suppose
> http://localhost:8080/axis/services/registrationCoordinator) , I am not
> really sure how to achieve this.
>
>
>
> Any pointers?
>
>
>
> Thanking you in advance.
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
>
>
> -----Original Message-----
> From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> Sent: Monday, July 14, 2008 7:43 PM
> To: kandula-dev@ws.apache.org
> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> Subject: RE: Issues while compiling src code
>
>
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
>
>
> You should be able to use either coordinator. To use a different coordinator
>
> with the Kandula provided toy TM, you can specify the end point of the
>
> activation service to the begin() method.
>
>
>
> Note that the coordination context is created by the activation service.
>
> There is another Coordinator service which handles termination. Please
>
> make sure that you are not sending the CreateCoordinationContext message to
>
> the coordinator endpoint.
>
>
>
> If you are using the Kandula activation service, then once the coordination
>
> context has been created and the service on WAS is invoked with the
> coordination
>
> context, WAS should register with the Kandula registration service.
>
>
>
> If you are using WAS activation service, then service on WAS should register
>
> with the registration service on WAS.
>
>
>
> Let me know whether you get this far.
>
>
>
> Please post your questions on kandula-dev so that they get archived.
>
>
>
> Thanks,
>
> -- dasarath
>
>
>
>
>
> > That is exactly what I am trying to achieve using the Kandula client. And
>
> > that's where I am facing the issues L L
>
>
>
> >
>
> > Since I am using a Kandula client, the coordination context should be
> created
>
> > using web service activationCoordinator deployed on tomcat
>
> > àhttp://localhost:8080/axis/services/activationCoordinator, which is
> actually
>
> > being created and also being sent in the soap header in the soap request
>
> > while the web service on WAS. (PFA kandula-soap-request.xml)
>
> >
>
> > But then again, this transaction details is not working as the revoking
> part
>
> > is not working properly.
>
>
>
> >
>
> >
>
>
>
> >
>
> > Then I thought may be the coordination service of WAS should be invoked
> which
>
> > lies at http://localhost:9080/_IBMSYSAPP/wsat/services/Coordinator (which
>
> > might create the correct coordination context as required like attached à
>
> > WAS-Client-SOAP-request.xml ) but the request which is being sent to
> invoke
>
> > the coordinator service is not correct. (PFA the errors.txt)
>
> >
>
> >
>
>
>
> >
>
> > Thanks.
>
> >
>
> >
>
>
>
> >
>
> > Regards,
>
> >
>
> > Anshuk Pal Chaudhuri
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > -----Original Message-----
>
> > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
>
>
> > Sent: Friday, July 11, 2008 7:43 PM
>
> > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Subject: RE: Issues while compiling src code
>
> >
>
> >
>
>
>
> >
>
> > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> >
>
>
>
> >
>
> > Yes, this can be done. You can replace either the WAS box or MSFT box with
>
> >
>
> > Axis+Kandula or add Axis+Kandula as another branch of the same activity
>
> > along
>
> >
>
> > with the other two.
>
> >
>
> >
>
>
>
> >
>
> > If your resource is deployed in WAS then Kandula is only a client. Kandula
>
> >
>
> > will create a coordination context and then attach it to all invocations
>
> >
>
> > of your service methods on WAS and then finally terminate that transaction
>
> >
>
> > using WS-AT. Of course, we could add other resources to this activity
>
> > possibly
>
> >
>
> > residing outside of WAS. How your resource is configured and how the web
>
> > service
>
> >
>
> > is setup in WAS that you have to look at WAS docs. I would recommend that
>
> > you
>
> >
>
> > take the same WSDL of this interop scenario and try to generate a Kandula
>
> >
>
> > client. That way you can follow the same instructions on setting up the
> WAS
>
> > end.
>
> >
>
> >
>
>
>
> >
>
> > The other scenario is, WAS acts as the client and resource is deployed
>
> > inside
>
> >
>
> > Geronimo with Kandula providing the interfacing between WS-AT and JTA. You
>
> > can
>
> >
>
> > even test this with out involving Geronimo by using the toy TM that we
> have
>
> >
>
> > provided. Since we are only concerned about WS-AT, JTA side is not
>
> > important.
>
> >
>
> >
>
>
>
> >
>
> > I have tried inter-op testing Kandula with IBM implementation but had to
>
> > stop
>
> >
>
> > it due to a bug in their code.
>
> >
>
> >
>
>
>
> >
>
> > Happy testing!
>
> >
>
> > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks Dasarath for the input.
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > I am not trying to integrate Kandula with WAS as Kandula is being done
>
> >
>
> > > today with Geronimo. That is not my objective.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > The objective is:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Web Service Transaction Interoperability (Kandula Implementation and WAS
>
> >
>
> > > Implementation of Web Service Transaction)
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Web Service Client (build with axis generated stubs and using Kandula to
>
> >
>
> > > attach transaction details) ----------------------------> Web Service on
>
> >
>
> > > WAS (which does some insertion into database) Do you think this is
>
> >
>
> > > feasible or not?
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > The resources are defined (say datasource) within the WAS Container. Now
>
> >
>
> > > the question would be do I need to expose these resources (XAResource)
>
> >
>
> > > deployed within WAS using Kandula?
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > I was having a look somewhere
>
> >
>
> > > (http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
>
> >
>
> > > o/0707_lo.html ) where there are MS Web Service Clients (Web Service
>
> >
>
> > > Transactions configured) are interoperating with Web Services deployed
>
> >
>
> > > on WAS and the transaction management is happening. That is an excellent
>
> >
>
> > > case of web service transaction interoperability. What I am wondering is
>
> >
>
> > > if that is possible, then why not what I am trying out, where the client
>
> >
>
> > > would be using axis (instead of Microsoft) and the transaction
>
> >
>
> > > configuration would be done using Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Let me know if I am not clear.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > -----Original Message-----
>
> >
>
> > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
> >
>
> >
>
>
>
> >
>
> > > Sent: Thursday, July 10, 2008 10:55 PM
>
> >
>
> > > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > > Cc: kandula-dev@ws.apache.org
>
> >
>
> > > Subject: RE: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Quoting Anshuk <An...@cognizant.com>:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Interfacing JTA with WS-AT is completely different from
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > looking at web services interoperability between different
>
> >
>
> > > implementations
>
> >
>
> > >
>
>
>
> >
>
> > > like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
>
> >
>
> > > this point.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > If you want to expose some XAResource deployed inside WAS using Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > then you need to interface Kandula with the native JTA implementation in
>
> >
>
> > > WAS.
>
> >
>
> > >
>
>
>
> >
>
> > > What Kandula does is it creates a JTA transaction whenever it sees a new
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > coordination context and attaches it to the thread that would execute
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > the web service. From there on, the native JTA implementation takes care
>
> >
>
> > >
>
>
>
> >
>
> > > of the rest. In the absence of such a native JTA implementation we have
>
> >
>
> > > provided
>
> >
>
> > >
>
>
>
> >
>
> > > a toy JTA implementation that could be used but this is mainly for
>
> >
>
> > > testing.
>
> >
>
> > >
>
>
>
> >
>
> > > When the WS-AT protocol attempts to terminate the activity, Kandula will
>
> >
>
> > >
>
>
>
> >
>
> > > use its private interface with the native JTA implementation to
>
> >
>
> > > terminate
>
> >
>
> > >
>
>
>
> >
>
> > > the JTA transaction that was created earlier. Here Kandula uses the
>
> >
>
> > > two-phase
>
> >
>
> > >
>
>
>
> >
>
> > > commit protocol.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > However, the JTA API is not sufficient to completely handle the two
>
> >
>
> > > phase
>
> >
>
> > >
>
>
>
> >
>
> > > commit protocol that is used to terminate a transaction. For example, if
>
> >
>
> > >
>
>
>
> >
>
> > > you look at how Kandula has been interfaced with Geronimo, you would see
>
> >
>
> > >
>
>
>
> >
>
> > > that we have used an API exposed by the Geronimo transaction manager
>
> >
>
> > > which
>
> >
>
> > >
>
>
>
> >
>
> > > is non-standard. In the case of WAS it is not possible to study their
>
> >
>
> > >
>
>
>
> >
>
> > > internal API s to do the same. In short, it is not possible to do what
>
> >
>
> > > we have
>
> >
>
> > >
>
>
>
> >
>
> > > done with Geronimo with WAS.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > You could however, try the following:
>
> >
>
> > >
>
>
>
> >
>
> > > 1) Use a Kandula client with WAS server.
>
> >
>
> > >
>
>
>
> >
>
> > > 2) WAS client with Kandula server (in Geronimo server or Tomcat +
>
> >
>
> > > Geronimo
>
> >
>
> > >
>
>
>
> >
>
> > > transaction manager)
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > -- dasarath
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks Dasarath for the input.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > As I mentioned earlier, I did try out the WAS-WAS and it is working
>
> >
>
> > > fine. I
>
> >
>
> > >
>
>
>
> >
>
> > > > also tried out the Kandula-Kandula (as you mentioned about the banking
>
> >
>
> > >
>
>
>
> >
>
> > > > example)and it is also working fine.
>
> >
>
> > >
>
>
>
> >
>
> > > > Now w.r.t. the sceanrio which I described earlier, the first case
>
> >
>
> > > (WAS-WAS),
>
> >
>
> > >
>
>
>
> >
>
> > > > the datasource is defined within the WAS container, so the application
>
> >
>
> > > is
>
> >
>
> > >
>
>
>
> >
>
> > > > taking care of the rollback.
>
> >
>
> > >
>
>
>
> >
>
> > > > In the second case, (correct me if I am wrong), the resources are
>
> >
>
> > > defined in
>
> >
>
> > >
>
>
>
> >
>
> > > > the BankOneDBMS which implements NamedXAResource so the resources are
>
> >
>
> > >
>
>
>
> >
>
> > > > enlisted there only and the commit and rollback are managed explicitly
>
> >
>
> > >
>
>
>
> >
>
> > > > (using the Transaction Manager of Geronimo)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Now when I am trying to incorporate Kandula (at the client side) and
>
> >
>
> > > WAS (at
>
> >
>
> > >
>
>
>
> >
>
> > > > the server side, where the web service is deployed), the transaction
>
> >
>
> > >
>
>
>
> >
>
> > > > management is not taking place as expected.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > The co-ordination context (within the soap request) that I have sent
>
> >
>
> > > across
>
> >
>
> > >
>
>
>
> >
>
> > > > from WAS (when client) and Kandula (when client) seems to be
>
> >
>
> > > different.
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > In case of kandula (being client), the standalone client uses the
>
> >
>
> > > stubs
>
> >
>
> > >
>
>
>
> >
>
> > > > (generated from axis wsdl2java) and a client handler does the
>
> >
>
> > > following:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > public void invoke(MessageContext mc) throws AxisFault {
>
> >
>
> > >
>
>
>
> >
>
> > > > System.out.println("handler");
>
> >
>
> > >
>
>
>
> >
>
> > > > CoordinationContext ctx;
>
> >
>
> > >
>
>
>
> >
>
> > > > CoordinationContextType ctxType;
>
> >
>
> > >
>
>
>
> >
>
> > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > > ActivationStub stub = new
>
> >
>
> > > ActivationStub(new EndpointReference(
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > "http://localhost:8081/axis/services/activationCoordinator"));
>
> >
>
> > >
>
>
>
> >
>
> > > > ctx =
>
> >
>
> > > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > }catch (Exception re) {
>
> >
>
> > >
>
>
>
> >
>
> > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > > ctx =
>
> >
>
> > > null;
>
> >
>
> > >
>
>
>
> >
>
> > > > } catch
>
> >
>
> > > (Exception e) {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > e.printStackTrace();
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > }
>
> >
>
> > >
>
>
>
> >
>
> > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > I am not sure where I am going wrong.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Can you guide me on this.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > > Anshuk
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Dasarath Weeratunge-3 wrote:
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Have you looked at the banking example? If you are going to
>
> >
>
> > >
>
>
>
> >
>
> > > > > use WAS on one end and Kandula on the other end I would very much
>
> >
>
> > >
>
>
>
> >
>
> > > > > like to see what the result is going to be. I would recommend
>
> >
>
> > >
>
>
>
> >
>
> > > > > that you first try WAS-WAS and Kandula-Kandula before attempting
>
> >
>
> > >
>
>
>
> >
>
> > > > > WAS-Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > > what
>
> >
>
> > >
>
>
>
> >
>
> > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > This is unfortunately a little too gernal to answer over a mailing
>
> >
>
> > > list.
>
> >
>
> > >
>
>
>
> >
>
> > > > > Please be more specific/discrete about what you are trying to do.
>
> >
>
> > > For
>
> >
>
> > >
>
>
>
> >
>
> > > > > example,
>
> >
>
> > >
>
>
>
> >
>
> > > > > if you say you tried this and got this error, then we can tell you
>
> >
>
> > > why and
>
> >
>
> > >
>
>
>
> >
>
> > > > > what you need to do differently.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > > > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Hi Hannes,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Thanks for your input.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did try out using the atomic transaction that comes with the IBM
>
> >
>
> > > WAS
>
> >
>
> > >
>
>
>
> >
>
> > > > >> 6.0. The web service would insert some values in a database. The
>
> >
>
> > > web
>
> >
>
> > >
>
>
>
> >
>
> > > > >> service client was built using the stubs generated by the IBM SOAP
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Engine WSDL2Java and configured in such a way so that it would send
>
> >
>
> > >
>
>
>
> >
>
> > > > >> atomic transaction details in the soap envelope. So, I tested a
>
> >
>
> > > good
>
> >
>
> > >
>
>
>
> >
>
> > > > >> scenario and the values got inserted in the table. While testing
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> error scenario, in the web service after the part of the which does
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> insertion, I threw a runtime exception explicitly and when I
>
> >
>
> > > checked the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> tables, the values were not inserted.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Now I intend to do a similar scenario using Apache Kandula at the
>
> >
>
> > > client
>
> >
>
> > >
>
>
>
> >
>
> > > > >> side. The same web service (deployed on WAS) would be used, but
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> client would now send the soap request using apache Kandula and the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> necessary transaction details (within the soap header) would be
>
> >
>
> > > sent.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > > what
>
> >
>
> > >
>
>
>
> >
>
> > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Can you help/guide me in testing the above.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Thanking you in advance.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> -----Original Message-----
>
> >
>
> > >
>
>
>
> >
>
> > > > >> From: Hannes Erven [mailto:herven@apache.org]
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Sent: Sunday, June 29, 2008 4:37 AM
>
> >
>
> > >
>
>
>
> >
>
> > > > >> To: kandula-dev@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Subject: Re: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Hi Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> > What I am not clear is the flow how exactly the client creates
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> > co-ordination context and so on.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I'm not sure what you are exactly looking for and what you already
>
> >
>
> > > know
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> or have read.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> As a general starting point, I suggest you have a look at the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> WS-Coordination specification and also WS-AtomicTransaction or
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> WS-BusinessActivity, whatever transaction type you are interested
>
> >
>
> > > in.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> In the source code, at the Kandula server it all starts at
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> > > org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
>
> >
>
> > >
>
>
>
> >
>
> > > > >> text
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> , this is where the call from the client is received. From there,
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> actual transaction coordinator object is created depending on the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> requested type of transaction.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> If you have further questions or need reading tips, please reply
>
> >
>
> > > with
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> more details what you are interested in.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Best regards and thank you for your interest in Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> -hannes
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> This e-mail and any files transmitted with it are for the sole use
>
> >
>
> > > of the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> intended recipient(s) and may contain confidential and privileged
>
> >
>
> > >
>
>
>
> >
>
> > > > >> information.
>
> >
>
> > >
>
>
>
> >
>
> > > > >> If you are not the intended recipient, please contact the sender by
>
> >
>
> > > reply
>
> >
>
> > >
>
>
>
> >
>
> > > > >> e-mail and destroy all copies of the original message.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Any unauthorised review, use, disclosure, dissemination,
>
> >
>
> > > forwarding,
>
> >
>
> > >
>
>
>
> >
>
> > > > >> printing
>
> >
>
> > >
>
>
>
> >
>
> > > > >> or copying of this email or any action taken in reliance on this
>
> >
>
> > > e-mail
>
> >
>
> > >
>
>
>
> >
>
> > > > >> is
>
> >
>
> > >
>
>
>
> >
>
> > > > >> strictly
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> prohibited and may be unlawful.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > --
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > View this message in context:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
>
> >
>
> > > 3.html
>
> >
>
> > >
>
>
>
> >
>
> > > > Sent from the Kandula mailing list archive at Nabble.com.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > This e-mail and any files transmitted with it are for the sole use of
> the
>
> >
>
> > > intended recipient(s) and may contain confidential and privileged
>
> >
>
> > > information.
>
> >
>
> > > If you are not the intended recipient, please contact the sender by
> reply
>
> >
>
> > > e-mail and destroy all copies of the original message.
>
> >
>
> >
>
>
>
> >
>
> > > Any unauthorised review, use, disclosure, dissemination, forwarding,
>
> > printing
>
> >
>
> > > or copying of this email or any action taken in reliance on this e-mail
> is
>
> >
>
> > > strictly
>
> >
>
> >
>
>
>
> >
>
> > > prohibited and may be unlawful.
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
> >
>
> > This e-mail and any files transmitted with it are for the sole use of the
>
> > intended recipient(s) and may contain confidential and privileged
>
> > information.
>
> > If you are not the intended recipient, please contact the sender by reply
>
> > e-mail and destroy all copies of the original message.
>
>
>
> > Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing
>
> > or copying of this email or any action taken in reliance on this e-mail is
>
> > strictly
>
>
>
> > prohibited and may be unlawful.
>
>
>
>
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing
> or copying of this email or any action taken in reliance on this e-mail is
> strictly
> prohibited and may be unlawful.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Hi,
Thought the following might work:
public void invoke() throws RemoteException, ServiceException
{
DBUpdateService db = new DBUpdateServiceLocator();
DBUpdate invoke = db.getDBUpdate();
TransactionManagerImpl tm = TransactionManagerImpl.getInstance();
tm.begin();
try
{
invoke.insertTestOne(616,"cts");
}
catch (Exception e) {
tm.rollback();
}
tm.commit();
}
But there is a null pointer exception for the tm.rollback
java.lang.NullPointerException
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:796)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub.registerOperation(RegistrationPortTypeRPCBindingStub.java:290)
at org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:53)
at org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
at org.apache.kandula.coordinator.at.TransactionImpl.register(TransactionImpl.java:68)
at org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:136)
at org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at com.cts.db.ws.insert.Client.invoke(Client.java:62)
at com.cts.db.ws.insert.Client.main(Client.java:48)
Regards,
Anshuk Pal Chaudhuri
From: Pal Chaudhuri, Anshuk (Cognizant)
Sent: Wednesday, July 16, 2008 2:31 PM
To: kandula-dev@ws.apache.org
Cc: 'Dasarath Weeratunge'
Subject: RE: Issues while compiling src code
Hi,
As you suggested, I tried the following
public void invoke()
{
TransactionManagerImpl tm = TransactionManagerImpl.getInstance();
try {
tm.begin();
DBUpdateService db = new DBUpdateServiceLocator(); // using the stubs generated from the web service
DBUpdate invoke = db.getDBUpdate(); // using the stubs generated from the web service
invoke.insertTestOne(1,"anshuk"); // using the stubs generated from the web service
tm.commit();
}
catch (Exception e) {
e.printStackTrace();
}
}
But this is not revoking the inserted records from the database; When I checked the soap request in the tcpmon, the coordination context is not in the soap header of the request. Do I need to add any configuration or anything else?
Thanks.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
Sent: Tuesday, July 15, 2008 7:44 PM
To: kandula-dev@ws.apache.org
Cc: Pal Chaudhuri, Anshuk (Cognizant)
Subject: RE: Issues while compiling src code
Quoting Anshuk.PalChaudhuri@cognizant.com:
I don't understand why you have your own client level handler to
create a coordination context and then add it to out going messages!
Kandula already provides that mechanism and much more.
Just deploy Kandula in Axis according to the user guide and then
using a standalone client + the toy TM, invoke your WAS service inside a
transaction: toyTm.begin(); foo.invokeWASService(); toyTm.commit();
Since you are using a standalone client and Kandula only supports asynchornous
port types, tm.commit will not function properly. However, if you try this
inside a container like Axis, things will work as expected.
Thanks,
-- dasarath
> Hi,
>
>
>
> Agreed.
>
>
>
> Let's go step by step.
>
>
>
> I am using the Kandula activation service. The coordination context is being
> created. The coordination context is also being embedded in the soap envelope
> and the web service operation is then invoked.
>
>
>
>
>
> I am using a client level handler which invokes the Kandula activation
> service and creates the context and puts the coordination context in the soap
> header. (similar to what is done in the TM begin() method)
>
>
>
> The client handler has the invoke method which does the same.
>
>
>
> public void invoke(MessageContext mc) throws AxisFault
>
> {
>
> System.out.println("handler");
>
> CoordinationContext ctx;
>
> CoordinationContextType ctxType;
>
> try {
>
> ActivationStub stub = new
> ActivationStub(new EndpointReference(
>
>
> "http://localhost:1234/axis/services/activationCoordinator"));
>
> ctx =
> stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
>
>
> SOAPHeader header =
> mc.getCurrentMessage().getSOAPEnvelope().getHeader();
>
>
> ctx.toSOAPHeaderElement(header);
>
> }catch (Exception re) {
>
> try {
>
> ctx = null;
>
> } catch
> (Exception e) {
>
>
> e.printStackTrace();
>
>
> }
>
> }
>
> }
>
>
>
> (1234 is the tcpmon port monitor directed to 8080 @
> axis/services/activationCoordinator)
>
>
>
> The coordination context which is being in the soap request header while
> invoking the web service operation is:
>
>
>
> <wscoor:CoordinationContext
> soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
> soapenv:mustUnderstand="0"
> xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
>
>
> <wscoor:Identifier>uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</wscoor:Identifier>
>
>
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
>
> <wscoor:RegistrationService>
>
> <wsa:Address
>
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
>
> <wsa:ReferenceProperties
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> <ns4:CallbackRef
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</ns4:CallbackRef>
>
> </wsa:ReferenceProperties>
>
> </wscoor:RegistrationService>
>
> </wscoor:CoordinationContext>
>
>
>
> Now after this is done, you suggested that the WAS should register the
> Kandula registration service (which would be I suppose
> http://localhost:8080/axis/services/registrationCoordinator) , I am not
> really sure how to achieve this.
>
>
>
> Any pointers?
>
>
>
> Thanking you in advance.
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
>
>
> -----Original Message-----
> From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> Sent: Monday, July 14, 2008 7:43 PM
> To: kandula-dev@ws.apache.org
> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> Subject: RE: Issues while compiling src code
>
>
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
>
>
> You should be able to use either coordinator. To use a different coordinator
>
> with the Kandula provided toy TM, you can specify the end point of the
>
> activation service to the begin() method.
>
>
>
> Note that the coordination context is created by the activation service.
>
> There is another Coordinator service which handles termination. Please
>
> make sure that you are not sending the CreateCoordinationContext message to
>
> the coordinator endpoint.
>
>
>
> If you are using the Kandula activation service, then once the coordination
>
> context has been created and the service on WAS is invoked with the
> coordination
>
> context, WAS should register with the Kandula registration service.
>
>
>
> If you are using WAS activation service, then service on WAS should register
>
> with the registration service on WAS.
>
>
>
> Let me know whether you get this far.
>
>
>
> Please post your questions on kandula-dev so that they get archived.
>
>
>
> Thanks,
>
> -- dasarath
>
>
>
>
>
> > That is exactly what I am trying to achieve using the Kandula client. And
>
> > that's where I am facing the issues L L
>
>
>
> >
>
> > Since I am using a Kandula client, the coordination context should be
> created
>
> > using web service activationCoordinator deployed on tomcat
>
> > àhttp://localhost:8080/axis/services/activationCoordinator, which is
> actually
>
> > being created and also being sent in the soap header in the soap request
>
> > while the web service on WAS. (PFA kandula-soap-request.xml)
>
> >
>
> > But then again, this transaction details is not working as the revoking
> part
>
> > is not working properly.
>
>
>
> >
>
> >
>
>
>
> >
>
> > Then I thought may be the coordination service of WAS should be invoked
> which
>
> > lies at http://localhost:9080/_IBMSYSAPP/wsat/services/Coordinator (which
>
> > might create the correct coordination context as required like attached à
>
> > WAS-Client-SOAP-request.xml ) but the request which is being sent to
> invoke
>
> > the coordinator service is not correct. (PFA the errors.txt)
>
> >
>
> >
>
>
>
> >
>
> > Thanks.
>
> >
>
> >
>
>
>
> >
>
> > Regards,
>
> >
>
> > Anshuk Pal Chaudhuri
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > -----Original Message-----
>
> > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
>
>
> > Sent: Friday, July 11, 2008 7:43 PM
>
> > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Subject: RE: Issues while compiling src code
>
> >
>
> >
>
>
>
> >
>
> > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> >
>
>
>
> >
>
> > Yes, this can be done. You can replace either the WAS box or MSFT box with
>
> >
>
> > Axis+Kandula or add Axis+Kandula as another branch of the same activity
>
> > along
>
> >
>
> > with the other two.
>
> >
>
> >
>
>
>
> >
>
> > If your resource is deployed in WAS then Kandula is only a client. Kandula
>
> >
>
> > will create a coordination context and then attach it to all invocations
>
> >
>
> > of your service methods on WAS and then finally terminate that transaction
>
> >
>
> > using WS-AT. Of course, we could add other resources to this activity
>
> > possibly
>
> >
>
> > residing outside of WAS. How your resource is configured and how the web
>
> > service
>
> >
>
> > is setup in WAS that you have to look at WAS docs. I would recommend that
>
> > you
>
> >
>
> > take the same WSDL of this interop scenario and try to generate a Kandula
>
> >
>
> > client. That way you can follow the same instructions on setting up the
> WAS
>
> > end.
>
> >
>
> >
>
>
>
> >
>
> > The other scenario is, WAS acts as the client and resource is deployed
>
> > inside
>
> >
>
> > Geronimo with Kandula providing the interfacing between WS-AT and JTA. You
>
> > can
>
> >
>
> > even test this with out involving Geronimo by using the toy TM that we
> have
>
> >
>
> > provided. Since we are only concerned about WS-AT, JTA side is not
>
> > important.
>
> >
>
> >
>
>
>
> >
>
> > I have tried inter-op testing Kandula with IBM implementation but had to
>
> > stop
>
> >
>
> > it due to a bug in their code.
>
> >
>
> >
>
>
>
> >
>
> > Happy testing!
>
> >
>
> > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks Dasarath for the input.
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > I am not trying to integrate Kandula with WAS as Kandula is being done
>
> >
>
> > > today with Geronimo. That is not my objective.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > The objective is:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Web Service Transaction Interoperability (Kandula Implementation and WAS
>
> >
>
> > > Implementation of Web Service Transaction)
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Web Service Client (build with axis generated stubs and using Kandula to
>
> >
>
> > > attach transaction details) ----------------------------> Web Service on
>
> >
>
> > > WAS (which does some insertion into database) Do you think this is
>
> >
>
> > > feasible or not?
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > The resources are defined (say datasource) within the WAS Container. Now
>
> >
>
> > > the question would be do I need to expose these resources (XAResource)
>
> >
>
> > > deployed within WAS using Kandula?
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > I was having a look somewhere
>
> >
>
> > > (http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
>
> >
>
> > > o/0707_lo.html ) where there are MS Web Service Clients (Web Service
>
> >
>
> > > Transactions configured) are interoperating with Web Services deployed
>
> >
>
> > > on WAS and the transaction management is happening. That is an excellent
>
> >
>
> > > case of web service transaction interoperability. What I am wondering is
>
> >
>
> > > if that is possible, then why not what I am trying out, where the client
>
> >
>
> > > would be using axis (instead of Microsoft) and the transaction
>
> >
>
> > > configuration would be done using Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Let me know if I am not clear.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > -----Original Message-----
>
> >
>
> > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
> >
>
> >
>
>
>
> >
>
> > > Sent: Thursday, July 10, 2008 10:55 PM
>
> >
>
> > > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > > Cc: kandula-dev@ws.apache.org
>
> >
>
> > > Subject: RE: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Quoting Anshuk <An...@cognizant.com>:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Interfacing JTA with WS-AT is completely different from
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > looking at web services interoperability between different
>
> >
>
> > > implementations
>
> >
>
> > >
>
>
>
> >
>
> > > like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
>
> >
>
> > > this point.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > If you want to expose some XAResource deployed inside WAS using Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > then you need to interface Kandula with the native JTA implementation in
>
> >
>
> > > WAS.
>
> >
>
> > >
>
>
>
> >
>
> > > What Kandula does is it creates a JTA transaction whenever it sees a new
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > coordination context and attaches it to the thread that would execute
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > the web service. From there on, the native JTA implementation takes care
>
> >
>
> > >
>
>
>
> >
>
> > > of the rest. In the absence of such a native JTA implementation we have
>
> >
>
> > > provided
>
> >
>
> > >
>
>
>
> >
>
> > > a toy JTA implementation that could be used but this is mainly for
>
> >
>
> > > testing.
>
> >
>
> > >
>
>
>
> >
>
> > > When the WS-AT protocol attempts to terminate the activity, Kandula will
>
> >
>
> > >
>
>
>
> >
>
> > > use its private interface with the native JTA implementation to
>
> >
>
> > > terminate
>
> >
>
> > >
>
>
>
> >
>
> > > the JTA transaction that was created earlier. Here Kandula uses the
>
> >
>
> > > two-phase
>
> >
>
> > >
>
>
>
> >
>
> > > commit protocol.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > However, the JTA API is not sufficient to completely handle the two
>
> >
>
> > > phase
>
> >
>
> > >
>
>
>
> >
>
> > > commit protocol that is used to terminate a transaction. For example, if
>
> >
>
> > >
>
>
>
> >
>
> > > you look at how Kandula has been interfaced with Geronimo, you would see
>
> >
>
> > >
>
>
>
> >
>
> > > that we have used an API exposed by the Geronimo transaction manager
>
> >
>
> > > which
>
> >
>
> > >
>
>
>
> >
>
> > > is non-standard. In the case of WAS it is not possible to study their
>
> >
>
> > >
>
>
>
> >
>
> > > internal API s to do the same. In short, it is not possible to do what
>
> >
>
> > > we have
>
> >
>
> > >
>
>
>
> >
>
> > > done with Geronimo with WAS.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > You could however, try the following:
>
> >
>
> > >
>
>
>
> >
>
> > > 1) Use a Kandula client with WAS server.
>
> >
>
> > >
>
>
>
> >
>
> > > 2) WAS client with Kandula server (in Geronimo server or Tomcat +
>
> >
>
> > > Geronimo
>
> >
>
> > >
>
>
>
> >
>
> > > transaction manager)
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > -- dasarath
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks Dasarath for the input.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > As I mentioned earlier, I did try out the WAS-WAS and it is working
>
> >
>
> > > fine. I
>
> >
>
> > >
>
>
>
> >
>
> > > > also tried out the Kandula-Kandula (as you mentioned about the banking
>
> >
>
> > >
>
>
>
> >
>
> > > > example)and it is also working fine.
>
> >
>
> > >
>
>
>
> >
>
> > > > Now w.r.t. the sceanrio which I described earlier, the first case
>
> >
>
> > > (WAS-WAS),
>
> >
>
> > >
>
>
>
> >
>
> > > > the datasource is defined within the WAS container, so the application
>
> >
>
> > > is
>
> >
>
> > >
>
>
>
> >
>
> > > > taking care of the rollback.
>
> >
>
> > >
>
>
>
> >
>
> > > > In the second case, (correct me if I am wrong), the resources are
>
> >
>
> > > defined in
>
> >
>
> > >
>
>
>
> >
>
> > > > the BankOneDBMS which implements NamedXAResource so the resources are
>
> >
>
> > >
>
>
>
> >
>
> > > > enlisted there only and the commit and rollback are managed explicitly
>
> >
>
> > >
>
>
>
> >
>
> > > > (using the Transaction Manager of Geronimo)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Now when I am trying to incorporate Kandula (at the client side) and
>
> >
>
> > > WAS (at
>
> >
>
> > >
>
>
>
> >
>
> > > > the server side, where the web service is deployed), the transaction
>
> >
>
> > >
>
>
>
> >
>
> > > > management is not taking place as expected.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > The co-ordination context (within the soap request) that I have sent
>
> >
>
> > > across
>
> >
>
> > >
>
>
>
> >
>
> > > > from WAS (when client) and Kandula (when client) seems to be
>
> >
>
> > > different.
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > In case of kandula (being client), the standalone client uses the
>
> >
>
> > > stubs
>
> >
>
> > >
>
>
>
> >
>
> > > > (generated from axis wsdl2java) and a client handler does the
>
> >
>
> > > following:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > public void invoke(MessageContext mc) throws AxisFault {
>
> >
>
> > >
>
>
>
> >
>
> > > > System.out.println("handler");
>
> >
>
> > >
>
>
>
> >
>
> > > > CoordinationContext ctx;
>
> >
>
> > >
>
>
>
> >
>
> > > > CoordinationContextType ctxType;
>
> >
>
> > >
>
>
>
> >
>
> > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > > ActivationStub stub = new
>
> >
>
> > > ActivationStub(new EndpointReference(
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > "http://localhost:8081/axis/services/activationCoordinator"));
>
> >
>
> > >
>
>
>
> >
>
> > > > ctx =
>
> >
>
> > > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > }catch (Exception re) {
>
> >
>
> > >
>
>
>
> >
>
> > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > > ctx =
>
> >
>
> > > null;
>
> >
>
> > >
>
>
>
> >
>
> > > > } catch
>
> >
>
> > > (Exception e) {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > e.printStackTrace();
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > }
>
> >
>
> > >
>
>
>
> >
>
> > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > I am not sure where I am going wrong.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Can you guide me on this.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > > Anshuk
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Dasarath Weeratunge-3 wrote:
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Have you looked at the banking example? If you are going to
>
> >
>
> > >
>
>
>
> >
>
> > > > > use WAS on one end and Kandula on the other end I would very much
>
> >
>
> > >
>
>
>
> >
>
> > > > > like to see what the result is going to be. I would recommend
>
> >
>
> > >
>
>
>
> >
>
> > > > > that you first try WAS-WAS and Kandula-Kandula before attempting
>
> >
>
> > >
>
>
>
> >
>
> > > > > WAS-Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > > what
>
> >
>
> > >
>
>
>
> >
>
> > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > This is unfortunately a little too gernal to answer over a mailing
>
> >
>
> > > list.
>
> >
>
> > >
>
>
>
> >
>
> > > > > Please be more specific/discrete about what you are trying to do.
>
> >
>
> > > For
>
> >
>
> > >
>
>
>
> >
>
> > > > > example,
>
> >
>
> > >
>
>
>
> >
>
> > > > > if you say you tried this and got this error, then we can tell you
>
> >
>
> > > why and
>
> >
>
> > >
>
>
>
> >
>
> > > > > what you need to do differently.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > > > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Hi Hannes,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Thanks for your input.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did try out using the atomic transaction that comes with the IBM
>
> >
>
> > > WAS
>
> >
>
> > >
>
>
>
> >
>
> > > > >> 6.0. The web service would insert some values in a database. The
>
> >
>
> > > web
>
> >
>
> > >
>
>
>
> >
>
> > > > >> service client was built using the stubs generated by the IBM SOAP
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Engine WSDL2Java and configured in such a way so that it would send
>
> >
>
> > >
>
>
>
> >
>
> > > > >> atomic transaction details in the soap envelope. So, I tested a
>
> >
>
> > > good
>
> >
>
> > >
>
>
>
> >
>
> > > > >> scenario and the values got inserted in the table. While testing
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> error scenario, in the web service after the part of the which does
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> insertion, I threw a runtime exception explicitly and when I
>
> >
>
> > > checked the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> tables, the values were not inserted.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Now I intend to do a similar scenario using Apache Kandula at the
>
> >
>
> > > client
>
> >
>
> > >
>
>
>
> >
>
> > > > >> side. The same web service (deployed on WAS) would be used, but
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> client would now send the soap request using apache Kandula and the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> necessary transaction details (within the soap header) would be
>
> >
>
> > > sent.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > > what
>
> >
>
> > >
>
>
>
> >
>
> > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Can you help/guide me in testing the above.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Thanking you in advance.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> -----Original Message-----
>
> >
>
> > >
>
>
>
> >
>
> > > > >> From: Hannes Erven [mailto:herven@apache.org]
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Sent: Sunday, June 29, 2008 4:37 AM
>
> >
>
> > >
>
>
>
> >
>
> > > > >> To: kandula-dev@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Subject: Re: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Hi Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> > What I am not clear is the flow how exactly the client creates
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> > co-ordination context and so on.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I'm not sure what you are exactly looking for and what you already
>
> >
>
> > > know
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> or have read.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> As a general starting point, I suggest you have a look at the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> WS-Coordination specification and also WS-AtomicTransaction or
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> WS-BusinessActivity, whatever transaction type you are interested
>
> >
>
> > > in.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> In the source code, at the Kandula server it all starts at
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> > > org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
>
> >
>
> > >
>
>
>
> >
>
> > > > >> text
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> , this is where the call from the client is received. From there,
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> actual transaction coordinator object is created depending on the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> requested type of transaction.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> If you have further questions or need reading tips, please reply
>
> >
>
> > > with
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> more details what you are interested in.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Best regards and thank you for your interest in Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> -hannes
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> This e-mail and any files transmitted with it are for the sole use
>
> >
>
> > > of the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> intended recipient(s) and may contain confidential and privileged
>
> >
>
> > >
>
>
>
> >
>
> > > > >> information.
>
> >
>
> > >
>
>
>
> >
>
> > > > >> If you are not the intended recipient, please contact the sender by
>
> >
>
> > > reply
>
> >
>
> > >
>
>
>
> >
>
> > > > >> e-mail and destroy all copies of the original message.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Any unauthorised review, use, disclosure, dissemination,
>
> >
>
> > > forwarding,
>
> >
>
> > >
>
>
>
> >
>
> > > > >> printing
>
> >
>
> > >
>
>
>
> >
>
> > > > >> or copying of this email or any action taken in reliance on this
>
> >
>
> > > e-mail
>
> >
>
> > >
>
>
>
> >
>
> > > > >> is
>
> >
>
> > >
>
>
>
> >
>
> > > > >> strictly
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> prohibited and may be unlawful.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > --
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > View this message in context:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
>
> >
>
> > > 3.html
>
> >
>
> > >
>
>
>
> >
>
> > > > Sent from the Kandula mailing list archive at Nabble.com.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > This e-mail and any files transmitted with it are for the sole use of
> the
>
> >
>
> > > intended recipient(s) and may contain confidential and privileged
>
> >
>
> > > information.
>
> >
>
> > > If you are not the intended recipient, please contact the sender by
> reply
>
> >
>
> > > e-mail and destroy all copies of the original message.
>
> >
>
> >
>
>
>
> >
>
> > > Any unauthorised review, use, disclosure, dissemination, forwarding,
>
> > printing
>
> >
>
> > > or copying of this email or any action taken in reliance on this e-mail
> is
>
> >
>
> > > strictly
>
> >
>
> >
>
>
>
> >
>
> > > prohibited and may be unlawful.
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
> >
>
> > This e-mail and any files transmitted with it are for the sole use of the
>
> > intended recipient(s) and may contain confidential and privileged
>
> > information.
>
> > If you are not the intended recipient, please contact the sender by reply
>
> > e-mail and destroy all copies of the original message.
>
>
>
> > Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing
>
> > or copying of this email or any action taken in reliance on this e-mail is
>
> > strictly
>
>
>
> > prohibited and may be unlawful.
>
>
>
>
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing
> or copying of this email or any action taken in reliance on this e-mail is
> strictly
> prohibited and may be unlawful.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Hi,
Thanks Dasarath for your input.
Yeah, I am digging more into the interoperability issues. I would definitely be interested in submitting a document on the R&D work that I am currently doing in Web Services Transaction.
What I am currently testing is the both way interoperability.ie.
Client à Kandula WS Client (within the axis and Tomcat container) à IBM InsertOne WS (within the IBM WAS container) à InsertTwo Web Service using Kandula (within axis and tomcat)
As discussed earlier, the IBM WS would insert a record in a table in the database and the InsertTwo Kandula WS would insert one more record in a different table. The above mentioned grey highlighted part is working fine, i.e. Kandula Client and IBM WS Web Service.
But when the IBM WS (now becomes client for the next web service) is trying to invoke the InsertTwo Kandula WS (the highlighted red part), there is an issue. This issues is more of IBM problem (I am not sure whether you were talking this IBM issue earlier or not J J) , because the transaction framework of IBM while sending the transaction context details in the SOAP Request Header sends CoordinationContextType instead of the CoordinationContext (which should be as per the actual specification) , and eventually the transaction handler by kandula is not able to understand the same. I am not sure why exactly IBM has done this kind of an implementation which is not strictly adhering to standards.
To this, there is a workaround, which I read at http://opensource.sys-con.com/read/314083.htm, part of which states that
"Sometimes, vendors provide service packs or refresh packs to overcome discrepancies in the released version of the product. These packs might bring in changes in the supported specifications. These changes might break the existing interoperability or enable interoperability where it was absent earlier. For example, IBM WebSphere Application Server (WAS) 6.0 supports the element <CoordinationContextType> for WS-AT, but when the refresh pack 6.0.2.9 is applied over it, the supported element changes to <CoordinationContext>. You should analyze all such changes in the refresh packs before deciding to apply these packs."
So I am currently trying to update the same with 6.0.2.9 refresh pack, not sure how successful it would really be. Let's see.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
Sent: Friday, July 18, 2008 7:52 PM
To: Pal Chaudhuri, Anshuk (Cognizant)
Cc: kandula-dev@ws.apache.org
Subject: RE: Issues while compiling src code
Quoting Anshuk.PalChaudhuri@cognizant.com:
Kandula hasn't been used in any production environment as far as I know.
Until last year we didn't have a business activity implementation either.
Most people who used Kandula to date, did so for some academic purpose.
I think you need to dig more into the interoperability issues. Last time
I did testing I found out lot of problems when testing failure scenarios.
This is just for atomic transaction. Then there is a the business activity
protocol too. You also need to test both ends. If you could prepare a document
on the status of your experiments that would be a valuable contribution
to this project.
We have not looked at scalability issues. So far our emphasis has been on
protocol compliance. If the architecture itself is a bottleneck (which
wouldn't surprise me since it is very much centralized at present) then
we need to address those. But Axis engine too could be a problem and this
has already been looked at when designing Axis2.
We still do not have WS-AT/BA on Axis2. Lot of these things are based
on the need.
Thanks,
-- dasarath
> Hi,
>
> Thanks for your input.
>
> Yes, the coordination context is going in the soap request in the message.
> The interopservice (web service deployed within the axis container) is
> invoking the external WAS web service. And the WAS WS method that inserts
> records is also called with a transaction context (JTA).
> And at the same time the deployment descriptor of the web service application
> needs to configured to make it enabled Execute using Web Service Atomic
> Transaction on incoming request.
>
> Now things are working fine as expected.
>
> Now this makes me think about more scenarios, you said that the transaction
> manager that the kandula is providing is a toyTM, for testing purpose, has
> kandula been used till-date in production scenarios?
> The reason being when in case of interoperability issues, say we have a web
> application (which is a web service client using kandula and axis) which is
> deployed in one web container and while invoking the web service (a
> different web container using a different WS-AT Framework). How will Kandula
> scale up?
>
> Btw, this has been a real good learning process for me.
>
> Thanking you in advance.
>
>
> Regards,
> Anshuk Pal Chaudhuri
>
> -----Original Message-----
> From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> Sent: Wednesday, July 16, 2008 9:04 PM
> To: kandula-dev@ws.apache.org
> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> Subject: RE: Issues while compiling src code
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> If the coordination context is not been included in the message, then
> that means the transaction handler is not deployed properly. Most of the
> time this is due to some problem in your .wsdd file.
>
> Since the database (the resource) is inside the WAS box, the onus of
> removing the database records inserted falls on WAS. Kandula responsibility
> is to inform the rollback of the transaction to WAS /Coordinator endpoint.
>
> Once you call tm.rollback on the client side, There should be a rollback
> message
> sent from client to WAS box and WAS box should reply with an acknowledgment.
> The specific message sequence is there in the WS-AT specification.
> Kandula should send the rollback message to the /Coordinator endpoint
> provided
> in the WAS registration request and WAS should send the acknowledgment to
> the
> /Coordinator endpoint provided by Kandula in registration response.
>
> Before you get down to rollback, please check whether the service method
> that
> inserts records is called with a transaction context (JTA). Even if the
> service
> invocation has a coordination context, if the WAS side doesn't recognize it,
> the
> method may not be called with transaction context. If you look at the
> banking
> example, you can see how to print the transaction status.
>
> Thanks,
> -- dasarath
>
>
>
>
>
>
>
> > Hi,
> >
> >
>
> >
> > The scenario I have tried to create now is more like a banking example (I
> > have created a interopibmkandulaservice similar to bankone test which
> would
> > invoke the actual web service deployed on WAS)
> >
> >
>
> >
> > The coordination context is being attached now but the WAS web service
> > (where I have explicitly thrown a remote exception after a db insertion)
> is
> > not doing a rollback of the database values inserted.
> >
> >
>
> >
> > The code for interopibmkandulaservice (operation à testingInterop )
> deployed
> > on axis on tomcat:
> >
> >
>
> >
> > public void testingInterop() throws RemoteException, ServiceException {
> >
> > DBUpdateService db = new
> > DBUpdateServiceLocator();
> >
> >
>
> >
> > DBUpdate invoke = db.getDBUpdate();
> >
> > TransactionManagerImpl tm =
> > TransactionManagerImpl.getInstance();
> >
> > try
> >
> > {
> >
> > tm.begin();
> >
> >
> > invoke.insertTestOne(621,"anshuk");
> >
> > tm.commit();
> >
> > }
> >
> > catch(RemoteException re)
> >
> > {
> >
> > tm.rollback();
> >
> > }
> >
> > }
> >
> >
>
> >
> > The SOAP Request and Response for interopibmkandulaservice web service:
>
> >
> >
>
> >
> > Request
> >
> >
>
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> >
> > <soapenv:Body>
> >
> > <testingInterop xmlns=""/>
> >
> > </soapenv:Body>
> >
> > </soapenv:Envelope>
> >
> >
>
> >
> > Response
> >
> >
>
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> >
> > <soapenv:Body>
> >
> > <testingInteropResponse xmlns=""/>
> >
> > </soapenv:Body>
> >
> > </soapenv:Envelope>
> >
> >
>
> >
> > The SOAP Request and response for the WAS Web Service:
> >
> >
>
> >
> > Request
> >
> >
>
> >
> > <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
> >
> > <soapenv:Header>
> >
> > <wsa:MessageID
> >
>
soapenv:mustUnderstand="0">uuid:feacfe40-5342-11dd-bfe3-cce87efa941f</wsa:MessageID>
> >
> > <wsa:To
> >
>
soapenv:mustUnderstand="0">http://localhost:9082/IBM-KANDULA-INTEROPER-WS/services/DBUpdate</wsa:To>
> >
> > <wsa:Action
> >
>
soapenv:mustUnderstand="0">http://ws.apache.org/interop/ibm/IBMKandula#insertTestOne</wsa:Action>
> >
> > <wsa:From soapenv:mustUnderstand="0">
> >
> >
> >
>
<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
> >
> > </wsa:From>
> >
> > <wscoor:CoordinationContext
> > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
> > soapenv:mustUnderstand="0"
> > xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
> >
> >
> >
> <wscoor:Identifier>uuid:fe121dd0-5342-11dd-bfe3-cce87efa941f</wscoor:Identifier>
> >
> >
> >
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
> >
> > <wscoor:RegistrationService>
> >
> >
> >
>
<wsa:Address>http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
> >
> > <wsa:ReferenceProperties>
> >
> > <ns4:CallbackRef
> >
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:fe121dd0-5342-11dd-bfe3-cce87efa941f</ns4:CallbackRef>
> >
> > </wsa:ReferenceProperties>
> >
> > </wscoor:RegistrationService>
> >
> > </wscoor:CoordinationContext>
> >
> > </soapenv:Header>
> >
> > <soapenv:Body>
> >
> > <insertTestOne xmlns="http://ws.ibm.cts.com">
> >
> > <testOneId xmlns="">621</testOneId>
> >
> > <testOneDescription xmlns="">cts</testOneDescription>
> >
> > </insertTestOne>
> >
> > </soapenv:Body>
> >
> > </soapenv:Envelope>
> >
> >
>
> >
> >
>
> >
> > Response
> >
> >
>
> >
> > <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
> >
> > <soapenv:Header>
> >
> >
> >
> <wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action>
> >
> >
> >
> <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
> >
> >
> > <wsa:MessageID>uuid:2C42C087-011B-4000-E000-0DE00AE35A2E</wsa:MessageID>
> >
> >
> > <wsa:RelatesTo>uuid:feacfe40-5342-11dd-bfe3-cce87efa941f</wsa:RelatesTo>
> >
> > </soapenv:Header>
> >
> > <soapenv:Body>
> >
> > <soapenv:Fault>
> >
> > <faultcode>soapenv:Server.generalException</faultcode>
> >
> > <faultstring>java.rmi.RemoteException: WS IBM-KANDULA Interoper
> > FailedSimulated abort</faultstring>
> >
> > </soapenv:Fault>
> >
> > </soapenv:Body>
> >
> > </soapenv:Envelope>
> >
> >
>
> >
> > As suggested by Dasarath, the transaction management should work now but
> it's
> > not.
> >
> > I am not sure where I am going wrong.
> >
> >
>
> >
> > Thanks.
> >
> >
>
> >
> > Regards,
> >
> > Anshuk Pal Chaudhuri
> >
> >
>
> >
> > From: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Sent: Wednesday, July 16, 2008 4:03 PM
> > To: 'kandula-dev@ws.apache.org'
> > Cc: 'Dasarath Weeratunge'
> > Subject: RE: Issues while compiling src code
> >
> >
>
> >
> > Hi,
>
> >
> >
>
> >
> > Thought the following might work:
> >
> >
>
> >
> > public void invoke() throws RemoteException,
> > ServiceException
> >
> > {
> >
> > DBUpdateService db = new
> > DBUpdateServiceLocator();
> >
> > DBUpdate invoke = db.getDBUpdate();
> >
> > TransactionManagerImpl tm =
> > TransactionManagerImpl.getInstance();
> >
> > tm.begin();
> >
> > try
>
> >
> > {
> >
> >
> > invoke.insertTestOne(616,"cts");
> >
> > }
> >
> > catch (Exception e) {
> >
> >
> > tm.rollback();
> >
> > }
> >
> > tm.commit();
> >
> >
>
> >
> > }
> >
> >
>
> >
> > But there is a null pointer exception for the tm.rollback
> >
> >
>
> >
> > java.lang.NullPointerException
> >
> > at
> >
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
> >
> > at
> >
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
> >
> > at
> >
>
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
> >
> > at
> >
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
> >
> > at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
> >
> > at
> >
>
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
> >
> > at
> > org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
> >
> > at
> org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
> >
> > at
> >
> org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:796)
> >
> > at
> > org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
> >
> > at
> >
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
> >
> > at
> > org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> >
> > at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> >
> > at
> > org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
> >
> > at
> org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> >
> > at org.apache.axis.client.Call.invoke(Call.java:2767)
> >
> > at org.apache.axis.client.Call.invoke(Call.java:2443)
> >
> > at org.apache.axis.client.Call.invoke(Call.java:2366)
> >
> > at org.apache.axis.client.Call.invoke(Call.java:1812)
> >
> > at
> >
>
org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub.registerOperation(RegistrationPortTypeRPCBindingStub.java:290)
> >
> > at
> >
>
org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:53)
> >
> > at
> >
>
org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
> >
> > at
> >
>
org.apache.kandula.coordinator.at.TransactionImpl.register(TransactionImpl.java:68)
> >
> > at
> >
>
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:136)
> >
> > at
> >
>
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
> >
> > at com.cts.db.ws.insert.Client.invoke(Client.java:62)
> >
> > at com.cts.db.ws.insert.Client.main(Client.java:48)
> >
> >
>
> >
> >
>
> >
> > Regards,
> >
> > Anshuk Pal Chaudhuri
> >
> >
>
> >
> > From: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Sent: Wednesday, July 16, 2008 2:31 PM
> > To: kandula-dev@ws.apache.org
> > Cc: 'Dasarath Weeratunge'
> > Subject: RE: Issues while compiling src code
> >
> >
>
> >
> > Hi,
> >
> >
>
> >
> > As you suggested, I tried the following
>
> >
> >
>
> >
> > public void invoke()
> >
> > {
> >
> > TransactionManagerImpl tm =
> > TransactionManagerImpl.getInstance();
> >
> > try {
> >
> > tm.begin();
> >
> > DBUpdateService db = new
> > DBUpdateServiceLocator(); // using the stubs generated from the web
> service
> >
> > DBUpdate invoke =
> > db.getDBUpdate(); // using the stubs generated from the web service
> >
> >
> > invoke.insertTestOne(1,"anshuk"); // using the stubs generated from the
> web
> > service
> >
> > tm.commit();
> >
> > }
> >
> > catch (Exception e) {
> >
> > e.printStackTrace();
> >
> > }
> >
> > }
> >
> >
>
> >
> > But this is not revoking the inserted records from the database; When I
> > checked the soap request in the tcpmon, the coordination context is not in
> > the soap header of the request. Do I need to add any configuration or
> > anything else?
> >
> >
>
> >
> > Thanks.
> >
> >
>
> >
> >
>
> >
> > Regards,
> >
> > Anshuk Pal Chaudhuri
> >
> >
>
> >
> > -----Original Message-----
> > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
> > Sent: Tuesday, July 15, 2008 7:44 PM
> > To: kandula-dev@ws.apache.org
> > Cc: Pal Chaudhuri, Anshuk (Cognizant)
> > Subject: RE: Issues while compiling src code
> >
> >
>
> >
> > Quoting Anshuk.PalChaudhuri@cognizant.com:
> >
> >
>
> >
> > I don't understand why you have your own client level handler to
> >
> > create a coordination context and then add it to out going messages!
> >
> > Kandula already provides that mechanism and much more.
> >
> >
>
> >
> > Just deploy Kandula in Axis according to the user guide and then
> >
> > using a standalone client + the toy TM, invoke your WAS service inside a
> >
> > transaction: toyTm.begin(); foo.invokeWASService(); toyTm.commit();
> >
> >
>
> >
> > Since you are using a standalone client and Kandula only supports
> > asynchornous
> >
> > port types, tm.commit will not function properly. However, if you try this
> >
> > inside a container like Axis, things will work as expected.
> >
> >
>
> >
> > Thanks,
> >
> > -- dasarath
> >
> >
>
> >
> >
>
> >
> > > Hi,
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Agreed.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Let's go step by step.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > I am using the Kandula activation service. The coordination context is
> > being
> >
> > > created. The coordination context is also being embedded in the soap
> > envelope
> >
> > > and the web service operation is then invoked.
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > I am using a client level handler which invokes the Kandula activation
> >
> > > service and creates the context and puts the coordination context in the
> > soap
> >
> > > header. (similar to what is done in the TM begin() method)
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > The client handler has the invoke method which does the same.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > public void invoke(MessageContext mc) throws AxisFault
> >
> >
>
> >
> > >
>
> >
> > > {
> >
> > >
>
> >
> > > System.out.println("handler");
> >
> > >
>
> >
> > > CoordinationContext ctx;
> >
> > >
>
> >
> > > CoordinationContextType ctxType;
> >
> > >
>
> >
> > > try {
> >
> > >
>
> >
> > > ActivationStub stub =
> new
> >
> > > ActivationStub(new EndpointReference(
> >
> > >
>
> >
> > >
>
> >
> > > "http://localhost:1234/axis/services/activationCoordinator"));
> >
> > >
>
> >
> > > ctx =
> >
> > > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > SOAPHeader header =
> >
> > > mc.getCurrentMessage().getSOAPEnvelope().getHeader();
> >
> > >
>
> >
> > >
>
> >
> > > ctx.toSOAPHeaderElement(header);
> >
> > >
>
> >
> > > }catch (Exception re) {
> >
> > >
>
> >
> > > try {
> >
> > >
>
> >
> > > ctx =
> > null;
> >
> > >
>
> >
> > > } catch
> >
> > > (Exception e) {
> >
> > >
>
> >
> > >
>
> >
>
> >
> > > e.printStackTrace();
> >
> > >
>
> >
> > >
>
> >
>
> >
> > > }
> >
> > >
>
> >
> > > }
> >
> > >
>
> >
> > > }
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > (1234 is the tcpmon port monitor directed to 8080 @
> >
> > > axis/services/activationCoordinator)
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > The coordination context which is being in the soap request header while
> >
> > > invoking the web service operation is:
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > <wscoor:CoordinationContext
> >
> > > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
> >
> > > soapenv:mustUnderstand="0"
> >
> > > xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
> >
> > >
>
> >
> > >
>
> >
> > >
> >
> <wscoor:Identifier>uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</wscoor:Identifier>
> >
> > >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
> >
> > >
>
> >
> > > <wscoor:RegistrationService>
> >
> > >
>
> >
> > > <wsa:Address
> >
> > >
>
> >
> >
>
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
> >
> > >
>
> >
> > > <wsa:ReferenceProperties
> >
> > > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
> >
> > >
>
> >
> > > <ns4:CallbackRef
> >
> > >
>
> >
> >
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</ns4:CallbackRef>
> >
> > >
>
> >
> > > </wsa:ReferenceProperties>
> >
> > >
>
> >
> > > </wscoor:RegistrationService>
> >
> > >
>
> >
> > > </wscoor:CoordinationContext>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Now after this is done, you suggested that the WAS should register the
> >
> > > Kandula registration service (which would be I suppose
> >
> > > http://localhost:8080/axis/services/registrationCoordinator) , I am not
> >
> > > really sure how to achieve this.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Any pointers?
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Thanking you in advance.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Regards,
> >
> > >
>
> >
> > > Anshuk Pal Chaudhuri
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > -----Original Message-----
> >
> > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> >
> >
>
> >
> > > Sent: Monday, July 14, 2008 7:43 PM
> >
> > > To: kandula-dev@ws.apache.org
> >
> > > Cc: Pal Chaudhuri, Anshuk (Cognizant)
> >
> > > Subject: RE: Issues while compiling src code
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Quoting Anshuk.PalChaudhuri@cognizant.com:
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > You should be able to use either coordinator. To use a different
> > coordinator
> >
> > >
>
> >
> > > with the Kandula provided toy TM, you can specify the end point of the
> >
> > >
>
> >
> > > activation service to the begin() method.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Note that the coordination context is created by the activation service.
> >
> > >
>
> >
> > > There is another Coordinator service which handles termination. Please
> >
> > >
>
> >
> > > make sure that you are not sending the CreateCoordinationContext message
> > to
> >
> > >
>
> >
> > > the coordinator endpoint.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > If you are using the Kandula activation service, then once the
> > coordination
> >
> > >
>
> >
> > > context has been created and the service on WAS is invoked with the
> >
> > > coordination
> >
> > >
>
> >
> > > context, WAS should register with the Kandula registration service.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > If you are using WAS activation service, then service on WAS should
> > register
> >
> > >
>
> >
> > > with the registration service on WAS.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Let me know whether you get this far.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Please post your questions on kandula-dev so that they get archived.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Thanks,
> >
> > >
>
> >
> > > -- dasarath
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > > That is exactly what I am trying to achieve using the Kandula client.
> > And
> >
> > >
>
> >
> > > > that's where I am facing the issues L L
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Since I am using a Kandula client, the coordination context should be
> >
> > > created
> >
> > >
>
> >
> > > > using web service activationCoordinator deployed on tomcat
> >
> > >
>
> >
> > > > àhttp://localhost:8080/axis/services/activationCoordinator, which is
> >
> > > actually
> >
> > >
>
> >
> > > > being created and also being sent in the soap header in the soap
> request
> >
> > >
>
> >
> > > > while the web service on WAS. (PFA kandula-soap-request.xml)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > But then again, this transaction details is not working as the
> revoking
> >
> > > part
> >
> > >
>
> >
> > > > is not working properly.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Then I thought may be the coordination service of WAS should be
> invoked
> >
> > > which
> >
> > >
>
> >
> > > > lies at http://localhost:9080/_IBMSYSAPP/wsat/services/Coordinator
> > (which
> >
> > >
>
> >
> > > > might create the correct coordination context as required like
> attached
> > à
> >
> > >
>
> >
> > > > WAS-Client-SOAP-request.xml ) but the request which is being sent to
> >
> > > invoke
> >
> > >
>
> >
> > > > the coordinator service is not correct. (PFA the errors.txt)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Thanks.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Regards,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Anshuk Pal Chaudhuri
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > -----Original Message-----
> >
> > >
>
> >
> > > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > > Sent: Friday, July 11, 2008 7:43 PM
> >
> > >
>
> >
> > > > To: Pal Chaudhuri, Anshuk (Cognizant)
> >
> > >
>
> >
> > > > Subject: RE: Issues while compiling src code
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Yes, this can be done. You can replace either the WAS box or MSFT box
> > with
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Axis+Kandula or add Axis+Kandula as another branch of the same
> activity
> >
> > >
>
> >
> > > > along
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > with the other two.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > If your resource is deployed in WAS then Kandula is only a client.
> > Kandula
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > will create a coordination context and then attach it to all
> invocations
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > of your service methods on WAS and then finally terminate that
> > transaction
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > using WS-AT. Of course, we could add other resources to this activity
> >
> > >
>
> >
> > > > possibly
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > residing outside of WAS. How your resource is configured and how the
> web
> >
> > >
>
> >
> > > > service
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > is setup in WAS that you have to look at WAS docs. I would recommend
> > that
> >
> > >
>
> >
> > > > you
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > take the same WSDL of this interop scenario and try to generate a
> > Kandula
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > client. That way you can follow the same instructions on setting up
> the
> >
> > > WAS
> >
> > >
>
> >
> > > > end.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > The other scenario is, WAS acts as the client and resource is deployed
> >
> > >
>
> >
> > > > inside
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Geronimo with Kandula providing the interfacing between WS-AT and JTA.
> > You
> >
> > >
>
> >
> > > > can
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > even test this with out involving Geronimo by using the toy TM that we
> >
> > > have
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > provided. Since we are only concerned about WS-AT, JTA side is not
> >
> > >
>
> >
> > > > important.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > I have tried inter-op testing Kandula with IBM implementation but had
> to
> >
> > >
>
> >
> > > > stop
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > it due to a bug in their code.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Happy testing!
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > -- dasarath
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Thanks Dasarath for the input.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > I am not trying to integrate Kandula with WAS as Kandula is being
> done
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > today with Geronimo. That is not my objective.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > The objective is:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Web Service Transaction Interoperability (Kandula Implementation and
> > WAS
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Implementation of Web Service Transaction)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Web Service Client (build with axis generated stubs and using
> Kandula
> > to
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > attach transaction details) ----------------------------> Web
> Service
> > on
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > WAS (which does some insertion into database) Do you think this is
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > feasible or not?
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > The resources are defined (say datasource) within the WAS Container.
> > Now
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the question would be do I need to expose these resources
> (XAResource)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > deployed within WAS using Kandula?
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > I was having a look somewhere
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> > (http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > o/0707_lo.html ) where there are MS Web Service Clients (Web Service
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Transactions configured) are interoperating with Web Services
> deployed
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > on WAS and the transaction management is happening. That is an
> > excellent
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > case of web service transaction interoperability. What I am
> wondering
> > is
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > if that is possible, then why not what I am trying out, where the
> > client
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > would be using axis (instead of Microsoft) and the transaction
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > configuration would be done using Kandula.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Let me know if I am not clear.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Regards,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Anshuk Pal Chaudhuri
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > -----Original Message-----
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Sent: Thursday, July 10, 2008 10:55 PM
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > To: Pal Chaudhuri, Anshuk (Cognizant)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Cc: kandula-dev@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Subject: RE: Issues while compiling src code
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Quoting Anshuk <An...@cognizant.com>:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Interfacing JTA with WS-AT is completely different from
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > looking at web services interoperability between different
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > implementations
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > this point.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > If you want to expose some XAResource deployed inside WAS using
> > Kandula,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > then you need to interface Kandula with the native JTA
> implementation
> > in
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > WAS.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > What Kandula does is it creates a JTA transaction whenever it sees a
> > new
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > coordination context and attaches it to the thread that would
> execute
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the web service. From there on, the native JTA implementation takes
> > care
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > of the rest. In the absence of such a native JTA implementation we
> > have
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > provided
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > a toy JTA implementation that could be used but this is mainly for
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > testing.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > When the WS-AT protocol attempts to terminate the activity, Kandula
> > will
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > use its private interface with the native JTA implementation to
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > terminate
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the JTA transaction that was created earlier. Here Kandula uses the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > two-phase
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > commit protocol.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > However, the JTA API is not sufficient to completely handle the two
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > phase
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > commit protocol that is used to terminate a transaction. For
> example,
> > if
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > you look at how Kandula has been interfaced with Geronimo, you would
> > see
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > that we have used an API exposed by the Geronimo transaction manager
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > which
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > is non-standard. In the case of WAS it is not possible to study
> their
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > internal API s to do the same. In short, it is not possible to do
> what
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > we have
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > done with Geronimo with WAS.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > You could however, try the following:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > 1) Use a Kandula client with WAS server.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > 2) WAS client with Kandula server (in Geronimo server or Tomcat +
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Geronimo
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > transaction manager)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Thanks,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > -- dasarath
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Thanks Dasarath for the input.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > As I mentioned earlier, I did try out the WAS-WAS and it is
> working
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > fine. I
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > also tried out the Kandula-Kandula (as you mentioned about the
> > banking
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > example)and it is also working fine.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Now w.r.t. the sceanrio which I described earlier, the first case
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > (WAS-WAS),
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > the datasource is defined within the WAS container, so the
> > application
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > is
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > taking care of the rollback.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > In the second case, (correct me if I am wrong), the resources are
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > defined in
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > the BankOneDBMS which implements NamedXAResource so the resources
> > are
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > enlisted there only and the commit and rollback are managed
> > explicitly
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > (using the Transaction Manager of Geronimo)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Now when I am trying to incorporate Kandula (at the client side)
> and
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > WAS (at
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > the server side, where the web service is deployed), the
> transaction
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > management is not taking place as expected.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > The co-ordination context (within the soap request) that I have
> sent
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > across
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > from WAS (when client) and Kandula (when client) seems to be
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > different.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > In case of kandula (being client), the standalone client uses the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > stubs
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > (generated from axis wsdl2java) and a client handler does the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > following:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > public void invoke(MessageContext mc) throws AxisFault {
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > System.out.println("handler");
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > CoordinationContext ctx;
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > CoordinationContextType ctxType;
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > try {
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > ActivationStub stub =
> > new
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > ActivationStub(new EndpointReference(
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > "http://localhost:8081/axis/services/activationCoordinator"));
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > ctx =
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > }catch (Exception re) {
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > try {
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > ctx =
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > null;
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > }
> catch
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > (Exception e) {
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > e.printStackTrace();
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > }
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > }
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > }
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > I am not sure where I am going wrong.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Can you guide me on this.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Thanks.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Regards,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Anshuk
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Dasarath Weeratunge-3 wrote:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > Anshuk,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > Have you looked at the banking example? If you are going to
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > use WAS on one end and Kandula on the other end I would very
> much
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > like to see what the result is going to be. I would recommend
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > that you first try WAS-WAS and Kandula-Kandula before attempting
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > WAS-Kandula.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> I did have a look at the documentation, but I am not exactly
> sure
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > what
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> needs to be done.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > This is unfortunately a little too gernal to answer over a
> mailing
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > list.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > Please be more specific/discrete about what you are trying to
> do.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > For
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > example,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > if you say you tried this and got this error, then we can tell
> you
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > why and
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > what you need to do differently.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > Thanks,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > -- dasarath
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Hi Hannes,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Thanks for your input.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> I did try out using the atomic transaction that comes with the
> > IBM
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > WAS
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> 6.0. The web service would insert some values in a database.
> The
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > web
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> service client was built using the stubs generated by the IBM
> > SOAP
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Engine WSDL2Java and configured in such a way so that it would
> > send
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> atomic transaction details in the soap envelope. So, I tested a
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > good
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> scenario and the values got inserted in the table. While
> testing
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> error scenario, in the web service after the part of the which
> > does
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> insertion, I threw a runtime exception explicitly and when I
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > checked the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> tables, the values were not inserted.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Now I intend to do a similar scenario using Apache Kandula at
> the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > client
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> side. The same web service (deployed on WAS) would be used,
> but
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> client would now send the soap request using apache Kandula and
> > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> necessary transaction details (within the soap header) would be
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > sent.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> I did have a look at the documentation, but I am not exactly
> sure
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > what
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> needs to be done.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Can you help/guide me in testing the above.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Thanking you in advance.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Regards,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Anshuk Pal Chaudhuri
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> -----Original Message-----
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> From: Hannes Erven [mailto:herven@apache.org]
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Sent: Sunday, June 29, 2008 4:37 AM
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> To: kandula-dev@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Subject: Re: Issues while compiling src code
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Hi Anshuk,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> > What I am not clear is the flow how exactly the client
> creates
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> > co-ordination context and so on.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> I'm not sure what you are exactly looking for and what you
> > already
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > know
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> or have read.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> As a general starting point, I suggest you have a look at the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> WS-Coordination specification and also WS-AtomicTransaction or
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> WS-BusinessActivity, whatever transaction type you are
> interested
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > in.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> In the source code, at the Kandula server it all starts at
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> > org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> text
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> , this is where the call from the client is received. From
> there,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> actual transaction coordinator object is created depending on
> the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> requested type of transaction.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> If you have further questions or need reading tips, please
> reply
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > with
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> more details what you are interested in.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Best regards and thank you for your interest in Kandula,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> -hannes
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> This e-mail and any files transmitted with it are for the sole
> > use
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > of the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> intended recipient(s) and may contain confidential and
> privileged
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> information.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> If you are not the intended recipient, please contact the
> sender
> > by
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > reply
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> e-mail and destroy all copies of the original message.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Any unauthorised review, use, disclosure, dissemination,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > forwarding,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> printing
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> or copying of this email or any action taken in reliance on
> this
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > e-mail
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> is
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> strictly
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> prohibited and may be unlawful.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> ---------------------------------------------------------------------
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> ---------------------------------------------------------------------
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > --
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > View this message in context:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> > http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > 3.html
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Sent from the Kandula mailing list archive at Nabble.com.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> > ---------------------------------------------------------------------
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > This e-mail and any files transmitted with it are for the sole use
> of
> >
> > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > intended recipient(s) and may contain confidential and privileged
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > information.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > If you are not the intended recipient, please contact the sender by
> >
> > > reply
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > e-mail and destroy all copies of the original message.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Any unauthorised review, use, disclosure, dissemination, forwarding,
> >
> > >
>
> >
> > > > printing
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > or copying of this email or any action taken in reliance on this
> > e-mail
> >
> > > is
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > strictly
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > prohibited and may be unlawful.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > This e-mail and any files transmitted with it are for the sole use of
> > the
> >
> > >
>
> >
> > > > intended recipient(s) and may contain confidential and privileged
> >
> > >
>
> >
> > > > information.
> >
> > >
>
> >
> > > > If you are not the intended recipient, please contact the sender by
> > reply
> >
> > >
>
> >
> > > > e-mail and destroy all copies of the original message.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > > Any unauthorised review, use, disclosure, dissemination, forwarding,
> >
> > > printing
> >
> > >
>
> >
> > > > or copying of this email or any action taken in reliance on this
> e-mail
> > is
> >
> > >
>
> >
> > > > strictly
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > > prohibited and may be unlawful.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> > >
>
> >
> > > This e-mail and any files transmitted with it are for the sole use of
> the
> >
> > > intended recipient(s) and may contain confidential and privileged
> >
> > > information.
> >
> > > If you are not the intended recipient, please contact the sender by
> reply
> >
> > > e-mail and destroy all copies of the original message.
> >
> >
>
> >
> > > Any unauthorised review, use, disclosure, dissemination, forwarding,
> > printing
> >
> > > or copying of this email or any action taken in reliance on this e-mail
> is
> >
> > > strictly
> >
> >
>
> >
> > > prohibited and may be unlawful.
> >
> >
>
> >
> >
>
> >
> >
> >
> > This e-mail and any files transmitted with it are for the sole use of the
> > intended recipient(s) and may contain confidential and privileged
> > information.
> > If you are not the intended recipient, please contact the sender by reply
> > e-mail and destroy all copies of the original message.
>
> > Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing
> > or copying of this email or any action taken in reliance on this e-mail is
> > strictly
>
> > prohibited and may be unlawful.
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing
> or copying of this email or any action taken in reliance on this e-mail is
> strictly
> prohibited and may be unlawful.
>
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
RE: Issues while compiling src code
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Anshuk.PalChaudhuri@cognizant.com:
Kandula hasn't been used in any production environment as far as I know.
Until last year we didn't have a business activity implementation either.
Most people who used Kandula to date, did so for some academic purpose.
I think you need to dig more into the interoperability issues. Last time
I did testing I found out lot of problems when testing failure scenarios.
This is just for atomic transaction. Then there is a the business activity
protocol too. You also need to test both ends. If you could prepare a document
on the status of your experiments that would be a valuable contribution
to this project.
We have not looked at scalability issues. So far our emphasis has been on
protocol compliance. If the architecture itself is a bottleneck (which
wouldn't surprise me since it is very much centralized at present) then
we need to address those. But Axis engine too could be a problem and this
has already been looked at when designing Axis2.
We still do not have WS-AT/BA on Axis2. Lot of these things are based
on the need.
Thanks,
-- dasarath
> Hi,
>
> Thanks for your input.
>
> Yes, the coordination context is going in the soap request in the message.
> The interopservice (web service deployed within the axis container) is
> invoking the external WAS web service. And the WAS WS method that inserts
> records is also called with a transaction context (JTA).
> And at the same time the deployment descriptor of the web service application
> needs to configured to make it enabled Execute using Web Service Atomic
> Transaction on incoming request.
>
> Now things are working fine as expected.
>
> Now this makes me think about more scenarios, you said that the transaction
> manager that the kandula is providing is a toyTM, for testing purpose, has
> kandula been used till-date in production scenarios?
> The reason being when in case of interoperability issues, say we have a web
> application (which is a web service client using kandula and axis) which is
> deployed in one web container and while invoking the web service (a
> different web container using a different WS-AT Framework). How will Kandula
> scale up?
>
> Btw, this has been a real good learning process for me.
>
> Thanking you in advance.
>
>
> Regards,
> Anshuk Pal Chaudhuri
>
> -----Original Message-----
> From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> Sent: Wednesday, July 16, 2008 9:04 PM
> To: kandula-dev@ws.apache.org
> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> Subject: RE: Issues while compiling src code
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> If the coordination context is not been included in the message, then
> that means the transaction handler is not deployed properly. Most of the
> time this is due to some problem in your .wsdd file.
>
> Since the database (the resource) is inside the WAS box, the onus of
> removing the database records inserted falls on WAS. Kandula responsibility
> is to inform the rollback of the transaction to WAS /Coordinator endpoint.
>
> Once you call tm.rollback on the client side, There should be a rollback
> message
> sent from client to WAS box and WAS box should reply with an acknowledgment.
> The specific message sequence is there in the WS-AT specification.
> Kandula should send the rollback message to the /Coordinator endpoint
> provided
> in the WAS registration request and WAS should send the acknowledgment to
> the
> /Coordinator endpoint provided by Kandula in registration response.
>
> Before you get down to rollback, please check whether the service method
> that
> inserts records is called with a transaction context (JTA). Even if the
> service
> invocation has a coordination context, if the WAS side doesn't recognize it,
> the
> method may not be called with transaction context. If you look at the
> banking
> example, you can see how to print the transaction status.
>
> Thanks,
> -- dasarath
>
>
>
>
>
>
>
> > Hi,
> >
> >
>
> >
> > The scenario I have tried to create now is more like a banking example (I
> > have created a interopibmkandulaservice similar to bankone test which
> would
> > invoke the actual web service deployed on WAS)
> >
> >
>
> >
> > The coordination context is being attached now but the WAS web service
> > (where I have explicitly thrown a remote exception after a db insertion)
> is
> > not doing a rollback of the database values inserted.
> >
> >
>
> >
> > The code for interopibmkandulaservice (operation à testingInterop )
> deployed
> > on axis on tomcat:
> >
> >
>
> >
> > public void testingInterop() throws RemoteException, ServiceException {
> >
> > DBUpdateService db = new
> > DBUpdateServiceLocator();
> >
> >
>
> >
> > DBUpdate invoke = db.getDBUpdate();
> >
> > TransactionManagerImpl tm =
> > TransactionManagerImpl.getInstance();
> >
> > try
> >
> > {
> >
> > tm.begin();
> >
> >
> > invoke.insertTestOne(621,"anshuk");
> >
> > tm.commit();
> >
> > }
> >
> > catch(RemoteException re)
> >
> > {
> >
> > tm.rollback();
> >
> > }
> >
> > }
> >
> >
>
> >
> > The SOAP Request and Response for interopibmkandulaservice web service:
>
> >
> >
>
> >
> > Request
> >
> >
>
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> >
> > <soapenv:Body>
> >
> > <testingInterop xmlns=""/>
> >
> > </soapenv:Body>
> >
> > </soapenv:Envelope>
> >
> >
>
> >
> > Response
> >
> >
>
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> >
> > <soapenv:Body>
> >
> > <testingInteropResponse xmlns=""/>
> >
> > </soapenv:Body>
> >
> > </soapenv:Envelope>
> >
> >
>
> >
> > The SOAP Request and response for the WAS Web Service:
> >
> >
>
> >
> > Request
> >
> >
>
> >
> > <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
> >
> > <soapenv:Header>
> >
> > <wsa:MessageID
> >
>
soapenv:mustUnderstand="0">uuid:feacfe40-5342-11dd-bfe3-cce87efa941f</wsa:MessageID>
> >
> > <wsa:To
> >
>
soapenv:mustUnderstand="0">http://localhost:9082/IBM-KANDULA-INTEROPER-WS/services/DBUpdate</wsa:To>
> >
> > <wsa:Action
> >
>
soapenv:mustUnderstand="0">http://ws.apache.org/interop/ibm/IBMKandula#insertTestOne</wsa:Action>
> >
> > <wsa:From soapenv:mustUnderstand="0">
> >
> >
> >
>
<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
> >
> > </wsa:From>
> >
> > <wscoor:CoordinationContext
> > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
> > soapenv:mustUnderstand="0"
> > xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
> >
> >
> >
> <wscoor:Identifier>uuid:fe121dd0-5342-11dd-bfe3-cce87efa941f</wscoor:Identifier>
> >
> >
> >
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
> >
> > <wscoor:RegistrationService>
> >
> >
> >
>
<wsa:Address>http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
> >
> > <wsa:ReferenceProperties>
> >
> > <ns4:CallbackRef
> >
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:fe121dd0-5342-11dd-bfe3-cce87efa941f</ns4:CallbackRef>
> >
> > </wsa:ReferenceProperties>
> >
> > </wscoor:RegistrationService>
> >
> > </wscoor:CoordinationContext>
> >
> > </soapenv:Header>
> >
> > <soapenv:Body>
> >
> > <insertTestOne xmlns="http://ws.ibm.cts.com">
> >
> > <testOneId xmlns="">621</testOneId>
> >
> > <testOneDescription xmlns="">cts</testOneDescription>
> >
> > </insertTestOne>
> >
> > </soapenv:Body>
> >
> > </soapenv:Envelope>
> >
> >
>
> >
> >
>
> >
> > Response
> >
> >
>
> >
> > <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
> >
> > <soapenv:Header>
> >
> >
> >
> <wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action>
> >
> >
> >
> <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
> >
> >
> > <wsa:MessageID>uuid:2C42C087-011B-4000-E000-0DE00AE35A2E</wsa:MessageID>
> >
> >
> > <wsa:RelatesTo>uuid:feacfe40-5342-11dd-bfe3-cce87efa941f</wsa:RelatesTo>
> >
> > </soapenv:Header>
> >
> > <soapenv:Body>
> >
> > <soapenv:Fault>
> >
> > <faultcode>soapenv:Server.generalException</faultcode>
> >
> > <faultstring>java.rmi.RemoteException: WS IBM-KANDULA Interoper
> > FailedSimulated abort</faultstring>
> >
> > </soapenv:Fault>
> >
> > </soapenv:Body>
> >
> > </soapenv:Envelope>
> >
> >
>
> >
> > As suggested by Dasarath, the transaction management should work now but
> it's
> > not.
> >
> > I am not sure where I am going wrong.
> >
> >
>
> >
> > Thanks.
> >
> >
>
> >
> > Regards,
> >
> > Anshuk Pal Chaudhuri
> >
> >
>
> >
> > From: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Sent: Wednesday, July 16, 2008 4:03 PM
> > To: 'kandula-dev@ws.apache.org'
> > Cc: 'Dasarath Weeratunge'
> > Subject: RE: Issues while compiling src code
> >
> >
>
> >
> > Hi,
>
> >
> >
>
> >
> > Thought the following might work:
> >
> >
>
> >
> > public void invoke() throws RemoteException,
> > ServiceException
> >
> > {
> >
> > DBUpdateService db = new
> > DBUpdateServiceLocator();
> >
> > DBUpdate invoke = db.getDBUpdate();
> >
> > TransactionManagerImpl tm =
> > TransactionManagerImpl.getInstance();
> >
> > tm.begin();
> >
> > try
>
> >
> > {
> >
> >
> > invoke.insertTestOne(616,"cts");
> >
> > }
> >
> > catch (Exception e) {
> >
> >
> > tm.rollback();
> >
> > }
> >
> > tm.commit();
> >
> >
>
> >
> > }
> >
> >
>
> >
> > But there is a null pointer exception for the tm.rollback
> >
> >
>
> >
> > java.lang.NullPointerException
> >
> > at
> >
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
> >
> > at
> >
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
> >
> > at
> >
>
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
> >
> > at
> >
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
> >
> > at
> >
>
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
> >
> > at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
> >
> > at
> >
>
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
> >
> > at
> > org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
> >
> > at
> org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
> >
> > at
> >
> org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:796)
> >
> > at
> > org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
> >
> > at
> >
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
> >
> > at
> > org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> >
> > at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> >
> > at
> > org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
> >
> > at
> org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> >
> > at org.apache.axis.client.Call.invoke(Call.java:2767)
> >
> > at org.apache.axis.client.Call.invoke(Call.java:2443)
> >
> > at org.apache.axis.client.Call.invoke(Call.java:2366)
> >
> > at org.apache.axis.client.Call.invoke(Call.java:1812)
> >
> > at
> >
>
org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub.registerOperation(RegistrationPortTypeRPCBindingStub.java:290)
> >
> > at
> >
>
org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:53)
> >
> > at
> >
>
org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
> >
> > at
> >
>
org.apache.kandula.coordinator.at.TransactionImpl.register(TransactionImpl.java:68)
> >
> > at
> >
>
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:136)
> >
> > at
> >
>
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
> >
> > at com.cts.db.ws.insert.Client.invoke(Client.java:62)
> >
> > at com.cts.db.ws.insert.Client.main(Client.java:48)
> >
> >
>
> >
> >
>
> >
> > Regards,
> >
> > Anshuk Pal Chaudhuri
> >
> >
>
> >
> > From: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Sent: Wednesday, July 16, 2008 2:31 PM
> > To: kandula-dev@ws.apache.org
> > Cc: 'Dasarath Weeratunge'
> > Subject: RE: Issues while compiling src code
> >
> >
>
> >
> > Hi,
> >
> >
>
> >
> > As you suggested, I tried the following
>
> >
> >
>
> >
> > public void invoke()
> >
> > {
> >
> > TransactionManagerImpl tm =
> > TransactionManagerImpl.getInstance();
> >
> > try {
> >
> > tm.begin();
> >
> > DBUpdateService db = new
> > DBUpdateServiceLocator(); // using the stubs generated from the web
> service
> >
> > DBUpdate invoke =
> > db.getDBUpdate(); // using the stubs generated from the web service
> >
> >
> > invoke.insertTestOne(1,"anshuk"); // using the stubs generated from the
> web
> > service
> >
> > tm.commit();
> >
> > }
> >
> > catch (Exception e) {
> >
> > e.printStackTrace();
> >
> > }
> >
> > }
> >
> >
>
> >
> > But this is not revoking the inserted records from the database; When I
> > checked the soap request in the tcpmon, the coordination context is not in
> > the soap header of the request. Do I need to add any configuration or
> > anything else?
> >
> >
>
> >
> > Thanks.
> >
> >
>
> >
> >
>
> >
> > Regards,
> >
> > Anshuk Pal Chaudhuri
> >
> >
>
> >
> > -----Original Message-----
> > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
> > Sent: Tuesday, July 15, 2008 7:44 PM
> > To: kandula-dev@ws.apache.org
> > Cc: Pal Chaudhuri, Anshuk (Cognizant)
> > Subject: RE: Issues while compiling src code
> >
> >
>
> >
> > Quoting Anshuk.PalChaudhuri@cognizant.com:
> >
> >
>
> >
> > I don't understand why you have your own client level handler to
> >
> > create a coordination context and then add it to out going messages!
> >
> > Kandula already provides that mechanism and much more.
> >
> >
>
> >
> > Just deploy Kandula in Axis according to the user guide and then
> >
> > using a standalone client + the toy TM, invoke your WAS service inside a
> >
> > transaction: toyTm.begin(); foo.invokeWASService(); toyTm.commit();
> >
> >
>
> >
> > Since you are using a standalone client and Kandula only supports
> > asynchornous
> >
> > port types, tm.commit will not function properly. However, if you try this
> >
> > inside a container like Axis, things will work as expected.
> >
> >
>
> >
> > Thanks,
> >
> > -- dasarath
> >
> >
>
> >
> >
>
> >
> > > Hi,
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Agreed.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Let's go step by step.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > I am using the Kandula activation service. The coordination context is
> > being
> >
> > > created. The coordination context is also being embedded in the soap
> > envelope
> >
> > > and the web service operation is then invoked.
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > I am using a client level handler which invokes the Kandula activation
> >
> > > service and creates the context and puts the coordination context in the
> > soap
> >
> > > header. (similar to what is done in the TM begin() method)
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > The client handler has the invoke method which does the same.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > public void invoke(MessageContext mc) throws AxisFault
> >
> >
>
> >
> > >
>
> >
> > > {
> >
> > >
>
> >
> > > System.out.println("handler");
> >
> > >
>
> >
> > > CoordinationContext ctx;
> >
> > >
>
> >
> > > CoordinationContextType ctxType;
> >
> > >
>
> >
> > > try {
> >
> > >
>
> >
> > > ActivationStub stub =
> new
> >
> > > ActivationStub(new EndpointReference(
> >
> > >
>
> >
> > >
>
> >
> > > "http://localhost:1234/axis/services/activationCoordinator"));
> >
> > >
>
> >
> > > ctx =
> >
> > > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > SOAPHeader header =
> >
> > > mc.getCurrentMessage().getSOAPEnvelope().getHeader();
> >
> > >
>
> >
> > >
>
> >
> > > ctx.toSOAPHeaderElement(header);
> >
> > >
>
> >
> > > }catch (Exception re) {
> >
> > >
>
> >
> > > try {
> >
> > >
>
> >
> > > ctx =
> > null;
> >
> > >
>
> >
> > > } catch
> >
> > > (Exception e) {
> >
> > >
>
> >
> > >
>
> >
>
> >
> > > e.printStackTrace();
> >
> > >
>
> >
> > >
>
> >
>
> >
> > > }
> >
> > >
>
> >
> > > }
> >
> > >
>
> >
> > > }
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > (1234 is the tcpmon port monitor directed to 8080 @
> >
> > > axis/services/activationCoordinator)
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > The coordination context which is being in the soap request header while
> >
> > > invoking the web service operation is:
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > <wscoor:CoordinationContext
> >
> > > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
> >
> > > soapenv:mustUnderstand="0"
> >
> > > xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
> >
> > >
>
> >
> > >
>
> >
> > >
> >
> <wscoor:Identifier>uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</wscoor:Identifier>
> >
> > >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
> >
> > >
>
> >
> > > <wscoor:RegistrationService>
> >
> > >
>
> >
> > > <wsa:Address
> >
> > >
>
> >
> >
>
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
> >
> > >
>
> >
> > > <wsa:ReferenceProperties
> >
> > > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
> >
> > >
>
> >
> > > <ns4:CallbackRef
> >
> > >
>
> >
> >
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</ns4:CallbackRef>
> >
> > >
>
> >
> > > </wsa:ReferenceProperties>
> >
> > >
>
> >
> > > </wscoor:RegistrationService>
> >
> > >
>
> >
> > > </wscoor:CoordinationContext>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Now after this is done, you suggested that the WAS should register the
> >
> > > Kandula registration service (which would be I suppose
> >
> > > http://localhost:8080/axis/services/registrationCoordinator) , I am not
> >
> > > really sure how to achieve this.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Any pointers?
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Thanking you in advance.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Regards,
> >
> > >
>
> >
> > > Anshuk Pal Chaudhuri
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > -----Original Message-----
> >
> > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> >
> >
>
> >
> > > Sent: Monday, July 14, 2008 7:43 PM
> >
> > > To: kandula-dev@ws.apache.org
> >
> > > Cc: Pal Chaudhuri, Anshuk (Cognizant)
> >
> > > Subject: RE: Issues while compiling src code
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Quoting Anshuk.PalChaudhuri@cognizant.com:
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > You should be able to use either coordinator. To use a different
> > coordinator
> >
> > >
>
> >
> > > with the Kandula provided toy TM, you can specify the end point of the
> >
> > >
>
> >
> > > activation service to the begin() method.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Note that the coordination context is created by the activation service.
> >
> > >
>
> >
> > > There is another Coordinator service which handles termination. Please
> >
> > >
>
> >
> > > make sure that you are not sending the CreateCoordinationContext message
> > to
> >
> > >
>
> >
> > > the coordinator endpoint.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > If you are using the Kandula activation service, then once the
> > coordination
> >
> > >
>
> >
> > > context has been created and the service on WAS is invoked with the
> >
> > > coordination
> >
> > >
>
> >
> > > context, WAS should register with the Kandula registration service.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > If you are using WAS activation service, then service on WAS should
> > register
> >
> > >
>
> >
> > > with the registration service on WAS.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Let me know whether you get this far.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Please post your questions on kandula-dev so that they get archived.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > Thanks,
> >
> > >
>
> >
> > > -- dasarath
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > > That is exactly what I am trying to achieve using the Kandula client.
> > And
> >
> > >
>
> >
> > > > that's where I am facing the issues L L
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Since I am using a Kandula client, the coordination context should be
> >
> > > created
> >
> > >
>
> >
> > > > using web service activationCoordinator deployed on tomcat
> >
> > >
>
> >
> > > > àhttp://localhost:8080/axis/services/activationCoordinator, which is
> >
> > > actually
> >
> > >
>
> >
> > > > being created and also being sent in the soap header in the soap
> request
> >
> > >
>
> >
> > > > while the web service on WAS. (PFA kandula-soap-request.xml)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > But then again, this transaction details is not working as the
> revoking
> >
> > > part
> >
> > >
>
> >
> > > > is not working properly.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Then I thought may be the coordination service of WAS should be
> invoked
> >
> > > which
> >
> > >
>
> >
> > > > lies at http://localhost:9080/_IBMSYSAPP/wsat/services/Coordinator
> > (which
> >
> > >
>
> >
> > > > might create the correct coordination context as required like
> attached
> > à
> >
> > >
>
> >
> > > > WAS-Client-SOAP-request.xml ) but the request which is being sent to
> >
> > > invoke
> >
> > >
>
> >
> > > > the coordinator service is not correct. (PFA the errors.txt)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Thanks.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Regards,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Anshuk Pal Chaudhuri
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > -----Original Message-----
> >
> > >
>
> >
> > > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > > Sent: Friday, July 11, 2008 7:43 PM
> >
> > >
>
> >
> > > > To: Pal Chaudhuri, Anshuk (Cognizant)
> >
> > >
>
> >
> > > > Subject: RE: Issues while compiling src code
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Yes, this can be done. You can replace either the WAS box or MSFT box
> > with
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Axis+Kandula or add Axis+Kandula as another branch of the same
> activity
> >
> > >
>
> >
> > > > along
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > with the other two.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > If your resource is deployed in WAS then Kandula is only a client.
> > Kandula
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > will create a coordination context and then attach it to all
> invocations
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > of your service methods on WAS and then finally terminate that
> > transaction
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > using WS-AT. Of course, we could add other resources to this activity
> >
> > >
>
> >
> > > > possibly
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > residing outside of WAS. How your resource is configured and how the
> web
> >
> > >
>
> >
> > > > service
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > is setup in WAS that you have to look at WAS docs. I would recommend
> > that
> >
> > >
>
> >
> > > > you
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > take the same WSDL of this interop scenario and try to generate a
> > Kandula
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > client. That way you can follow the same instructions on setting up
> the
> >
> > > WAS
> >
> > >
>
> >
> > > > end.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > The other scenario is, WAS acts as the client and resource is deployed
> >
> > >
>
> >
> > > > inside
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Geronimo with Kandula providing the interfacing between WS-AT and JTA.
> > You
> >
> > >
>
> >
> > > > can
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > even test this with out involving Geronimo by using the toy TM that we
> >
> > > have
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > provided. Since we are only concerned about WS-AT, JTA side is not
> >
> > >
>
> >
> > > > important.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > I have tried inter-op testing Kandula with IBM implementation but had
> to
> >
> > >
>
> >
> > > > stop
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > it due to a bug in their code.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > Happy testing!
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > -- dasarath
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Thanks Dasarath for the input.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > I am not trying to integrate Kandula with WAS as Kandula is being
> done
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > today with Geronimo. That is not my objective.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > The objective is:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Web Service Transaction Interoperability (Kandula Implementation and
> > WAS
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Implementation of Web Service Transaction)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Web Service Client (build with axis generated stubs and using
> Kandula
> > to
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > attach transaction details) ----------------------------> Web
> Service
> > on
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > WAS (which does some insertion into database) Do you think this is
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > feasible or not?
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > The resources are defined (say datasource) within the WAS Container.
> > Now
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the question would be do I need to expose these resources
> (XAResource)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > deployed within WAS using Kandula?
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > I was having a look somewhere
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> > (http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > o/0707_lo.html ) where there are MS Web Service Clients (Web Service
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Transactions configured) are interoperating with Web Services
> deployed
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > on WAS and the transaction management is happening. That is an
> > excellent
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > case of web service transaction interoperability. What I am
> wondering
> > is
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > if that is possible, then why not what I am trying out, where the
> > client
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > would be using axis (instead of Microsoft) and the transaction
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > configuration would be done using Kandula.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Let me know if I am not clear.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Regards,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Anshuk Pal Chaudhuri
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > -----Original Message-----
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Sent: Thursday, July 10, 2008 10:55 PM
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > To: Pal Chaudhuri, Anshuk (Cognizant)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Cc: kandula-dev@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Subject: RE: Issues while compiling src code
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Quoting Anshuk <An...@cognizant.com>:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Interfacing JTA with WS-AT is completely different from
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > looking at web services interoperability between different
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > implementations
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > this point.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > If you want to expose some XAResource deployed inside WAS using
> > Kandula,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > then you need to interface Kandula with the native JTA
> implementation
> > in
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > WAS.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > What Kandula does is it creates a JTA transaction whenever it sees a
> > new
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > coordination context and attaches it to the thread that would
> execute
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the web service. From there on, the native JTA implementation takes
> > care
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > of the rest. In the absence of such a native JTA implementation we
> > have
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > provided
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > a toy JTA implementation that could be used but this is mainly for
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > testing.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > When the WS-AT protocol attempts to terminate the activity, Kandula
> > will
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > use its private interface with the native JTA implementation to
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > terminate
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the JTA transaction that was created earlier. Here Kandula uses the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > two-phase
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > commit protocol.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > However, the JTA API is not sufficient to completely handle the two
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > phase
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > commit protocol that is used to terminate a transaction. For
> example,
> > if
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > you look at how Kandula has been interfaced with Geronimo, you would
> > see
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > that we have used an API exposed by the Geronimo transaction manager
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > which
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > is non-standard. In the case of WAS it is not possible to study
> their
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > internal API s to do the same. In short, it is not possible to do
> what
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > we have
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > done with Geronimo with WAS.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > You could however, try the following:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > 1) Use a Kandula client with WAS server.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > 2) WAS client with Kandula server (in Geronimo server or Tomcat +
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Geronimo
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > transaction manager)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Thanks,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > -- dasarath
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Thanks Dasarath for the input.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > As I mentioned earlier, I did try out the WAS-WAS and it is
> working
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > fine. I
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > also tried out the Kandula-Kandula (as you mentioned about the
> > banking
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > example)and it is also working fine.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Now w.r.t. the sceanrio which I described earlier, the first case
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > (WAS-WAS),
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > the datasource is defined within the WAS container, so the
> > application
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > is
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > taking care of the rollback.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > In the second case, (correct me if I am wrong), the resources are
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > defined in
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > the BankOneDBMS which implements NamedXAResource so the resources
> > are
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > enlisted there only and the commit and rollback are managed
> > explicitly
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > (using the Transaction Manager of Geronimo)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Now when I am trying to incorporate Kandula (at the client side)
> and
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > WAS (at
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > the server side, where the web service is deployed), the
> transaction
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > management is not taking place as expected.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > The co-ordination context (within the soap request) that I have
> sent
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > across
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > from WAS (when client) and Kandula (when client) seems to be
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > different.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > In case of kandula (being client), the standalone client uses the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > stubs
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > (generated from axis wsdl2java) and a client handler does the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > following:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > public void invoke(MessageContext mc) throws AxisFault {
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > System.out.println("handler");
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > CoordinationContext ctx;
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > CoordinationContextType ctxType;
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > try {
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > ActivationStub stub =
> > new
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > ActivationStub(new EndpointReference(
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > "http://localhost:8081/axis/services/activationCoordinator"));
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > ctx =
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > }catch (Exception re) {
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > try {
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > ctx =
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > null;
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > }
> catch
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > (Exception e) {
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > e.printStackTrace();
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > }
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > }
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > }
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > I am not sure where I am going wrong.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Can you guide me on this.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Thanks.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Regards,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Anshuk
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Dasarath Weeratunge-3 wrote:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > Anshuk,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > Have you looked at the banking example? If you are going to
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > use WAS on one end and Kandula on the other end I would very
> much
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > like to see what the result is going to be. I would recommend
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > that you first try WAS-WAS and Kandula-Kandula before attempting
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > WAS-Kandula.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> I did have a look at the documentation, but I am not exactly
> sure
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > what
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> needs to be done.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > This is unfortunately a little too gernal to answer over a
> mailing
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > list.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > Please be more specific/discrete about what you are trying to
> do.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > For
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > example,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > if you say you tried this and got this error, then we can tell
> you
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > why and
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > what you need to do differently.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > Thanks,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > -- dasarath
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Hi Hannes,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Thanks for your input.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> I did try out using the atomic transaction that comes with the
> > IBM
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > WAS
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> 6.0. The web service would insert some values in a database.
> The
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > web
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> service client was built using the stubs generated by the IBM
> > SOAP
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Engine WSDL2Java and configured in such a way so that it would
> > send
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> atomic transaction details in the soap envelope. So, I tested a
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > good
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> scenario and the values got inserted in the table. While
> testing
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> error scenario, in the web service after the part of the which
> > does
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> insertion, I threw a runtime exception explicitly and when I
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > checked the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> tables, the values were not inserted.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Now I intend to do a similar scenario using Apache Kandula at
> the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > client
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> side. The same web service (deployed on WAS) would be used,
> but
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> client would now send the soap request using apache Kandula and
> > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> necessary transaction details (within the soap header) would be
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > sent.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> I did have a look at the documentation, but I am not exactly
> sure
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > what
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> needs to be done.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Can you help/guide me in testing the above.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Thanking you in advance.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Regards,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Anshuk Pal Chaudhuri
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> -----Original Message-----
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> From: Hannes Erven [mailto:herven@apache.org]
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Sent: Sunday, June 29, 2008 4:37 AM
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> To: kandula-dev@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Subject: Re: Issues while compiling src code
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Hi Anshuk,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> > What I am not clear is the flow how exactly the client
> creates
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> > co-ordination context and so on.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> I'm not sure what you are exactly looking for and what you
> > already
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > know
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> or have read.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> As a general starting point, I suggest you have a look at the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> WS-Coordination specification and also WS-AtomicTransaction or
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> WS-BusinessActivity, whatever transaction type you are
> interested
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > in.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> In the source code, at the Kandula server it all starts at
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> > org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> text
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> , this is where the call from the client is received. From
> there,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> actual transaction coordinator object is created depending on
> the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> requested type of transaction.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> If you have further questions or need reading tips, please
> reply
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > with
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> more details what you are interested in.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Best regards and thank you for your interest in Kandula,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> -hannes
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> This e-mail and any files transmitted with it are for the sole
> > use
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > of the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> intended recipient(s) and may contain confidential and
> privileged
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> information.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> If you are not the intended recipient, please contact the
> sender
> > by
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > reply
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> e-mail and destroy all copies of the original message.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> Any unauthorised review, use, disclosure, dissemination,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > forwarding,
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> printing
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> or copying of this email or any action taken in reliance on
> this
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > e-mail
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> is
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> strictly
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> prohibited and may be unlawful.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> ---------------------------------------------------------------------
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> ---------------------------------------------------------------------
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > --
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > View this message in context:
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> > http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > 3.html
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > Sent from the Kandula mailing list archive at Nabble.com.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> > ---------------------------------------------------------------------
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > >
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > >
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > This e-mail and any files transmitted with it are for the sole use
> of
> >
> > > the
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > intended recipient(s) and may contain confidential and privileged
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > information.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > If you are not the intended recipient, please contact the sender by
> >
> > > reply
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > e-mail and destroy all copies of the original message.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > Any unauthorised review, use, disclosure, dissemination, forwarding,
> >
> > >
>
> >
> > > > printing
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > or copying of this email or any action taken in reliance on this
> > e-mail
> >
> > > is
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > strictly
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > > prohibited and may be unlawful.
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > >
> >
> >
>
> >
> > >
>
> >
> > > > This e-mail and any files transmitted with it are for the sole use of
> > the
> >
> > >
>
> >
> > > > intended recipient(s) and may contain confidential and privileged
> >
> > >
>
> >
> > > > information.
> >
> > >
>
> >
> > > > If you are not the intended recipient, please contact the sender by
> > reply
> >
> > >
>
> >
> > > > e-mail and destroy all copies of the original message.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > > Any unauthorised review, use, disclosure, dissemination, forwarding,
> >
> > > printing
> >
> > >
>
> >
> > > > or copying of this email or any action taken in reliance on this
> e-mail
> > is
> >
> > >
>
> >
> > > > strictly
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > > > prohibited and may be unlawful.
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> >
>
> >
> > >
>
> >
> > >
>
> >
> > >
>
> >
> > > This e-mail and any files transmitted with it are for the sole use of
> the
> >
> > > intended recipient(s) and may contain confidential and privileged
> >
> > > information.
> >
> > > If you are not the intended recipient, please contact the sender by
> reply
> >
> > > e-mail and destroy all copies of the original message.
> >
> >
>
> >
> > > Any unauthorised review, use, disclosure, dissemination, forwarding,
> > printing
> >
> > > or copying of this email or any action taken in reliance on this e-mail
> is
> >
> > > strictly
> >
> >
>
> >
> > > prohibited and may be unlawful.
> >
> >
>
> >
> >
>
> >
> >
> >
> > This e-mail and any files transmitted with it are for the sole use of the
> > intended recipient(s) and may contain confidential and privileged
> > information.
> > If you are not the intended recipient, please contact the sender by reply
> > e-mail and destroy all copies of the original message.
>
> > Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing
> > or copying of this email or any action taken in reliance on this e-mail is
> > strictly
>
> > prohibited and may be unlawful.
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing
> or copying of this email or any action taken in reliance on this e-mail is
> strictly
> prohibited and may be unlawful.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Hi,
Thanks for your input.
Yes, the coordination context is going in the soap request in the message. The interopservice (web service deployed within the axis container) is invoking the external WAS web service. And the WAS WS method that inserts records is also called with a transaction context (JTA).
And at the same time the deployment descriptor of the web service application needs to configured to make it enabled Execute using Web Service Atomic Transaction on incoming request.
Now things are working fine as expected.
Now this makes me think about more scenarios, you said that the transaction manager that the kandula is providing is a toyTM, for testing purpose, has kandula been used till-date in production scenarios?
The reason being when in case of interoperability issues, say we have a web application (which is a web service client using kandula and axis) which is deployed in one web container and while invoking the web service (a different web container using a different WS-AT Framework). How will Kandula scale up?
Btw, this has been a real good learning process for me.
Thanking you in advance.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
Sent: Wednesday, July 16, 2008 9:04 PM
To: kandula-dev@ws.apache.org
Cc: Pal Chaudhuri, Anshuk (Cognizant)
Subject: RE: Issues while compiling src code
Quoting Anshuk.PalChaudhuri@cognizant.com:
If the coordination context is not been included in the message, then
that means the transaction handler is not deployed properly. Most of the
time this is due to some problem in your .wsdd file.
Since the database (the resource) is inside the WAS box, the onus of
removing the database records inserted falls on WAS. Kandula responsibility
is to inform the rollback of the transaction to WAS /Coordinator endpoint.
Once you call tm.rollback on the client side, There should be a rollback message
sent from client to WAS box and WAS box should reply with an acknowledgment.
The specific message sequence is there in the WS-AT specification.
Kandula should send the rollback message to the /Coordinator endpoint provided
in the WAS registration request and WAS should send the acknowledgment to the
/Coordinator endpoint provided by Kandula in registration response.
Before you get down to rollback, please check whether the service method that
inserts records is called with a transaction context (JTA). Even if the service
invocation has a coordination context, if the WAS side doesn't recognize it, the
method may not be called with transaction context. If you look at the banking
example, you can see how to print the transaction status.
Thanks,
-- dasarath
> Hi,
>
>
>
> The scenario I have tried to create now is more like a banking example (I
> have created a interopibmkandulaservice similar to bankone test which would
> invoke the actual web service deployed on WAS)
>
>
>
> The coordination context is being attached now but the WAS web service
> (where I have explicitly thrown a remote exception after a db insertion) is
> not doing a rollback of the database values inserted.
>
>
>
> The code for interopibmkandulaservice (operation à testingInterop ) deployed
> on axis on tomcat:
>
>
>
> public void testingInterop() throws RemoteException, ServiceException {
>
> DBUpdateService db = new
> DBUpdateServiceLocator();
>
>
>
> DBUpdate invoke = db.getDBUpdate();
>
> TransactionManagerImpl tm =
> TransactionManagerImpl.getInstance();
>
> try
>
> {
>
> tm.begin();
>
>
> invoke.insertTestOne(621,"anshuk");
>
> tm.commit();
>
> }
>
> catch(RemoteException re)
>
> {
>
> tm.rollback();
>
> }
>
> }
>
>
>
> The SOAP Request and Response for interopibmkandulaservice web service:
>
>
>
> Request
>
>
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>
> <soapenv:Body>
>
> <testingInterop xmlns=""/>
>
> </soapenv:Body>
>
> </soapenv:Envelope>
>
>
>
> Response
>
>
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>
> <soapenv:Body>
>
> <testingInteropResponse xmlns=""/>
>
> </soapenv:Body>
>
> </soapenv:Envelope>
>
>
>
> The SOAP Request and response for the WAS Web Service:
>
>
>
> Request
>
>
>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> <soapenv:Header>
>
> <wsa:MessageID
>
soapenv:mustUnderstand="0">uuid:feacfe40-5342-11dd-bfe3-cce87efa941f</wsa:MessageID>
>
> <wsa:To
>
soapenv:mustUnderstand="0">http://localhost:9082/IBM-KANDULA-INTEROPER-WS/services/DBUpdate</wsa:To>
>
> <wsa:Action
>
soapenv:mustUnderstand="0">http://ws.apache.org/interop/ibm/IBMKandula#insertTestOne</wsa:Action>
>
> <wsa:From soapenv:mustUnderstand="0">
>
>
>
<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
>
> </wsa:From>
>
> <wscoor:CoordinationContext
> soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
> soapenv:mustUnderstand="0"
> xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
>
>
> <wscoor:Identifier>uuid:fe121dd0-5342-11dd-bfe3-cce87efa941f</wscoor:Identifier>
>
>
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
>
> <wscoor:RegistrationService>
>
>
>
<wsa:Address>http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
>
> <wsa:ReferenceProperties>
>
> <ns4:CallbackRef
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:fe121dd0-5342-11dd-bfe3-cce87efa941f</ns4:CallbackRef>
>
> </wsa:ReferenceProperties>
>
> </wscoor:RegistrationService>
>
> </wscoor:CoordinationContext>
>
> </soapenv:Header>
>
> <soapenv:Body>
>
> <insertTestOne xmlns="http://ws.ibm.cts.com">
>
> <testOneId xmlns="">621</testOneId>
>
> <testOneDescription xmlns="">cts</testOneDescription>
>
> </insertTestOne>
>
> </soapenv:Body>
>
> </soapenv:Envelope>
>
>
>
>
>
> Response
>
>
>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> <soapenv:Header>
>
>
> <wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action>
>
>
> <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
>
>
> <wsa:MessageID>uuid:2C42C087-011B-4000-E000-0DE00AE35A2E</wsa:MessageID>
>
>
> <wsa:RelatesTo>uuid:feacfe40-5342-11dd-bfe3-cce87efa941f</wsa:RelatesTo>
>
> </soapenv:Header>
>
> <soapenv:Body>
>
> <soapenv:Fault>
>
> <faultcode>soapenv:Server.generalException</faultcode>
>
> <faultstring>java.rmi.RemoteException: WS IBM-KANDULA Interoper
> FailedSimulated abort</faultstring>
>
> </soapenv:Fault>
>
> </soapenv:Body>
>
> </soapenv:Envelope>
>
>
>
> As suggested by Dasarath, the transaction management should work now but it's
> not.
>
> I am not sure where I am going wrong.
>
>
>
> Thanks.
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
> From: Pal Chaudhuri, Anshuk (Cognizant)
> Sent: Wednesday, July 16, 2008 4:03 PM
> To: 'kandula-dev@ws.apache.org'
> Cc: 'Dasarath Weeratunge'
> Subject: RE: Issues while compiling src code
>
>
>
> Hi,
>
>
>
> Thought the following might work:
>
>
>
> public void invoke() throws RemoteException,
> ServiceException
>
> {
>
> DBUpdateService db = new
> DBUpdateServiceLocator();
>
> DBUpdate invoke = db.getDBUpdate();
>
> TransactionManagerImpl tm =
> TransactionManagerImpl.getInstance();
>
> tm.begin();
>
> try
>
> {
>
>
> invoke.insertTestOne(616,"cts");
>
> }
>
> catch (Exception e) {
>
>
> tm.rollback();
>
> }
>
> tm.commit();
>
>
>
> }
>
>
>
> But there is a null pointer exception for the tm.rollback
>
>
>
> java.lang.NullPointerException
>
> at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>
> at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>
> at
>
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>
> at
>
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
>
> at
>
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
>
> at
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
>
> at
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
>
> at
>
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
>
> at
>
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
>
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
>
> at
>
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
>
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
>
> at
>
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>
> at
> org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>
> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>
> at
> org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:796)
>
> at
> org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
>
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
>
> at
> org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
>
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>
> at org.apache.axis.client.Call.invoke(Call.java:2767)
>
> at org.apache.axis.client.Call.invoke(Call.java:2443)
>
> at org.apache.axis.client.Call.invoke(Call.java:2366)
>
> at org.apache.axis.client.Call.invoke(Call.java:1812)
>
> at
>
org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub.registerOperation(RegistrationPortTypeRPCBindingStub.java:290)
>
> at
>
org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:53)
>
> at
>
org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
>
> at
>
org.apache.kandula.coordinator.at.TransactionImpl.register(TransactionImpl.java:68)
>
> at
>
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:136)
>
> at
>
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
>
> at com.cts.db.ws.insert.Client.invoke(Client.java:62)
>
> at com.cts.db.ws.insert.Client.main(Client.java:48)
>
>
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
> From: Pal Chaudhuri, Anshuk (Cognizant)
> Sent: Wednesday, July 16, 2008 2:31 PM
> To: kandula-dev@ws.apache.org
> Cc: 'Dasarath Weeratunge'
> Subject: RE: Issues while compiling src code
>
>
>
> Hi,
>
>
>
> As you suggested, I tried the following
>
>
>
> public void invoke()
>
> {
>
> TransactionManagerImpl tm =
> TransactionManagerImpl.getInstance();
>
> try {
>
> tm.begin();
>
> DBUpdateService db = new
> DBUpdateServiceLocator(); // using the stubs generated from the web service
>
> DBUpdate invoke =
> db.getDBUpdate(); // using the stubs generated from the web service
>
>
> invoke.insertTestOne(1,"anshuk"); // using the stubs generated from the web
> service
>
> tm.commit();
>
> }
>
> catch (Exception e) {
>
> e.printStackTrace();
>
> }
>
> }
>
>
>
> But this is not revoking the inserted records from the database; When I
> checked the soap request in the tcpmon, the coordination context is not in
> the soap header of the request. Do I need to add any configuration or
> anything else?
>
>
>
> Thanks.
>
>
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
> -----Original Message-----
> From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> Sent: Tuesday, July 15, 2008 7:44 PM
> To: kandula-dev@ws.apache.org
> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> Subject: RE: Issues while compiling src code
>
>
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
>
>
> I don't understand why you have your own client level handler to
>
> create a coordination context and then add it to out going messages!
>
> Kandula already provides that mechanism and much more.
>
>
>
> Just deploy Kandula in Axis according to the user guide and then
>
> using a standalone client + the toy TM, invoke your WAS service inside a
>
> transaction: toyTm.begin(); foo.invokeWASService(); toyTm.commit();
>
>
>
> Since you are using a standalone client and Kandula only supports
> asynchornous
>
> port types, tm.commit will not function properly. However, if you try this
>
> inside a container like Axis, things will work as expected.
>
>
>
> Thanks,
>
> -- dasarath
>
>
>
>
>
> > Hi,
>
> >
>
> >
>
>
>
> >
>
> > Agreed.
>
> >
>
> >
>
>
>
> >
>
> > Let's go step by step.
>
> >
>
> >
>
>
>
> >
>
> > I am using the Kandula activation service. The coordination context is
> being
>
> > created. The coordination context is also being embedded in the soap
> envelope
>
> > and the web service operation is then invoked.
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > I am using a client level handler which invokes the Kandula activation
>
> > service and creates the context and puts the coordination context in the
> soap
>
> > header. (similar to what is done in the TM begin() method)
>
> >
>
> >
>
>
>
> >
>
> > The client handler has the invoke method which does the same.
>
> >
>
> >
>
>
>
> >
>
> > public void invoke(MessageContext mc) throws AxisFault
>
>
>
> >
>
> > {
>
> >
>
> > System.out.println("handler");
>
> >
>
> > CoordinationContext ctx;
>
> >
>
> > CoordinationContextType ctxType;
>
> >
>
> > try {
>
> >
>
> > ActivationStub stub = new
>
> > ActivationStub(new EndpointReference(
>
> >
>
> >
>
> > "http://localhost:1234/axis/services/activationCoordinator"));
>
> >
>
> > ctx =
>
> > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> >
>
> >
>
>
>
> >
>
> > SOAPHeader header =
>
> > mc.getCurrentMessage().getSOAPEnvelope().getHeader();
>
> >
>
> >
>
> > ctx.toSOAPHeaderElement(header);
>
> >
>
> > }catch (Exception re) {
>
> >
>
> > try {
>
> >
>
> > ctx =
> null;
>
> >
>
> > } catch
>
> > (Exception e) {
>
> >
>
> >
>
>
> > e.printStackTrace();
>
> >
>
> >
>
>
> > }
>
> >
>
> > }
>
> >
>
> > }
>
> >
>
> >
>
>
>
> >
>
> > (1234 is the tcpmon port monitor directed to 8080 @
>
> > axis/services/activationCoordinator)
>
> >
>
> >
>
>
>
> >
>
> > The coordination context which is being in the soap request header while
>
> > invoking the web service operation is:
>
> >
>
> >
>
>
>
> >
>
> > <wscoor:CoordinationContext
>
> > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
>
> > soapenv:mustUnderstand="0"
>
> > xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
>
> >
>
> >
>
> >
> <wscoor:Identifier>uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</wscoor:Identifier>
>
> >
>
> >
>
> >
>
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
>
> >
>
> > <wscoor:RegistrationService>
>
> >
>
> > <wsa:Address
>
> >
>
>
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
>
> >
>
> > <wsa:ReferenceProperties
>
> > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> >
>
> > <ns4:CallbackRef
>
> >
>
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</ns4:CallbackRef>
>
> >
>
> > </wsa:ReferenceProperties>
>
> >
>
> > </wscoor:RegistrationService>
>
> >
>
> > </wscoor:CoordinationContext>
>
> >
>
> >
>
>
>
> >
>
> > Now after this is done, you suggested that the WAS should register the
>
> > Kandula registration service (which would be I suppose
>
> > http://localhost:8080/axis/services/registrationCoordinator) , I am not
>
> > really sure how to achieve this.
>
> >
>
> >
>
>
>
> >
>
> > Any pointers?
>
> >
>
> >
>
>
>
> >
>
> > Thanking you in advance.
>
> >
>
> >
>
>
>
> >
>
> > Regards,
>
> >
>
> > Anshuk Pal Chaudhuri
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > -----Original Message-----
>
> > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
>
>
> > Sent: Monday, July 14, 2008 7:43 PM
>
> > To: kandula-dev@ws.apache.org
>
> > Cc: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Subject: RE: Issues while compiling src code
>
> >
>
> >
>
>
>
> >
>
> > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> >
>
>
>
> >
>
> > You should be able to use either coordinator. To use a different
> coordinator
>
> >
>
> > with the Kandula provided toy TM, you can specify the end point of the
>
> >
>
> > activation service to the begin() method.
>
> >
>
> >
>
>
>
> >
>
> > Note that the coordination context is created by the activation service.
>
> >
>
> > There is another Coordinator service which handles termination. Please
>
> >
>
> > make sure that you are not sending the CreateCoordinationContext message
> to
>
> >
>
> > the coordinator endpoint.
>
> >
>
> >
>
>
>
> >
>
> > If you are using the Kandula activation service, then once the
> coordination
>
> >
>
> > context has been created and the service on WAS is invoked with the
>
> > coordination
>
> >
>
> > context, WAS should register with the Kandula registration service.
>
> >
>
> >
>
>
>
> >
>
> > If you are using WAS activation service, then service on WAS should
> register
>
> >
>
> > with the registration service on WAS.
>
> >
>
> >
>
>
>
> >
>
> > Let me know whether you get this far.
>
> >
>
> >
>
>
>
> >
>
> > Please post your questions on kandula-dev so that they get archived.
>
> >
>
> >
>
>
>
> >
>
> > Thanks,
>
> >
>
> > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > > That is exactly what I am trying to achieve using the Kandula client.
> And
>
> >
>
> > > that's where I am facing the issues L L
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Since I am using a Kandula client, the coordination context should be
>
> > created
>
> >
>
> > > using web service activationCoordinator deployed on tomcat
>
> >
>
> > > àhttp://localhost:8080/axis/services/activationCoordinator, which is
>
> > actually
>
> >
>
> > > being created and also being sent in the soap header in the soap request
>
> >
>
> > > while the web service on WAS. (PFA kandula-soap-request.xml)
>
> >
>
> > >
>
>
>
> >
>
> > > But then again, this transaction details is not working as the revoking
>
> > part
>
> >
>
> > > is not working properly.
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Then I thought may be the coordination service of WAS should be invoked
>
> > which
>
> >
>
> > > lies at http://localhost:9080/_IBMSYSAPP/wsat/services/Coordinator
> (which
>
> >
>
> > > might create the correct coordination context as required like attached
> à
>
> >
>
> > > WAS-Client-SOAP-request.xml ) but the request which is being sent to
>
> > invoke
>
> >
>
> > > the coordinator service is not correct. (PFA the errors.txt)
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > -----Original Message-----
>
> >
>
> > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
> >
>
> >
>
>
>
> >
>
> > > Sent: Friday, July 11, 2008 7:43 PM
>
> >
>
> > > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > > Subject: RE: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Yes, this can be done. You can replace either the WAS box or MSFT box
> with
>
> >
>
> > >
>
>
>
> >
>
> > > Axis+Kandula or add Axis+Kandula as another branch of the same activity
>
> >
>
> > > along
>
> >
>
> > >
>
>
>
> >
>
> > > with the other two.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > If your resource is deployed in WAS then Kandula is only a client.
> Kandula
>
> >
>
> > >
>
>
>
> >
>
> > > will create a coordination context and then attach it to all invocations
>
> >
>
> > >
>
>
>
> >
>
> > > of your service methods on WAS and then finally terminate that
> transaction
>
> >
>
> > >
>
>
>
> >
>
> > > using WS-AT. Of course, we could add other resources to this activity
>
> >
>
> > > possibly
>
> >
>
> > >
>
>
>
> >
>
> > > residing outside of WAS. How your resource is configured and how the web
>
> >
>
> > > service
>
> >
>
> > >
>
>
>
> >
>
> > > is setup in WAS that you have to look at WAS docs. I would recommend
> that
>
> >
>
> > > you
>
> >
>
> > >
>
>
>
> >
>
> > > take the same WSDL of this interop scenario and try to generate a
> Kandula
>
> >
>
> > >
>
>
>
> >
>
> > > client. That way you can follow the same instructions on setting up the
>
> > WAS
>
> >
>
> > > end.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > The other scenario is, WAS acts as the client and resource is deployed
>
> >
>
> > > inside
>
> >
>
> > >
>
>
>
> >
>
> > > Geronimo with Kandula providing the interfacing between WS-AT and JTA.
> You
>
> >
>
> > > can
>
> >
>
> > >
>
>
>
> >
>
> > > even test this with out involving Geronimo by using the toy TM that we
>
> > have
>
> >
>
> > >
>
>
>
> >
>
> > > provided. Since we are only concerned about WS-AT, JTA side is not
>
> >
>
> > > important.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > I have tried inter-op testing Kandula with IBM implementation but had to
>
> >
>
> > > stop
>
> >
>
> > >
>
>
>
> >
>
> > > it due to a bug in their code.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Happy testing!
>
> >
>
> > >
>
>
>
> >
>
> > > -- dasarath
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks Dasarath for the input.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > I am not trying to integrate Kandula with WAS as Kandula is being done
>
> >
>
> > >
>
>
>
> >
>
> > > > today with Geronimo. That is not my objective.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > The objective is:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Web Service Transaction Interoperability (Kandula Implementation and
> WAS
>
> >
>
> > >
>
>
>
> >
>
> > > > Implementation of Web Service Transaction)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Web Service Client (build with axis generated stubs and using Kandula
> to
>
> >
>
> > >
>
>
>
> >
>
> > > > attach transaction details) ----------------------------> Web Service
> on
>
> >
>
> > >
>
>
>
> >
>
> > > > WAS (which does some insertion into database) Do you think this is
>
> >
>
> > >
>
>
>
> >
>
> > > > feasible or not?
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > The resources are defined (say datasource) within the WAS Container.
> Now
>
> >
>
> > >
>
>
>
> >
>
> > > > the question would be do I need to expose these resources (XAResource)
>
> >
>
> > >
>
>
>
> >
>
> > > > deployed within WAS using Kandula?
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > I was having a look somewhere
>
> >
>
> > >
>
>
>
> >
>
> > > >
> (http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
>
> >
>
> > >
>
>
>
> >
>
> > > > o/0707_lo.html ) where there are MS Web Service Clients (Web Service
>
> >
>
> > >
>
>
>
> >
>
> > > > Transactions configured) are interoperating with Web Services deployed
>
> >
>
> > >
>
>
>
> >
>
> > > > on WAS and the transaction management is happening. That is an
> excellent
>
> >
>
> > >
>
>
>
> >
>
> > > > case of web service transaction interoperability. What I am wondering
> is
>
> >
>
> > >
>
>
>
> >
>
> > > > if that is possible, then why not what I am trying out, where the
> client
>
> >
>
> > >
>
>
>
> >
>
> > > > would be using axis (instead of Microsoft) and the transaction
>
> >
>
> > >
>
>
>
> >
>
> > > > configuration would be done using Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Let me know if I am not clear.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > -----Original Message-----
>
> >
>
> > >
>
>
>
> >
>
> > > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Sent: Thursday, July 10, 2008 10:55 PM
>
> >
>
> > >
>
>
>
> >
>
> > > > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > >
>
>
>
> >
>
> > > > Cc: kandula-dev@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > Subject: RE: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Quoting Anshuk <An...@cognizant.com>:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Interfacing JTA with WS-AT is completely different from
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > looking at web services interoperability between different
>
> >
>
> > >
>
>
>
> >
>
> > > > implementations
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
>
> >
>
> > >
>
>
>
> >
>
> > > > this point.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > If you want to expose some XAResource deployed inside WAS using
> Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > then you need to interface Kandula with the native JTA implementation
> in
>
> >
>
> > >
>
>
>
> >
>
> > > > WAS.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > What Kandula does is it creates a JTA transaction whenever it sees a
> new
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > coordination context and attaches it to the thread that would execute
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > the web service. From there on, the native JTA implementation takes
> care
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > of the rest. In the absence of such a native JTA implementation we
> have
>
> >
>
> > >
>
>
>
> >
>
> > > > provided
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > a toy JTA implementation that could be used but this is mainly for
>
> >
>
> > >
>
>
>
> >
>
> > > > testing.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > When the WS-AT protocol attempts to terminate the activity, Kandula
> will
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > use its private interface with the native JTA implementation to
>
> >
>
> > >
>
>
>
> >
>
> > > > terminate
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > the JTA transaction that was created earlier. Here Kandula uses the
>
> >
>
> > >
>
>
>
> >
>
> > > > two-phase
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > commit protocol.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > However, the JTA API is not sufficient to completely handle the two
>
> >
>
> > >
>
>
>
> >
>
> > > > phase
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > commit protocol that is used to terminate a transaction. For example,
> if
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > you look at how Kandula has been interfaced with Geronimo, you would
> see
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > that we have used an API exposed by the Geronimo transaction manager
>
> >
>
> > >
>
>
>
> >
>
> > > > which
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > is non-standard. In the case of WAS it is not possible to study their
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > internal API s to do the same. In short, it is not possible to do what
>
> >
>
> > >
>
>
>
> >
>
> > > > we have
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > done with Geronimo with WAS.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > You could however, try the following:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > 1) Use a Kandula client with WAS server.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > 2) WAS client with Kandula server (in Geronimo server or Tomcat +
>
> >
>
> > >
>
>
>
> >
>
> > > > Geronimo
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > transaction manager)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > -- dasarath
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Thanks Dasarath for the input.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > As I mentioned earlier, I did try out the WAS-WAS and it is working
>
> >
>
> > >
>
>
>
> >
>
> > > > fine. I
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > also tried out the Kandula-Kandula (as you mentioned about the
> banking
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > example)and it is also working fine.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Now w.r.t. the sceanrio which I described earlier, the first case
>
> >
>
> > >
>
>
>
> >
>
> > > > (WAS-WAS),
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > the datasource is defined within the WAS container, so the
> application
>
> >
>
> > >
>
>
>
> >
>
> > > > is
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > taking care of the rollback.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > In the second case, (correct me if I am wrong), the resources are
>
> >
>
> > >
>
>
>
> >
>
> > > > defined in
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > the BankOneDBMS which implements NamedXAResource so the resources
> are
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > enlisted there only and the commit and rollback are managed
> explicitly
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > (using the Transaction Manager of Geronimo)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Now when I am trying to incorporate Kandula (at the client side) and
>
> >
>
> > >
>
>
>
> >
>
> > > > WAS (at
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > the server side, where the web service is deployed), the transaction
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > management is not taking place as expected.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > The co-ordination context (within the soap request) that I have sent
>
> >
>
> > >
>
>
>
> >
>
> > > > across
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > from WAS (when client) and Kandula (when client) seems to be
>
> >
>
> > >
>
>
>
> >
>
> > > > different.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > In case of kandula (being client), the standalone client uses the
>
> >
>
> > >
>
>
>
> >
>
> > > > stubs
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > (generated from axis wsdl2java) and a client handler does the
>
> >
>
> > >
>
>
>
> >
>
> > > > following:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > public void invoke(MessageContext mc) throws AxisFault {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > System.out.println("handler");
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > CoordinationContext ctx;
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > CoordinationContextType ctxType;
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > ActivationStub stub =
> new
>
> >
>
> > >
>
>
>
> >
>
> > > > ActivationStub(new EndpointReference(
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > > > "http://localhost:8081/axis/services/activationCoordinator"));
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > ctx =
>
> >
>
> > >
>
>
>
> >
>
> > > > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > }catch (Exception re) {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > ctx =
>
> >
>
> > >
>
>
>
> >
>
> > > > null;
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > } catch
>
> >
>
> > >
>
>
>
> >
>
> > > > (Exception e) {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > > > e.printStackTrace();
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > I am not sure where I am going wrong.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Can you guide me on this.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Thanks.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Anshuk
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Dasarath Weeratunge-3 wrote:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > Have you looked at the banking example? If you are going to
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > use WAS on one end and Kandula on the other end I would very much
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > like to see what the result is going to be. I would recommend
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > that you first try WAS-WAS and Kandula-Kandula before attempting
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > WAS-Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > >
>
>
>
> >
>
> > > > what
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > This is unfortunately a little too gernal to answer over a mailing
>
> >
>
> > >
>
>
>
> >
>
> > > > list.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > Please be more specific/discrete about what you are trying to do.
>
> >
>
> > >
>
>
>
> >
>
> > > > For
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > example,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > if you say you tried this and got this error, then we can tell you
>
> >
>
> > >
>
>
>
> >
>
> > > > why and
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > what you need to do differently.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > -- dasarath
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Hi Hannes,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Thanks for your input.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> I did try out using the atomic transaction that comes with the
> IBM
>
> >
>
> > >
>
>
>
> >
>
> > > > WAS
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> 6.0. The web service would insert some values in a database. The
>
> >
>
> > >
>
>
>
> >
>
> > > > web
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> service client was built using the stubs generated by the IBM
> SOAP
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Engine WSDL2Java and configured in such a way so that it would
> send
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> atomic transaction details in the soap envelope. So, I tested a
>
> >
>
> > >
>
>
>
> >
>
> > > > good
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> scenario and the values got inserted in the table. While testing
>
> >
>
> > >
>
>
>
> >
>
> > > > the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> error scenario, in the web service after the part of the which
> does
>
> >
>
> > >
>
>
>
> >
>
> > > > the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> insertion, I threw a runtime exception explicitly and when I
>
> >
>
> > >
>
>
>
> >
>
> > > > checked the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> tables, the values were not inserted.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Now I intend to do a similar scenario using Apache Kandula at the
>
> >
>
> > >
>
>
>
> >
>
> > > > client
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> side. The same web service (deployed on WAS) would be used, but
>
> >
>
> > >
>
>
>
> >
>
> > > > the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> client would now send the soap request using apache Kandula and
> the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> necessary transaction details (within the soap header) would be
>
> >
>
> > >
>
>
>
> >
>
> > > > sent.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > >
>
>
>
> >
>
> > > > what
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Can you help/guide me in testing the above.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Thanking you in advance.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> -----Original Message-----
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> From: Hannes Erven [mailto:herven@apache.org]
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Sent: Sunday, June 29, 2008 4:37 AM
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> To: kandula-dev@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Subject: Re: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Hi Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> > What I am not clear is the flow how exactly the client creates
>
> >
>
> > >
>
>
>
> >
>
> > > > the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> > co-ordination context and so on.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> I'm not sure what you are exactly looking for and what you
> already
>
> >
>
> > >
>
>
>
> >
>
> > > > know
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> or have read.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> As a general starting point, I suggest you have a look at the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> WS-Coordination specification and also WS-AtomicTransaction or
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> WS-BusinessActivity, whatever transaction type you are interested
>
> >
>
> > >
>
>
>
> >
>
> > > > in.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> In the source code, at the Kandula server it all starts at
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > > >
> org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> text
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> , this is where the call from the client is received. From there,
>
> >
>
> > >
>
>
>
> >
>
> > > > the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> actual transaction coordinator object is created depending on the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> requested type of transaction.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> If you have further questions or need reading tips, please reply
>
> >
>
> > >
>
>
>
> >
>
> > > > with
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> more details what you are interested in.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Best regards and thank you for your interest in Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> -hannes
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> This e-mail and any files transmitted with it are for the sole
> use
>
> >
>
> > >
>
>
>
> >
>
> > > > of the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> intended recipient(s) and may contain confidential and privileged
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> information.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> If you are not the intended recipient, please contact the sender
> by
>
> >
>
> > >
>
>
>
> >
>
> > > > reply
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> e-mail and destroy all copies of the original message.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Any unauthorised review, use, disclosure, dissemination,
>
> >
>
> > >
>
>
>
> >
>
> > > > forwarding,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> printing
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> or copying of this email or any action taken in reliance on this
>
> >
>
> > >
>
>
>
> >
>
> > > > e-mail
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> is
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> strictly
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> prohibited and may be unlawful.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > --
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > View this message in context:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > > >
> http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
>
> >
>
> > >
>
>
>
> >
>
> > > > 3.html
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Sent from the Kandula mailing list archive at Nabble.com.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
> ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > This e-mail and any files transmitted with it are for the sole use of
>
> > the
>
> >
>
> > >
>
>
>
> >
>
> > > > intended recipient(s) and may contain confidential and privileged
>
> >
>
> > >
>
>
>
> >
>
> > > > information.
>
> >
>
> > >
>
>
>
> >
>
> > > > If you are not the intended recipient, please contact the sender by
>
> > reply
>
> >
>
> > >
>
>
>
> >
>
> > > > e-mail and destroy all copies of the original message.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Any unauthorised review, use, disclosure, dissemination, forwarding,
>
> >
>
> > > printing
>
> >
>
> > >
>
>
>
> >
>
> > > > or copying of this email or any action taken in reliance on this
> e-mail
>
> > is
>
> >
>
> > >
>
>
>
> >
>
> > > > strictly
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > prohibited and may be unlawful.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > This e-mail and any files transmitted with it are for the sole use of
> the
>
> >
>
> > > intended recipient(s) and may contain confidential and privileged
>
> >
>
> > > information.
>
> >
>
> > > If you are not the intended recipient, please contact the sender by
> reply
>
> >
>
> > > e-mail and destroy all copies of the original message.
>
> >
>
> >
>
>
>
> >
>
> > > Any unauthorised review, use, disclosure, dissemination, forwarding,
>
> > printing
>
> >
>
> > > or copying of this email or any action taken in reliance on this e-mail
> is
>
> >
>
> > > strictly
>
> >
>
> >
>
>
>
> >
>
> > > prohibited and may be unlawful.
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
> >
>
> > This e-mail and any files transmitted with it are for the sole use of the
>
> > intended recipient(s) and may contain confidential and privileged
>
> > information.
>
> > If you are not the intended recipient, please contact the sender by reply
>
> > e-mail and destroy all copies of the original message.
>
>
>
> > Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing
>
> > or copying of this email or any action taken in reliance on this e-mail is
>
> > strictly
>
>
>
> > prohibited and may be unlawful.
>
>
>
>
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing
> or copying of this email or any action taken in reliance on this e-mail is
> strictly
> prohibited and may be unlawful.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Anshuk.PalChaudhuri@cognizant.com:
If the coordination context is not been included in the message, then
that means the transaction handler is not deployed properly. Most of the
time this is due to some problem in your .wsdd file.
Since the database (the resource) is inside the WAS box, the onus of
removing the database records inserted falls on WAS. Kandula responsibility
is to inform the rollback of the transaction to WAS /Coordinator endpoint.
Once you call tm.rollback on the client side, There should be a rollback message
sent from client to WAS box and WAS box should reply with an acknowledgment.
The specific message sequence is there in the WS-AT specification.
Kandula should send the rollback message to the /Coordinator endpoint provided
in the WAS registration request and WAS should send the acknowledgment to the
/Coordinator endpoint provided by Kandula in registration response.
Before you get down to rollback, please check whether the service method that
inserts records is called with a transaction context (JTA). Even if the service
invocation has a coordination context, if the WAS side doesn't recognize it, the
method may not be called with transaction context. If you look at the banking
example, you can see how to print the transaction status.
Thanks,
-- dasarath
> Hi,
>
>
>
> The scenario I have tried to create now is more like a banking example (I
> have created a interopibmkandulaservice similar to bankone test which would
> invoke the actual web service deployed on WAS)
>
>
>
> The coordination context is being attached now but the WAS web service
> (where I have explicitly thrown a remote exception after a db insertion) is
> not doing a rollback of the database values inserted.
>
>
>
> The code for interopibmkandulaservice (operation à testingInterop ) deployed
> on axis on tomcat:
>
>
>
> public void testingInterop() throws RemoteException, ServiceException {
>
> DBUpdateService db = new
> DBUpdateServiceLocator();
>
>
>
> DBUpdate invoke = db.getDBUpdate();
>
> TransactionManagerImpl tm =
> TransactionManagerImpl.getInstance();
>
> try
>
> {
>
> tm.begin();
>
>
> invoke.insertTestOne(621,"anshuk");
>
> tm.commit();
>
> }
>
> catch(RemoteException re)
>
> {
>
> tm.rollback();
>
> }
>
> }
>
>
>
> The SOAP Request and Response for interopibmkandulaservice web service:
>
>
>
> Request
>
>
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>
> <soapenv:Body>
>
> <testingInterop xmlns=""/>
>
> </soapenv:Body>
>
> </soapenv:Envelope>
>
>
>
> Response
>
>
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>
> <soapenv:Body>
>
> <testingInteropResponse xmlns=""/>
>
> </soapenv:Body>
>
> </soapenv:Envelope>
>
>
>
> The SOAP Request and response for the WAS Web Service:
>
>
>
> Request
>
>
>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> <soapenv:Header>
>
> <wsa:MessageID
>
soapenv:mustUnderstand="0">uuid:feacfe40-5342-11dd-bfe3-cce87efa941f</wsa:MessageID>
>
> <wsa:To
>
soapenv:mustUnderstand="0">http://localhost:9082/IBM-KANDULA-INTEROPER-WS/services/DBUpdate</wsa:To>
>
> <wsa:Action
>
soapenv:mustUnderstand="0">http://ws.apache.org/interop/ibm/IBMKandula#insertTestOne</wsa:Action>
>
> <wsa:From soapenv:mustUnderstand="0">
>
>
>
<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
>
> </wsa:From>
>
> <wscoor:CoordinationContext
> soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
> soapenv:mustUnderstand="0"
> xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
>
>
> <wscoor:Identifier>uuid:fe121dd0-5342-11dd-bfe3-cce87efa941f</wscoor:Identifier>
>
>
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
>
> <wscoor:RegistrationService>
>
>
>
<wsa:Address>http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
>
> <wsa:ReferenceProperties>
>
> <ns4:CallbackRef
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:fe121dd0-5342-11dd-bfe3-cce87efa941f</ns4:CallbackRef>
>
> </wsa:ReferenceProperties>
>
> </wscoor:RegistrationService>
>
> </wscoor:CoordinationContext>
>
> </soapenv:Header>
>
> <soapenv:Body>
>
> <insertTestOne xmlns="http://ws.ibm.cts.com">
>
> <testOneId xmlns="">621</testOneId>
>
> <testOneDescription xmlns="">cts</testOneDescription>
>
> </insertTestOne>
>
> </soapenv:Body>
>
> </soapenv:Envelope>
>
>
>
>
>
> Response
>
>
>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> <soapenv:Header>
>
>
> <wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action>
>
>
> <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
>
>
> <wsa:MessageID>uuid:2C42C087-011B-4000-E000-0DE00AE35A2E</wsa:MessageID>
>
>
> <wsa:RelatesTo>uuid:feacfe40-5342-11dd-bfe3-cce87efa941f</wsa:RelatesTo>
>
> </soapenv:Header>
>
> <soapenv:Body>
>
> <soapenv:Fault>
>
> <faultcode>soapenv:Server.generalException</faultcode>
>
> <faultstring>java.rmi.RemoteException: WS IBM-KANDULA Interoper
> FailedSimulated abort</faultstring>
>
> </soapenv:Fault>
>
> </soapenv:Body>
>
> </soapenv:Envelope>
>
>
>
> As suggested by Dasarath, the transaction management should work now but it's
> not.
>
> I am not sure where I am going wrong.
>
>
>
> Thanks.
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
> From: Pal Chaudhuri, Anshuk (Cognizant)
> Sent: Wednesday, July 16, 2008 4:03 PM
> To: 'kandula-dev@ws.apache.org'
> Cc: 'Dasarath Weeratunge'
> Subject: RE: Issues while compiling src code
>
>
>
> Hi,
>
>
>
> Thought the following might work:
>
>
>
> public void invoke() throws RemoteException,
> ServiceException
>
> {
>
> DBUpdateService db = new
> DBUpdateServiceLocator();
>
> DBUpdate invoke = db.getDBUpdate();
>
> TransactionManagerImpl tm =
> TransactionManagerImpl.getInstance();
>
> tm.begin();
>
> try
>
> {
>
>
> invoke.insertTestOne(616,"cts");
>
> }
>
> catch (Exception e) {
>
>
> tm.rollback();
>
> }
>
> tm.commit();
>
>
>
> }
>
>
>
> But there is a null pointer exception for the tm.rollback
>
>
>
> java.lang.NullPointerException
>
> at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>
> at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>
> at
>
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>
> at
>
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
>
> at
>
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
>
> at
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
>
> at
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
>
> at
>
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
>
> at
>
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
>
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
>
> at
>
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
>
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
>
> at
>
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>
> at
> org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>
> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>
> at
> org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:796)
>
> at
> org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
>
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
>
> at
> org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
>
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>
> at org.apache.axis.client.Call.invoke(Call.java:2767)
>
> at org.apache.axis.client.Call.invoke(Call.java:2443)
>
> at org.apache.axis.client.Call.invoke(Call.java:2366)
>
> at org.apache.axis.client.Call.invoke(Call.java:1812)
>
> at
>
org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub.registerOperation(RegistrationPortTypeRPCBindingStub.java:290)
>
> at
>
org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:53)
>
> at
>
org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
>
> at
>
org.apache.kandula.coordinator.at.TransactionImpl.register(TransactionImpl.java:68)
>
> at
>
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:136)
>
> at
>
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
>
> at com.cts.db.ws.insert.Client.invoke(Client.java:62)
>
> at com.cts.db.ws.insert.Client.main(Client.java:48)
>
>
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
> From: Pal Chaudhuri, Anshuk (Cognizant)
> Sent: Wednesday, July 16, 2008 2:31 PM
> To: kandula-dev@ws.apache.org
> Cc: 'Dasarath Weeratunge'
> Subject: RE: Issues while compiling src code
>
>
>
> Hi,
>
>
>
> As you suggested, I tried the following
>
>
>
> public void invoke()
>
> {
>
> TransactionManagerImpl tm =
> TransactionManagerImpl.getInstance();
>
> try {
>
> tm.begin();
>
> DBUpdateService db = new
> DBUpdateServiceLocator(); // using the stubs generated from the web service
>
> DBUpdate invoke =
> db.getDBUpdate(); // using the stubs generated from the web service
>
>
> invoke.insertTestOne(1,"anshuk"); // using the stubs generated from the web
> service
>
> tm.commit();
>
> }
>
> catch (Exception e) {
>
> e.printStackTrace();
>
> }
>
> }
>
>
>
> But this is not revoking the inserted records from the database; When I
> checked the soap request in the tcpmon, the coordination context is not in
> the soap header of the request. Do I need to add any configuration or
> anything else?
>
>
>
> Thanks.
>
>
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
> -----Original Message-----
> From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> Sent: Tuesday, July 15, 2008 7:44 PM
> To: kandula-dev@ws.apache.org
> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> Subject: RE: Issues while compiling src code
>
>
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
>
>
> I don't understand why you have your own client level handler to
>
> create a coordination context and then add it to out going messages!
>
> Kandula already provides that mechanism and much more.
>
>
>
> Just deploy Kandula in Axis according to the user guide and then
>
> using a standalone client + the toy TM, invoke your WAS service inside a
>
> transaction: toyTm.begin(); foo.invokeWASService(); toyTm.commit();
>
>
>
> Since you are using a standalone client and Kandula only supports
> asynchornous
>
> port types, tm.commit will not function properly. However, if you try this
>
> inside a container like Axis, things will work as expected.
>
>
>
> Thanks,
>
> -- dasarath
>
>
>
>
>
> > Hi,
>
> >
>
> >
>
>
>
> >
>
> > Agreed.
>
> >
>
> >
>
>
>
> >
>
> > Let's go step by step.
>
> >
>
> >
>
>
>
> >
>
> > I am using the Kandula activation service. The coordination context is
> being
>
> > created. The coordination context is also being embedded in the soap
> envelope
>
> > and the web service operation is then invoked.
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > I am using a client level handler which invokes the Kandula activation
>
> > service and creates the context and puts the coordination context in the
> soap
>
> > header. (similar to what is done in the TM begin() method)
>
> >
>
> >
>
>
>
> >
>
> > The client handler has the invoke method which does the same.
>
> >
>
> >
>
>
>
> >
>
> > public void invoke(MessageContext mc) throws AxisFault
>
>
>
> >
>
> > {
>
> >
>
> > System.out.println("handler");
>
> >
>
> > CoordinationContext ctx;
>
> >
>
> > CoordinationContextType ctxType;
>
> >
>
> > try {
>
> >
>
> > ActivationStub stub = new
>
> > ActivationStub(new EndpointReference(
>
> >
>
> >
>
> > "http://localhost:1234/axis/services/activationCoordinator"));
>
> >
>
> > ctx =
>
> > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> >
>
> >
>
>
>
> >
>
> > SOAPHeader header =
>
> > mc.getCurrentMessage().getSOAPEnvelope().getHeader();
>
> >
>
> >
>
> > ctx.toSOAPHeaderElement(header);
>
> >
>
> > }catch (Exception re) {
>
> >
>
> > try {
>
> >
>
> > ctx =
> null;
>
> >
>
> > } catch
>
> > (Exception e) {
>
> >
>
> >
>
>
> > e.printStackTrace();
>
> >
>
> >
>
>
> > }
>
> >
>
> > }
>
> >
>
> > }
>
> >
>
> >
>
>
>
> >
>
> > (1234 is the tcpmon port monitor directed to 8080 @
>
> > axis/services/activationCoordinator)
>
> >
>
> >
>
>
>
> >
>
> > The coordination context which is being in the soap request header while
>
> > invoking the web service operation is:
>
> >
>
> >
>
>
>
> >
>
> > <wscoor:CoordinationContext
>
> > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
>
> > soapenv:mustUnderstand="0"
>
> > xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
>
> >
>
> >
>
> >
> <wscoor:Identifier>uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</wscoor:Identifier>
>
> >
>
> >
>
> >
>
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
>
> >
>
> > <wscoor:RegistrationService>
>
> >
>
> > <wsa:Address
>
> >
>
>
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
>
> >
>
> > <wsa:ReferenceProperties
>
> > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> >
>
> > <ns4:CallbackRef
>
> >
>
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</ns4:CallbackRef>
>
> >
>
> > </wsa:ReferenceProperties>
>
> >
>
> > </wscoor:RegistrationService>
>
> >
>
> > </wscoor:CoordinationContext>
>
> >
>
> >
>
>
>
> >
>
> > Now after this is done, you suggested that the WAS should register the
>
> > Kandula registration service (which would be I suppose
>
> > http://localhost:8080/axis/services/registrationCoordinator) , I am not
>
> > really sure how to achieve this.
>
> >
>
> >
>
>
>
> >
>
> > Any pointers?
>
> >
>
> >
>
>
>
> >
>
> > Thanking you in advance.
>
> >
>
> >
>
>
>
> >
>
> > Regards,
>
> >
>
> > Anshuk Pal Chaudhuri
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > -----Original Message-----
>
> > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
>
>
> > Sent: Monday, July 14, 2008 7:43 PM
>
> > To: kandula-dev@ws.apache.org
>
> > Cc: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Subject: RE: Issues while compiling src code
>
> >
>
> >
>
>
>
> >
>
> > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> >
>
>
>
> >
>
> > You should be able to use either coordinator. To use a different
> coordinator
>
> >
>
> > with the Kandula provided toy TM, you can specify the end point of the
>
> >
>
> > activation service to the begin() method.
>
> >
>
> >
>
>
>
> >
>
> > Note that the coordination context is created by the activation service.
>
> >
>
> > There is another Coordinator service which handles termination. Please
>
> >
>
> > make sure that you are not sending the CreateCoordinationContext message
> to
>
> >
>
> > the coordinator endpoint.
>
> >
>
> >
>
>
>
> >
>
> > If you are using the Kandula activation service, then once the
> coordination
>
> >
>
> > context has been created and the service on WAS is invoked with the
>
> > coordination
>
> >
>
> > context, WAS should register with the Kandula registration service.
>
> >
>
> >
>
>
>
> >
>
> > If you are using WAS activation service, then service on WAS should
> register
>
> >
>
> > with the registration service on WAS.
>
> >
>
> >
>
>
>
> >
>
> > Let me know whether you get this far.
>
> >
>
> >
>
>
>
> >
>
> > Please post your questions on kandula-dev so that they get archived.
>
> >
>
> >
>
>
>
> >
>
> > Thanks,
>
> >
>
> > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > > That is exactly what I am trying to achieve using the Kandula client.
> And
>
> >
>
> > > that's where I am facing the issues L L
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Since I am using a Kandula client, the coordination context should be
>
> > created
>
> >
>
> > > using web service activationCoordinator deployed on tomcat
>
> >
>
> > > àhttp://localhost:8080/axis/services/activationCoordinator, which is
>
> > actually
>
> >
>
> > > being created and also being sent in the soap header in the soap request
>
> >
>
> > > while the web service on WAS. (PFA kandula-soap-request.xml)
>
> >
>
> > >
>
>
>
> >
>
> > > But then again, this transaction details is not working as the revoking
>
> > part
>
> >
>
> > > is not working properly.
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Then I thought may be the coordination service of WAS should be invoked
>
> > which
>
> >
>
> > > lies at http://localhost:9080/_IBMSYSAPP/wsat/services/Coordinator
> (which
>
> >
>
> > > might create the correct coordination context as required like attached
> à
>
> >
>
> > > WAS-Client-SOAP-request.xml ) but the request which is being sent to
>
> > invoke
>
> >
>
> > > the coordinator service is not correct. (PFA the errors.txt)
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > -----Original Message-----
>
> >
>
> > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
> >
>
> >
>
>
>
> >
>
> > > Sent: Friday, July 11, 2008 7:43 PM
>
> >
>
> > > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > > Subject: RE: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Yes, this can be done. You can replace either the WAS box or MSFT box
> with
>
> >
>
> > >
>
>
>
> >
>
> > > Axis+Kandula or add Axis+Kandula as another branch of the same activity
>
> >
>
> > > along
>
> >
>
> > >
>
>
>
> >
>
> > > with the other two.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > If your resource is deployed in WAS then Kandula is only a client.
> Kandula
>
> >
>
> > >
>
>
>
> >
>
> > > will create a coordination context and then attach it to all invocations
>
> >
>
> > >
>
>
>
> >
>
> > > of your service methods on WAS and then finally terminate that
> transaction
>
> >
>
> > >
>
>
>
> >
>
> > > using WS-AT. Of course, we could add other resources to this activity
>
> >
>
> > > possibly
>
> >
>
> > >
>
>
>
> >
>
> > > residing outside of WAS. How your resource is configured and how the web
>
> >
>
> > > service
>
> >
>
> > >
>
>
>
> >
>
> > > is setup in WAS that you have to look at WAS docs. I would recommend
> that
>
> >
>
> > > you
>
> >
>
> > >
>
>
>
> >
>
> > > take the same WSDL of this interop scenario and try to generate a
> Kandula
>
> >
>
> > >
>
>
>
> >
>
> > > client. That way you can follow the same instructions on setting up the
>
> > WAS
>
> >
>
> > > end.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > The other scenario is, WAS acts as the client and resource is deployed
>
> >
>
> > > inside
>
> >
>
> > >
>
>
>
> >
>
> > > Geronimo with Kandula providing the interfacing between WS-AT and JTA.
> You
>
> >
>
> > > can
>
> >
>
> > >
>
>
>
> >
>
> > > even test this with out involving Geronimo by using the toy TM that we
>
> > have
>
> >
>
> > >
>
>
>
> >
>
> > > provided. Since we are only concerned about WS-AT, JTA side is not
>
> >
>
> > > important.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > I have tried inter-op testing Kandula with IBM implementation but had to
>
> >
>
> > > stop
>
> >
>
> > >
>
>
>
> >
>
> > > it due to a bug in their code.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Happy testing!
>
> >
>
> > >
>
>
>
> >
>
> > > -- dasarath
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks Dasarath for the input.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > I am not trying to integrate Kandula with WAS as Kandula is being done
>
> >
>
> > >
>
>
>
> >
>
> > > > today with Geronimo. That is not my objective.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > The objective is:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Web Service Transaction Interoperability (Kandula Implementation and
> WAS
>
> >
>
> > >
>
>
>
> >
>
> > > > Implementation of Web Service Transaction)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Web Service Client (build with axis generated stubs and using Kandula
> to
>
> >
>
> > >
>
>
>
> >
>
> > > > attach transaction details) ----------------------------> Web Service
> on
>
> >
>
> > >
>
>
>
> >
>
> > > > WAS (which does some insertion into database) Do you think this is
>
> >
>
> > >
>
>
>
> >
>
> > > > feasible or not?
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > The resources are defined (say datasource) within the WAS Container.
> Now
>
> >
>
> > >
>
>
>
> >
>
> > > > the question would be do I need to expose these resources (XAResource)
>
> >
>
> > >
>
>
>
> >
>
> > > > deployed within WAS using Kandula?
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > I was having a look somewhere
>
> >
>
> > >
>
>
>
> >
>
> > > >
> (http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
>
> >
>
> > >
>
>
>
> >
>
> > > > o/0707_lo.html ) where there are MS Web Service Clients (Web Service
>
> >
>
> > >
>
>
>
> >
>
> > > > Transactions configured) are interoperating with Web Services deployed
>
> >
>
> > >
>
>
>
> >
>
> > > > on WAS and the transaction management is happening. That is an
> excellent
>
> >
>
> > >
>
>
>
> >
>
> > > > case of web service transaction interoperability. What I am wondering
> is
>
> >
>
> > >
>
>
>
> >
>
> > > > if that is possible, then why not what I am trying out, where the
> client
>
> >
>
> > >
>
>
>
> >
>
> > > > would be using axis (instead of Microsoft) and the transaction
>
> >
>
> > >
>
>
>
> >
>
> > > > configuration would be done using Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Let me know if I am not clear.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > -----Original Message-----
>
> >
>
> > >
>
>
>
> >
>
> > > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Sent: Thursday, July 10, 2008 10:55 PM
>
> >
>
> > >
>
>
>
> >
>
> > > > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > >
>
>
>
> >
>
> > > > Cc: kandula-dev@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > Subject: RE: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Quoting Anshuk <An...@cognizant.com>:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Interfacing JTA with WS-AT is completely different from
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > looking at web services interoperability between different
>
> >
>
> > >
>
>
>
> >
>
> > > > implementations
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
>
> >
>
> > >
>
>
>
> >
>
> > > > this point.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > If you want to expose some XAResource deployed inside WAS using
> Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > then you need to interface Kandula with the native JTA implementation
> in
>
> >
>
> > >
>
>
>
> >
>
> > > > WAS.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > What Kandula does is it creates a JTA transaction whenever it sees a
> new
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > coordination context and attaches it to the thread that would execute
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > the web service. From there on, the native JTA implementation takes
> care
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > of the rest. In the absence of such a native JTA implementation we
> have
>
> >
>
> > >
>
>
>
> >
>
> > > > provided
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > a toy JTA implementation that could be used but this is mainly for
>
> >
>
> > >
>
>
>
> >
>
> > > > testing.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > When the WS-AT protocol attempts to terminate the activity, Kandula
> will
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > use its private interface with the native JTA implementation to
>
> >
>
> > >
>
>
>
> >
>
> > > > terminate
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > the JTA transaction that was created earlier. Here Kandula uses the
>
> >
>
> > >
>
>
>
> >
>
> > > > two-phase
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > commit protocol.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > However, the JTA API is not sufficient to completely handle the two
>
> >
>
> > >
>
>
>
> >
>
> > > > phase
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > commit protocol that is used to terminate a transaction. For example,
> if
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > you look at how Kandula has been interfaced with Geronimo, you would
> see
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > that we have used an API exposed by the Geronimo transaction manager
>
> >
>
> > >
>
>
>
> >
>
> > > > which
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > is non-standard. In the case of WAS it is not possible to study their
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > internal API s to do the same. In short, it is not possible to do what
>
> >
>
> > >
>
>
>
> >
>
> > > > we have
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > done with Geronimo with WAS.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > You could however, try the following:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > 1) Use a Kandula client with WAS server.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > 2) WAS client with Kandula server (in Geronimo server or Tomcat +
>
> >
>
> > >
>
>
>
> >
>
> > > > Geronimo
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > transaction manager)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > -- dasarath
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Thanks Dasarath for the input.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > As I mentioned earlier, I did try out the WAS-WAS and it is working
>
> >
>
> > >
>
>
>
> >
>
> > > > fine. I
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > also tried out the Kandula-Kandula (as you mentioned about the
> banking
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > example)and it is also working fine.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Now w.r.t. the sceanrio which I described earlier, the first case
>
> >
>
> > >
>
>
>
> >
>
> > > > (WAS-WAS),
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > the datasource is defined within the WAS container, so the
> application
>
> >
>
> > >
>
>
>
> >
>
> > > > is
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > taking care of the rollback.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > In the second case, (correct me if I am wrong), the resources are
>
> >
>
> > >
>
>
>
> >
>
> > > > defined in
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > the BankOneDBMS which implements NamedXAResource so the resources
> are
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > enlisted there only and the commit and rollback are managed
> explicitly
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > (using the Transaction Manager of Geronimo)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Now when I am trying to incorporate Kandula (at the client side) and
>
> >
>
> > >
>
>
>
> >
>
> > > > WAS (at
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > the server side, where the web service is deployed), the transaction
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > management is not taking place as expected.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > The co-ordination context (within the soap request) that I have sent
>
> >
>
> > >
>
>
>
> >
>
> > > > across
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > from WAS (when client) and Kandula (when client) seems to be
>
> >
>
> > >
>
>
>
> >
>
> > > > different.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > In case of kandula (being client), the standalone client uses the
>
> >
>
> > >
>
>
>
> >
>
> > > > stubs
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > (generated from axis wsdl2java) and a client handler does the
>
> >
>
> > >
>
>
>
> >
>
> > > > following:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > public void invoke(MessageContext mc) throws AxisFault {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > System.out.println("handler");
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > CoordinationContext ctx;
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > CoordinationContextType ctxType;
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > ActivationStub stub =
> new
>
> >
>
> > >
>
>
>
> >
>
> > > > ActivationStub(new EndpointReference(
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > > > "http://localhost:8081/axis/services/activationCoordinator"));
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > ctx =
>
> >
>
> > >
>
>
>
> >
>
> > > > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > }catch (Exception re) {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > ctx =
>
> >
>
> > >
>
>
>
> >
>
> > > > null;
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > } catch
>
> >
>
> > >
>
>
>
> >
>
> > > > (Exception e) {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > > > e.printStackTrace();
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > I am not sure where I am going wrong.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Can you guide me on this.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Thanks.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Anshuk
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Dasarath Weeratunge-3 wrote:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > Have you looked at the banking example? If you are going to
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > use WAS on one end and Kandula on the other end I would very much
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > like to see what the result is going to be. I would recommend
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > that you first try WAS-WAS and Kandula-Kandula before attempting
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > WAS-Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > >
>
>
>
> >
>
> > > > what
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > This is unfortunately a little too gernal to answer over a mailing
>
> >
>
> > >
>
>
>
> >
>
> > > > list.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > Please be more specific/discrete about what you are trying to do.
>
> >
>
> > >
>
>
>
> >
>
> > > > For
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > example,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > if you say you tried this and got this error, then we can tell you
>
> >
>
> > >
>
>
>
> >
>
> > > > why and
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > what you need to do differently.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > -- dasarath
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Hi Hannes,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Thanks for your input.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> I did try out using the atomic transaction that comes with the
> IBM
>
> >
>
> > >
>
>
>
> >
>
> > > > WAS
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> 6.0. The web service would insert some values in a database. The
>
> >
>
> > >
>
>
>
> >
>
> > > > web
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> service client was built using the stubs generated by the IBM
> SOAP
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Engine WSDL2Java and configured in such a way so that it would
> send
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> atomic transaction details in the soap envelope. So, I tested a
>
> >
>
> > >
>
>
>
> >
>
> > > > good
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> scenario and the values got inserted in the table. While testing
>
> >
>
> > >
>
>
>
> >
>
> > > > the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> error scenario, in the web service after the part of the which
> does
>
> >
>
> > >
>
>
>
> >
>
> > > > the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> insertion, I threw a runtime exception explicitly and when I
>
> >
>
> > >
>
>
>
> >
>
> > > > checked the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> tables, the values were not inserted.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Now I intend to do a similar scenario using Apache Kandula at the
>
> >
>
> > >
>
>
>
> >
>
> > > > client
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> side. The same web service (deployed on WAS) would be used, but
>
> >
>
> > >
>
>
>
> >
>
> > > > the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> client would now send the soap request using apache Kandula and
> the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> necessary transaction details (within the soap header) would be
>
> >
>
> > >
>
>
>
> >
>
> > > > sent.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > >
>
>
>
> >
>
> > > > what
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Can you help/guide me in testing the above.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Thanking you in advance.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> -----Original Message-----
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> From: Hannes Erven [mailto:herven@apache.org]
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Sent: Sunday, June 29, 2008 4:37 AM
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> To: kandula-dev@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Subject: Re: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Hi Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> > What I am not clear is the flow how exactly the client creates
>
> >
>
> > >
>
>
>
> >
>
> > > > the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> > co-ordination context and so on.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> I'm not sure what you are exactly looking for and what you
> already
>
> >
>
> > >
>
>
>
> >
>
> > > > know
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> or have read.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> As a general starting point, I suggest you have a look at the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> WS-Coordination specification and also WS-AtomicTransaction or
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> WS-BusinessActivity, whatever transaction type you are interested
>
> >
>
> > >
>
>
>
> >
>
> > > > in.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> In the source code, at the Kandula server it all starts at
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > > >
> org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> text
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> , this is where the call from the client is received. From there,
>
> >
>
> > >
>
>
>
> >
>
> > > > the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> actual transaction coordinator object is created depending on the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> requested type of transaction.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> If you have further questions or need reading tips, please reply
>
> >
>
> > >
>
>
>
> >
>
> > > > with
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> more details what you are interested in.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Best regards and thank you for your interest in Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> -hannes
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> This e-mail and any files transmitted with it are for the sole
> use
>
> >
>
> > >
>
>
>
> >
>
> > > > of the
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> intended recipient(s) and may contain confidential and privileged
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> information.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> If you are not the intended recipient, please contact the sender
> by
>
> >
>
> > >
>
>
>
> >
>
> > > > reply
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> e-mail and destroy all copies of the original message.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> Any unauthorised review, use, disclosure, dissemination,
>
> >
>
> > >
>
>
>
> >
>
> > > > forwarding,
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> printing
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> or copying of this email or any action taken in reliance on this
>
> >
>
> > >
>
>
>
> >
>
> > > > e-mail
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> is
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> strictly
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> prohibited and may be unlawful.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > --
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > View this message in context:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > > >
> http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
>
> >
>
> > >
>
>
>
> >
>
> > > > 3.html
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Sent from the Kandula mailing list archive at Nabble.com.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
> ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > This e-mail and any files transmitted with it are for the sole use of
>
> > the
>
> >
>
> > >
>
>
>
> >
>
> > > > intended recipient(s) and may contain confidential and privileged
>
> >
>
> > >
>
>
>
> >
>
> > > > information.
>
> >
>
> > >
>
>
>
> >
>
> > > > If you are not the intended recipient, please contact the sender by
>
> > reply
>
> >
>
> > >
>
>
>
> >
>
> > > > e-mail and destroy all copies of the original message.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Any unauthorised review, use, disclosure, dissemination, forwarding,
>
> >
>
> > > printing
>
> >
>
> > >
>
>
>
> >
>
> > > > or copying of this email or any action taken in reliance on this
> e-mail
>
> > is
>
> >
>
> > >
>
>
>
> >
>
> > > > strictly
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > prohibited and may be unlawful.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > This e-mail and any files transmitted with it are for the sole use of
> the
>
> >
>
> > > intended recipient(s) and may contain confidential and privileged
>
> >
>
> > > information.
>
> >
>
> > > If you are not the intended recipient, please contact the sender by
> reply
>
> >
>
> > > e-mail and destroy all copies of the original message.
>
> >
>
> >
>
>
>
> >
>
> > > Any unauthorised review, use, disclosure, dissemination, forwarding,
>
> > printing
>
> >
>
> > > or copying of this email or any action taken in reliance on this e-mail
> is
>
> >
>
> > > strictly
>
> >
>
> >
>
>
>
> >
>
> > > prohibited and may be unlawful.
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
> >
>
> > This e-mail and any files transmitted with it are for the sole use of the
>
> > intended recipient(s) and may contain confidential and privileged
>
> > information.
>
> > If you are not the intended recipient, please contact the sender by reply
>
> > e-mail and destroy all copies of the original message.
>
>
>
> > Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing
>
> > or copying of this email or any action taken in reliance on this e-mail is
>
> > strictly
>
>
>
> > prohibited and may be unlawful.
>
>
>
>
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing
> or copying of this email or any action taken in reliance on this e-mail is
> strictly
> prohibited and may be unlawful.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Hi,
The scenario I have tried to create now is more like a banking example (I have created a interopibmkandulaservice similar to bankone test which would invoke the actual web service deployed on WAS)
The coordination context is being attached now but the WAS web service (where I have explicitly thrown a remote exception after a db insertion) is not doing a rollback of the database values inserted.
The code for interopibmkandulaservice (operation à testingInterop ) deployed on axis on tomcat:
public void testingInterop() throws RemoteException, ServiceException {
DBUpdateService db = new DBUpdateServiceLocator();
DBUpdate invoke = db.getDBUpdate();
TransactionManagerImpl tm = TransactionManagerImpl.getInstance();
try
{
tm.begin();
invoke.insertTestOne(621,"anshuk");
tm.commit();
}
catch(RemoteException re)
{
tm.rollback();
}
}
The SOAP Request and Response for interopibmkandulaservice web service:
Request
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<testingInterop xmlns=""/>
</soapenv:Body>
</soapenv:Envelope>
Response
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<testingInteropResponse xmlns=""/>
</soapenv:Body>
</soapenv:Envelope>
The SOAP Request and response for the WAS Web Service:
Request
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<soapenv:Header>
<wsa:MessageID soapenv:mustUnderstand="0">uuid:feacfe40-5342-11dd-bfe3-cce87efa941f</wsa:MessageID>
<wsa:To soapenv:mustUnderstand="0">http://localhost:9082/IBM-KANDULA-INTEROPER-WS/services/DBUpdate</wsa:To>
<wsa:Action soapenv:mustUnderstand="0">http://ws.apache.org/interop/ibm/IBMKandula#insertTestOne</wsa:Action>
<wsa:From soapenv:mustUnderstand="0">
<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
</wsa:From>
<wscoor:CoordinationContext soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
<wscoor:Identifier>uuid:fe121dd0-5342-11dd-bfe3-cce87efa941f</wscoor:Identifier>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
<wscoor:RegistrationService>
<wsa:Address>http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
<wsa:ReferenceProperties>
<ns4:CallbackRef xmlns:ns4="http://ws.apache.org/kandula">uuid:fe121dd0-5342-11dd-bfe3-cce87efa941f</ns4:CallbackRef>
</wsa:ReferenceProperties>
</wscoor:RegistrationService>
</wscoor:CoordinationContext>
</soapenv:Header>
<soapenv:Body>
<insertTestOne xmlns="http://ws.ibm.cts.com">
<testOneId xmlns="">621</testOneId>
<testOneDescription xmlns="">cts</testOneDescription>
</insertTestOne>
</soapenv:Body>
</soapenv:Envelope>
Response
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<soapenv:Header>
<wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action>
<wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
<wsa:MessageID>uuid:2C42C087-011B-4000-E000-0DE00AE35A2E</wsa:MessageID>
<wsa:RelatesTo>uuid:feacfe40-5342-11dd-bfe3-cce87efa941f</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>java.rmi.RemoteException: WS IBM-KANDULA Interoper FailedSimulated abort</faultstring>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
As suggested by Dasarath, the transaction management should work now but it's not.
I am not sure where I am going wrong.
Thanks.
Regards,
Anshuk Pal Chaudhuri
From: Pal Chaudhuri, Anshuk (Cognizant)
Sent: Wednesday, July 16, 2008 4:03 PM
To: 'kandula-dev@ws.apache.org'
Cc: 'Dasarath Weeratunge'
Subject: RE: Issues while compiling src code
Hi,
Thought the following might work:
public void invoke() throws RemoteException, ServiceException
{
DBUpdateService db = new DBUpdateServiceLocator();
DBUpdate invoke = db.getDBUpdate();
TransactionManagerImpl tm = TransactionManagerImpl.getInstance();
tm.begin();
try
{
invoke.insertTestOne(616,"cts");
}
catch (Exception e) {
tm.rollback();
}
tm.commit();
}
But there is a null pointer exception for the tm.rollback
java.lang.NullPointerException
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:796)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub.registerOperation(RegistrationPortTypeRPCBindingStub.java:290)
at org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:53)
at org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
at org.apache.kandula.coordinator.at.TransactionImpl.register(TransactionImpl.java:68)
at org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:136)
at org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at com.cts.db.ws.insert.Client.invoke(Client.java:62)
at com.cts.db.ws.insert.Client.main(Client.java:48)
Regards,
Anshuk Pal Chaudhuri
From: Pal Chaudhuri, Anshuk (Cognizant)
Sent: Wednesday, July 16, 2008 2:31 PM
To: kandula-dev@ws.apache.org
Cc: 'Dasarath Weeratunge'
Subject: RE: Issues while compiling src code
Hi,
As you suggested, I tried the following
public void invoke()
{
TransactionManagerImpl tm = TransactionManagerImpl.getInstance();
try {
tm.begin();
DBUpdateService db = new DBUpdateServiceLocator(); // using the stubs generated from the web service
DBUpdate invoke = db.getDBUpdate(); // using the stubs generated from the web service
invoke.insertTestOne(1,"anshuk"); // using the stubs generated from the web service
tm.commit();
}
catch (Exception e) {
e.printStackTrace();
}
}
But this is not revoking the inserted records from the database; When I checked the soap request in the tcpmon, the coordination context is not in the soap header of the request. Do I need to add any configuration or anything else?
Thanks.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
Sent: Tuesday, July 15, 2008 7:44 PM
To: kandula-dev@ws.apache.org
Cc: Pal Chaudhuri, Anshuk (Cognizant)
Subject: RE: Issues while compiling src code
Quoting Anshuk.PalChaudhuri@cognizant.com:
I don't understand why you have your own client level handler to
create a coordination context and then add it to out going messages!
Kandula already provides that mechanism and much more.
Just deploy Kandula in Axis according to the user guide and then
using a standalone client + the toy TM, invoke your WAS service inside a
transaction: toyTm.begin(); foo.invokeWASService(); toyTm.commit();
Since you are using a standalone client and Kandula only supports asynchornous
port types, tm.commit will not function properly. However, if you try this
inside a container like Axis, things will work as expected.
Thanks,
-- dasarath
> Hi,
>
>
>
> Agreed.
>
>
>
> Let's go step by step.
>
>
>
> I am using the Kandula activation service. The coordination context is being
> created. The coordination context is also being embedded in the soap envelope
> and the web service operation is then invoked.
>
>
>
>
>
> I am using a client level handler which invokes the Kandula activation
> service and creates the context and puts the coordination context in the soap
> header. (similar to what is done in the TM begin() method)
>
>
>
> The client handler has the invoke method which does the same.
>
>
>
> public void invoke(MessageContext mc) throws AxisFault
>
> {
>
> System.out.println("handler");
>
> CoordinationContext ctx;
>
> CoordinationContextType ctxType;
>
> try {
>
> ActivationStub stub = new
> ActivationStub(new EndpointReference(
>
>
> "http://localhost:1234/axis/services/activationCoordinator"));
>
> ctx =
> stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
>
>
> SOAPHeader header =
> mc.getCurrentMessage().getSOAPEnvelope().getHeader();
>
>
> ctx.toSOAPHeaderElement(header);
>
> }catch (Exception re) {
>
> try {
>
> ctx = null;
>
> } catch
> (Exception e) {
>
>
> e.printStackTrace();
>
>
> }
>
> }
>
> }
>
>
>
> (1234 is the tcpmon port monitor directed to 8080 @
> axis/services/activationCoordinator)
>
>
>
> The coordination context which is being in the soap request header while
> invoking the web service operation is:
>
>
>
> <wscoor:CoordinationContext
> soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
> soapenv:mustUnderstand="0"
> xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
>
>
> <wscoor:Identifier>uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</wscoor:Identifier>
>
>
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
>
> <wscoor:RegistrationService>
>
> <wsa:Address
>
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
>
> <wsa:ReferenceProperties
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> <ns4:CallbackRef
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</ns4:CallbackRef>
>
> </wsa:ReferenceProperties>
>
> </wscoor:RegistrationService>
>
> </wscoor:CoordinationContext>
>
>
>
> Now after this is done, you suggested that the WAS should register the
> Kandula registration service (which would be I suppose
> http://localhost:8080/axis/services/registrationCoordinator) , I am not
> really sure how to achieve this.
>
>
>
> Any pointers?
>
>
>
> Thanking you in advance.
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
>
>
> -----Original Message-----
> From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> Sent: Monday, July 14, 2008 7:43 PM
> To: kandula-dev@ws.apache.org
> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> Subject: RE: Issues while compiling src code
>
>
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
>
>
> You should be able to use either coordinator. To use a different coordinator
>
> with the Kandula provided toy TM, you can specify the end point of the
>
> activation service to the begin() method.
>
>
>
> Note that the coordination context is created by the activation service.
>
> There is another Coordinator service which handles termination. Please
>
> make sure that you are not sending the CreateCoordinationContext message to
>
> the coordinator endpoint.
>
>
>
> If you are using the Kandula activation service, then once the coordination
>
> context has been created and the service on WAS is invoked with the
> coordination
>
> context, WAS should register with the Kandula registration service.
>
>
>
> If you are using WAS activation service, then service on WAS should register
>
> with the registration service on WAS.
>
>
>
> Let me know whether you get this far.
>
>
>
> Please post your questions on kandula-dev so that they get archived.
>
>
>
> Thanks,
>
> -- dasarath
>
>
>
>
>
> > That is exactly what I am trying to achieve using the Kandula client. And
>
> > that's where I am facing the issues L L
>
>
>
> >
>
> > Since I am using a Kandula client, the coordination context should be
> created
>
> > using web service activationCoordinator deployed on tomcat
>
> > àhttp://localhost:8080/axis/services/activationCoordinator, which is
> actually
>
> > being created and also being sent in the soap header in the soap request
>
> > while the web service on WAS. (PFA kandula-soap-request.xml)
>
> >
>
> > But then again, this transaction details is not working as the revoking
> part
>
> > is not working properly.
>
>
>
> >
>
> >
>
>
>
> >
>
> > Then I thought may be the coordination service of WAS should be invoked
> which
>
> > lies at http://localhost:9080/_IBMSYSAPP/wsat/services/Coordinator (which
>
> > might create the correct coordination context as required like attached à
>
> > WAS-Client-SOAP-request.xml ) but the request which is being sent to
> invoke
>
> > the coordinator service is not correct. (PFA the errors.txt)
>
> >
>
> >
>
>
>
> >
>
> > Thanks.
>
> >
>
> >
>
>
>
> >
>
> > Regards,
>
> >
>
> > Anshuk Pal Chaudhuri
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > -----Original Message-----
>
> > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
>
>
> > Sent: Friday, July 11, 2008 7:43 PM
>
> > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Subject: RE: Issues while compiling src code
>
> >
>
> >
>
>
>
> >
>
> > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> >
>
>
>
> >
>
> > Yes, this can be done. You can replace either the WAS box or MSFT box with
>
> >
>
> > Axis+Kandula or add Axis+Kandula as another branch of the same activity
>
> > along
>
> >
>
> > with the other two.
>
> >
>
> >
>
>
>
> >
>
> > If your resource is deployed in WAS then Kandula is only a client. Kandula
>
> >
>
> > will create a coordination context and then attach it to all invocations
>
> >
>
> > of your service methods on WAS and then finally terminate that transaction
>
> >
>
> > using WS-AT. Of course, we could add other resources to this activity
>
> > possibly
>
> >
>
> > residing outside of WAS. How your resource is configured and how the web
>
> > service
>
> >
>
> > is setup in WAS that you have to look at WAS docs. I would recommend that
>
> > you
>
> >
>
> > take the same WSDL of this interop scenario and try to generate a Kandula
>
> >
>
> > client. That way you can follow the same instructions on setting up the
> WAS
>
> > end.
>
> >
>
> >
>
>
>
> >
>
> > The other scenario is, WAS acts as the client and resource is deployed
>
> > inside
>
> >
>
> > Geronimo with Kandula providing the interfacing between WS-AT and JTA. You
>
> > can
>
> >
>
> > even test this with out involving Geronimo by using the toy TM that we
> have
>
> >
>
> > provided. Since we are only concerned about WS-AT, JTA side is not
>
> > important.
>
> >
>
> >
>
>
>
> >
>
> > I have tried inter-op testing Kandula with IBM implementation but had to
>
> > stop
>
> >
>
> > it due to a bug in their code.
>
> >
>
> >
>
>
>
> >
>
> > Happy testing!
>
> >
>
> > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks Dasarath for the input.
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > I am not trying to integrate Kandula with WAS as Kandula is being done
>
> >
>
> > > today with Geronimo. That is not my objective.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > The objective is:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Web Service Transaction Interoperability (Kandula Implementation and WAS
>
> >
>
> > > Implementation of Web Service Transaction)
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Web Service Client (build with axis generated stubs and using Kandula to
>
> >
>
> > > attach transaction details) ----------------------------> Web Service on
>
> >
>
> > > WAS (which does some insertion into database) Do you think this is
>
> >
>
> > > feasible or not?
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > The resources are defined (say datasource) within the WAS Container. Now
>
> >
>
> > > the question would be do I need to expose these resources (XAResource)
>
> >
>
> > > deployed within WAS using Kandula?
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > I was having a look somewhere
>
> >
>
> > > (http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
>
> >
>
> > > o/0707_lo.html ) where there are MS Web Service Clients (Web Service
>
> >
>
> > > Transactions configured) are interoperating with Web Services deployed
>
> >
>
> > > on WAS and the transaction management is happening. That is an excellent
>
> >
>
> > > case of web service transaction interoperability. What I am wondering is
>
> >
>
> > > if that is possible, then why not what I am trying out, where the client
>
> >
>
> > > would be using axis (instead of Microsoft) and the transaction
>
> >
>
> > > configuration would be done using Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Let me know if I am not clear.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > -----Original Message-----
>
> >
>
> > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
> >
>
> >
>
>
>
> >
>
> > > Sent: Thursday, July 10, 2008 10:55 PM
>
> >
>
> > > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > > Cc: kandula-dev@ws.apache.org
>
> >
>
> > > Subject: RE: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Quoting Anshuk <An...@cognizant.com>:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Interfacing JTA with WS-AT is completely different from
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > looking at web services interoperability between different
>
> >
>
> > > implementations
>
> >
>
> > >
>
>
>
> >
>
> > > like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
>
> >
>
> > > this point.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > If you want to expose some XAResource deployed inside WAS using Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > then you need to interface Kandula with the native JTA implementation in
>
> >
>
> > > WAS.
>
> >
>
> > >
>
>
>
> >
>
> > > What Kandula does is it creates a JTA transaction whenever it sees a new
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > coordination context and attaches it to the thread that would execute
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > the web service. From there on, the native JTA implementation takes care
>
> >
>
> > >
>
>
>
> >
>
> > > of the rest. In the absence of such a native JTA implementation we have
>
> >
>
> > > provided
>
> >
>
> > >
>
>
>
> >
>
> > > a toy JTA implementation that could be used but this is mainly for
>
> >
>
> > > testing.
>
> >
>
> > >
>
>
>
> >
>
> > > When the WS-AT protocol attempts to terminate the activity, Kandula will
>
> >
>
> > >
>
>
>
> >
>
> > > use its private interface with the native JTA implementation to
>
> >
>
> > > terminate
>
> >
>
> > >
>
>
>
> >
>
> > > the JTA transaction that was created earlier. Here Kandula uses the
>
> >
>
> > > two-phase
>
> >
>
> > >
>
>
>
> >
>
> > > commit protocol.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > However, the JTA API is not sufficient to completely handle the two
>
> >
>
> > > phase
>
> >
>
> > >
>
>
>
> >
>
> > > commit protocol that is used to terminate a transaction. For example, if
>
> >
>
> > >
>
>
>
> >
>
> > > you look at how Kandula has been interfaced with Geronimo, you would see
>
> >
>
> > >
>
>
>
> >
>
> > > that we have used an API exposed by the Geronimo transaction manager
>
> >
>
> > > which
>
> >
>
> > >
>
>
>
> >
>
> > > is non-standard. In the case of WAS it is not possible to study their
>
> >
>
> > >
>
>
>
> >
>
> > > internal API s to do the same. In short, it is not possible to do what
>
> >
>
> > > we have
>
> >
>
> > >
>
>
>
> >
>
> > > done with Geronimo with WAS.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > You could however, try the following:
>
> >
>
> > >
>
>
>
> >
>
> > > 1) Use a Kandula client with WAS server.
>
> >
>
> > >
>
>
>
> >
>
> > > 2) WAS client with Kandula server (in Geronimo server or Tomcat +
>
> >
>
> > > Geronimo
>
> >
>
> > >
>
>
>
> >
>
> > > transaction manager)
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > -- dasarath
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks Dasarath for the input.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > As I mentioned earlier, I did try out the WAS-WAS and it is working
>
> >
>
> > > fine. I
>
> >
>
> > >
>
>
>
> >
>
> > > > also tried out the Kandula-Kandula (as you mentioned about the banking
>
> >
>
> > >
>
>
>
> >
>
> > > > example)and it is also working fine.
>
> >
>
> > >
>
>
>
> >
>
> > > > Now w.r.t. the sceanrio which I described earlier, the first case
>
> >
>
> > > (WAS-WAS),
>
> >
>
> > >
>
>
>
> >
>
> > > > the datasource is defined within the WAS container, so the application
>
> >
>
> > > is
>
> >
>
> > >
>
>
>
> >
>
> > > > taking care of the rollback.
>
> >
>
> > >
>
>
>
> >
>
> > > > In the second case, (correct me if I am wrong), the resources are
>
> >
>
> > > defined in
>
> >
>
> > >
>
>
>
> >
>
> > > > the BankOneDBMS which implements NamedXAResource so the resources are
>
> >
>
> > >
>
>
>
> >
>
> > > > enlisted there only and the commit and rollback are managed explicitly
>
> >
>
> > >
>
>
>
> >
>
> > > > (using the Transaction Manager of Geronimo)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Now when I am trying to incorporate Kandula (at the client side) and
>
> >
>
> > > WAS (at
>
> >
>
> > >
>
>
>
> >
>
> > > > the server side, where the web service is deployed), the transaction
>
> >
>
> > >
>
>
>
> >
>
> > > > management is not taking place as expected.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > The co-ordination context (within the soap request) that I have sent
>
> >
>
> > > across
>
> >
>
> > >
>
>
>
> >
>
> > > > from WAS (when client) and Kandula (when client) seems to be
>
> >
>
> > > different.
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > In case of kandula (being client), the standalone client uses the
>
> >
>
> > > stubs
>
> >
>
> > >
>
>
>
> >
>
> > > > (generated from axis wsdl2java) and a client handler does the
>
> >
>
> > > following:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > public void invoke(MessageContext mc) throws AxisFault {
>
> >
>
> > >
>
>
>
> >
>
> > > > System.out.println("handler");
>
> >
>
> > >
>
>
>
> >
>
> > > > CoordinationContext ctx;
>
> >
>
> > >
>
>
>
> >
>
> > > > CoordinationContextType ctxType;
>
> >
>
> > >
>
>
>
> >
>
> > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > > ActivationStub stub = new
>
> >
>
> > > ActivationStub(new EndpointReference(
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > "http://localhost:8081/axis/services/activationCoordinator"));
>
> >
>
> > >
>
>
>
> >
>
> > > > ctx =
>
> >
>
> > > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > }catch (Exception re) {
>
> >
>
> > >
>
>
>
> >
>
> > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > > ctx =
>
> >
>
> > > null;
>
> >
>
> > >
>
>
>
> >
>
> > > > } catch
>
> >
>
> > > (Exception e) {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > e.printStackTrace();
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > }
>
> >
>
> > >
>
>
>
> >
>
> > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > I am not sure where I am going wrong.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Can you guide me on this.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > > Anshuk
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Dasarath Weeratunge-3 wrote:
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Have you looked at the banking example? If you are going to
>
> >
>
> > >
>
>
>
> >
>
> > > > > use WAS on one end and Kandula on the other end I would very much
>
> >
>
> > >
>
>
>
> >
>
> > > > > like to see what the result is going to be. I would recommend
>
> >
>
> > >
>
>
>
> >
>
> > > > > that you first try WAS-WAS and Kandula-Kandula before attempting
>
> >
>
> > >
>
>
>
> >
>
> > > > > WAS-Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > > what
>
> >
>
> > >
>
>
>
> >
>
> > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > This is unfortunately a little too gernal to answer over a mailing
>
> >
>
> > > list.
>
> >
>
> > >
>
>
>
> >
>
> > > > > Please be more specific/discrete about what you are trying to do.
>
> >
>
> > > For
>
> >
>
> > >
>
>
>
> >
>
> > > > > example,
>
> >
>
> > >
>
>
>
> >
>
> > > > > if you say you tried this and got this error, then we can tell you
>
> >
>
> > > why and
>
> >
>
> > >
>
>
>
> >
>
> > > > > what you need to do differently.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > > > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Hi Hannes,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Thanks for your input.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did try out using the atomic transaction that comes with the IBM
>
> >
>
> > > WAS
>
> >
>
> > >
>
>
>
> >
>
> > > > >> 6.0. The web service would insert some values in a database. The
>
> >
>
> > > web
>
> >
>
> > >
>
>
>
> >
>
> > > > >> service client was built using the stubs generated by the IBM SOAP
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Engine WSDL2Java and configured in such a way so that it would send
>
> >
>
> > >
>
>
>
> >
>
> > > > >> atomic transaction details in the soap envelope. So, I tested a
>
> >
>
> > > good
>
> >
>
> > >
>
>
>
> >
>
> > > > >> scenario and the values got inserted in the table. While testing
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> error scenario, in the web service after the part of the which does
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> insertion, I threw a runtime exception explicitly and when I
>
> >
>
> > > checked the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> tables, the values were not inserted.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Now I intend to do a similar scenario using Apache Kandula at the
>
> >
>
> > > client
>
> >
>
> > >
>
>
>
> >
>
> > > > >> side. The same web service (deployed on WAS) would be used, but
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> client would now send the soap request using apache Kandula and the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> necessary transaction details (within the soap header) would be
>
> >
>
> > > sent.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > > what
>
> >
>
> > >
>
>
>
> >
>
> > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Can you help/guide me in testing the above.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Thanking you in advance.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> -----Original Message-----
>
> >
>
> > >
>
>
>
> >
>
> > > > >> From: Hannes Erven [mailto:herven@apache.org]
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Sent: Sunday, June 29, 2008 4:37 AM
>
> >
>
> > >
>
>
>
> >
>
> > > > >> To: kandula-dev@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Subject: Re: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Hi Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> > What I am not clear is the flow how exactly the client creates
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> > co-ordination context and so on.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I'm not sure what you are exactly looking for and what you already
>
> >
>
> > > know
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> or have read.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> As a general starting point, I suggest you have a look at the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> WS-Coordination specification and also WS-AtomicTransaction or
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> WS-BusinessActivity, whatever transaction type you are interested
>
> >
>
> > > in.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> In the source code, at the Kandula server it all starts at
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> > > org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
>
> >
>
> > >
>
>
>
> >
>
> > > > >> text
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> , this is where the call from the client is received. From there,
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> actual transaction coordinator object is created depending on the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> requested type of transaction.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> If you have further questions or need reading tips, please reply
>
> >
>
> > > with
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> more details what you are interested in.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Best regards and thank you for your interest in Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> -hannes
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> This e-mail and any files transmitted with it are for the sole use
>
> >
>
> > > of the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> intended recipient(s) and may contain confidential and privileged
>
> >
>
> > >
>
>
>
> >
>
> > > > >> information.
>
> >
>
> > >
>
>
>
> >
>
> > > > >> If you are not the intended recipient, please contact the sender by
>
> >
>
> > > reply
>
> >
>
> > >
>
>
>
> >
>
> > > > >> e-mail and destroy all copies of the original message.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Any unauthorised review, use, disclosure, dissemination,
>
> >
>
> > > forwarding,
>
> >
>
> > >
>
>
>
> >
>
> > > > >> printing
>
> >
>
> > >
>
>
>
> >
>
> > > > >> or copying of this email or any action taken in reliance on this
>
> >
>
> > > e-mail
>
> >
>
> > >
>
>
>
> >
>
> > > > >> is
>
> >
>
> > >
>
>
>
> >
>
> > > > >> strictly
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> prohibited and may be unlawful.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > --
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > View this message in context:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
>
> >
>
> > > 3.html
>
> >
>
> > >
>
>
>
> >
>
> > > > Sent from the Kandula mailing list archive at Nabble.com.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > This e-mail and any files transmitted with it are for the sole use of
> the
>
> >
>
> > > intended recipient(s) and may contain confidential and privileged
>
> >
>
> > > information.
>
> >
>
> > > If you are not the intended recipient, please contact the sender by
> reply
>
> >
>
> > > e-mail and destroy all copies of the original message.
>
> >
>
> >
>
>
>
> >
>
> > > Any unauthorised review, use, disclosure, dissemination, forwarding,
>
> > printing
>
> >
>
> > > or copying of this email or any action taken in reliance on this e-mail
> is
>
> >
>
> > > strictly
>
> >
>
> >
>
>
>
> >
>
> > > prohibited and may be unlawful.
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
> >
>
> > This e-mail and any files transmitted with it are for the sole use of the
>
> > intended recipient(s) and may contain confidential and privileged
>
> > information.
>
> > If you are not the intended recipient, please contact the sender by reply
>
> > e-mail and destroy all copies of the original message.
>
>
>
> > Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing
>
> > or copying of this email or any action taken in reliance on this e-mail is
>
> > strictly
>
>
>
> > prohibited and may be unlawful.
>
>
>
>
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing
> or copying of this email or any action taken in reliance on this e-mail is
> strictly
> prohibited and may be unlawful.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
RE: Issues while compiling src code
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Anshuk.PalChaudhuri@cognizant.com:
I don't understand why you have your own client level handler to
create a coordination context and then add it to out going messages!
Kandula already provides that mechanism and much more.
Just deploy Kandula in Axis according to the user guide and then
using a standalone client + the toy TM, invoke your WAS service inside a
transaction: toyTm.begin(); foo.invokeWASService(); toyTm.commit();
Since you are using a standalone client and Kandula only supports asynchornous
port types, tm.commit will not function properly. However, if you try this
inside a container like Axis, things will work as expected.
Thanks,
-- dasarath
> Hi,
>
>
>
> Agreed.
>
>
>
> Let's go step by step.
>
>
>
> I am using the Kandula activation service. The coordination context is being
> created. The coordination context is also being embedded in the soap envelope
> and the web service operation is then invoked.
>
>
>
>
>
> I am using a client level handler which invokes the Kandula activation
> service and creates the context and puts the coordination context in the soap
> header. (similar to what is done in the TM begin() method)
>
>
>
> The client handler has the invoke method which does the same.
>
>
>
> public void invoke(MessageContext mc) throws AxisFault
>
> {
>
> System.out.println("handler");
>
> CoordinationContext ctx;
>
> CoordinationContextType ctxType;
>
> try {
>
> ActivationStub stub = new
> ActivationStub(new EndpointReference(
>
>
> "http://localhost:1234/axis/services/activationCoordinator"));
>
> ctx =
> stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
>
>
> SOAPHeader header =
> mc.getCurrentMessage().getSOAPEnvelope().getHeader();
>
>
> ctx.toSOAPHeaderElement(header);
>
> }catch (Exception re) {
>
> try {
>
> ctx = null;
>
> } catch
> (Exception e) {
>
>
> e.printStackTrace();
>
>
> }
>
> }
>
> }
>
>
>
> (1234 is the tcpmon port monitor directed to 8080 @
> axis/services/activationCoordinator)
>
>
>
> The coordination context which is being in the soap request header while
> invoking the web service operation is:
>
>
>
> <wscoor:CoordinationContext
> soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
> soapenv:mustUnderstand="0"
> xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
>
>
> <wscoor:Identifier>uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</wscoor:Identifier>
>
>
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
>
> <wscoor:RegistrationService>
>
> <wsa:Address
>
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
>
> <wsa:ReferenceProperties
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> <ns4:CallbackRef
>
xmlns:ns4="http://ws.apache.org/kandula">uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</ns4:CallbackRef>
>
> </wsa:ReferenceProperties>
>
> </wscoor:RegistrationService>
>
> </wscoor:CoordinationContext>
>
>
>
> Now after this is done, you suggested that the WAS should register the
> Kandula registration service (which would be I suppose
> http://localhost:8080/axis/services/registrationCoordinator) , I am not
> really sure how to achieve this.
>
>
>
> Any pointers?
>
>
>
> Thanking you in advance.
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
>
>
> -----Original Message-----
> From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> Sent: Monday, July 14, 2008 7:43 PM
> To: kandula-dev@ws.apache.org
> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> Subject: RE: Issues while compiling src code
>
>
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
>
>
> You should be able to use either coordinator. To use a different coordinator
>
> with the Kandula provided toy TM, you can specify the end point of the
>
> activation service to the begin() method.
>
>
>
> Note that the coordination context is created by the activation service.
>
> There is another Coordinator service which handles termination. Please
>
> make sure that you are not sending the CreateCoordinationContext message to
>
> the coordinator endpoint.
>
>
>
> If you are using the Kandula activation service, then once the coordination
>
> context has been created and the service on WAS is invoked with the
> coordination
>
> context, WAS should register with the Kandula registration service.
>
>
>
> If you are using WAS activation service, then service on WAS should register
>
> with the registration service on WAS.
>
>
>
> Let me know whether you get this far.
>
>
>
> Please post your questions on kandula-dev so that they get archived.
>
>
>
> Thanks,
>
> -- dasarath
>
>
>
>
>
> > That is exactly what I am trying to achieve using the Kandula client. And
>
> > that's where I am facing the issues L L
>
>
>
> >
>
> > Since I am using a Kandula client, the coordination context should be
> created
>
> > using web service activationCoordinator deployed on tomcat
>
> > àhttp://localhost:8080/axis/services/activationCoordinator, which is
> actually
>
> > being created and also being sent in the soap header in the soap request
>
> > while the web service on WAS. (PFA kandula-soap-request.xml)
>
> >
>
> > But then again, this transaction details is not working as the revoking
> part
>
> > is not working properly.
>
>
>
> >
>
> >
>
>
>
> >
>
> > Then I thought may be the coordination service of WAS should be invoked
> which
>
> > lies at http://localhost:9080/_IBMSYSAPP/wsat/services/Coordinator (which
>
> > might create the correct coordination context as required like attached à
>
> > WAS-Client-SOAP-request.xml ) but the request which is being sent to
> invoke
>
> > the coordinator service is not correct. (PFA the errors.txt)
>
> >
>
> >
>
>
>
> >
>
> > Thanks.
>
> >
>
> >
>
>
>
> >
>
> > Regards,
>
> >
>
> > Anshuk Pal Chaudhuri
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > -----Original Message-----
>
> > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
>
>
> > Sent: Friday, July 11, 2008 7:43 PM
>
> > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Subject: RE: Issues while compiling src code
>
> >
>
> >
>
>
>
> >
>
> > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> >
>
>
>
> >
>
> > Yes, this can be done. You can replace either the WAS box or MSFT box with
>
> >
>
> > Axis+Kandula or add Axis+Kandula as another branch of the same activity
>
> > along
>
> >
>
> > with the other two.
>
> >
>
> >
>
>
>
> >
>
> > If your resource is deployed in WAS then Kandula is only a client. Kandula
>
> >
>
> > will create a coordination context and then attach it to all invocations
>
> >
>
> > of your service methods on WAS and then finally terminate that transaction
>
> >
>
> > using WS-AT. Of course, we could add other resources to this activity
>
> > possibly
>
> >
>
> > residing outside of WAS. How your resource is configured and how the web
>
> > service
>
> >
>
> > is setup in WAS that you have to look at WAS docs. I would recommend that
>
> > you
>
> >
>
> > take the same WSDL of this interop scenario and try to generate a Kandula
>
> >
>
> > client. That way you can follow the same instructions on setting up the
> WAS
>
> > end.
>
> >
>
> >
>
>
>
> >
>
> > The other scenario is, WAS acts as the client and resource is deployed
>
> > inside
>
> >
>
> > Geronimo with Kandula providing the interfacing between WS-AT and JTA. You
>
> > can
>
> >
>
> > even test this with out involving Geronimo by using the toy TM that we
> have
>
> >
>
> > provided. Since we are only concerned about WS-AT, JTA side is not
>
> > important.
>
> >
>
> >
>
>
>
> >
>
> > I have tried inter-op testing Kandula with IBM implementation but had to
>
> > stop
>
> >
>
> > it due to a bug in their code.
>
> >
>
> >
>
>
>
> >
>
> > Happy testing!
>
> >
>
> > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks Dasarath for the input.
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > I am not trying to integrate Kandula with WAS as Kandula is being done
>
> >
>
> > > today with Geronimo. That is not my objective.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > The objective is:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Web Service Transaction Interoperability (Kandula Implementation and WAS
>
> >
>
> > > Implementation of Web Service Transaction)
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Web Service Client (build with axis generated stubs and using Kandula to
>
> >
>
> > > attach transaction details) ----------------------------> Web Service on
>
> >
>
> > > WAS (which does some insertion into database) Do you think this is
>
> >
>
> > > feasible or not?
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > The resources are defined (say datasource) within the WAS Container. Now
>
> >
>
> > > the question would be do I need to expose these resources (XAResource)
>
> >
>
> > > deployed within WAS using Kandula?
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > I was having a look somewhere
>
> >
>
> > > (http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
>
> >
>
> > > o/0707_lo.html ) where there are MS Web Service Clients (Web Service
>
> >
>
> > > Transactions configured) are interoperating with Web Services deployed
>
> >
>
> > > on WAS and the transaction management is happening. That is an excellent
>
> >
>
> > > case of web service transaction interoperability. What I am wondering is
>
> >
>
> > > if that is possible, then why not what I am trying out, where the client
>
> >
>
> > > would be using axis (instead of Microsoft) and the transaction
>
> >
>
> > > configuration would be done using Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Let me know if I am not clear.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > -----Original Message-----
>
> >
>
> > > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
> >
>
> >
>
>
>
> >
>
> > > Sent: Thursday, July 10, 2008 10:55 PM
>
> >
>
> > > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > > Cc: kandula-dev@ws.apache.org
>
> >
>
> > > Subject: RE: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Quoting Anshuk <An...@cognizant.com>:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Interfacing JTA with WS-AT is completely different from
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > looking at web services interoperability between different
>
> >
>
> > > implementations
>
> >
>
> > >
>
>
>
> >
>
> > > like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
>
> >
>
> > > this point.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > If you want to expose some XAResource deployed inside WAS using Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > then you need to interface Kandula with the native JTA implementation in
>
> >
>
> > > WAS.
>
> >
>
> > >
>
>
>
> >
>
> > > What Kandula does is it creates a JTA transaction whenever it sees a new
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > coordination context and attaches it to the thread that would execute
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > the web service. From there on, the native JTA implementation takes care
>
> >
>
> > >
>
>
>
> >
>
> > > of the rest. In the absence of such a native JTA implementation we have
>
> >
>
> > > provided
>
> >
>
> > >
>
>
>
> >
>
> > > a toy JTA implementation that could be used but this is mainly for
>
> >
>
> > > testing.
>
> >
>
> > >
>
>
>
> >
>
> > > When the WS-AT protocol attempts to terminate the activity, Kandula will
>
> >
>
> > >
>
>
>
> >
>
> > > use its private interface with the native JTA implementation to
>
> >
>
> > > terminate
>
> >
>
> > >
>
>
>
> >
>
> > > the JTA transaction that was created earlier. Here Kandula uses the
>
> >
>
> > > two-phase
>
> >
>
> > >
>
>
>
> >
>
> > > commit protocol.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > However, the JTA API is not sufficient to completely handle the two
>
> >
>
> > > phase
>
> >
>
> > >
>
>
>
> >
>
> > > commit protocol that is used to terminate a transaction. For example, if
>
> >
>
> > >
>
>
>
> >
>
> > > you look at how Kandula has been interfaced with Geronimo, you would see
>
> >
>
> > >
>
>
>
> >
>
> > > that we have used an API exposed by the Geronimo transaction manager
>
> >
>
> > > which
>
> >
>
> > >
>
>
>
> >
>
> > > is non-standard. In the case of WAS it is not possible to study their
>
> >
>
> > >
>
>
>
> >
>
> > > internal API s to do the same. In short, it is not possible to do what
>
> >
>
> > > we have
>
> >
>
> > >
>
>
>
> >
>
> > > done with Geronimo with WAS.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > You could however, try the following:
>
> >
>
> > >
>
>
>
> >
>
> > > 1) Use a Kandula client with WAS server.
>
> >
>
> > >
>
>
>
> >
>
> > > 2) WAS client with Kandula server (in Geronimo server or Tomcat +
>
> >
>
> > > Geronimo
>
> >
>
> > >
>
>
>
> >
>
> > > transaction manager)
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > -- dasarath
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks Dasarath for the input.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > As I mentioned earlier, I did try out the WAS-WAS and it is working
>
> >
>
> > > fine. I
>
> >
>
> > >
>
>
>
> >
>
> > > > also tried out the Kandula-Kandula (as you mentioned about the banking
>
> >
>
> > >
>
>
>
> >
>
> > > > example)and it is also working fine.
>
> >
>
> > >
>
>
>
> >
>
> > > > Now w.r.t. the sceanrio which I described earlier, the first case
>
> >
>
> > > (WAS-WAS),
>
> >
>
> > >
>
>
>
> >
>
> > > > the datasource is defined within the WAS container, so the application
>
> >
>
> > > is
>
> >
>
> > >
>
>
>
> >
>
> > > > taking care of the rollback.
>
> >
>
> > >
>
>
>
> >
>
> > > > In the second case, (correct me if I am wrong), the resources are
>
> >
>
> > > defined in
>
> >
>
> > >
>
>
>
> >
>
> > > > the BankOneDBMS which implements NamedXAResource so the resources are
>
> >
>
> > >
>
>
>
> >
>
> > > > enlisted there only and the commit and rollback are managed explicitly
>
> >
>
> > >
>
>
>
> >
>
> > > > (using the Transaction Manager of Geronimo)
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Now when I am trying to incorporate Kandula (at the client side) and
>
> >
>
> > > WAS (at
>
> >
>
> > >
>
>
>
> >
>
> > > > the server side, where the web service is deployed), the transaction
>
> >
>
> > >
>
>
>
> >
>
> > > > management is not taking place as expected.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > The co-ordination context (within the soap request) that I have sent
>
> >
>
> > > across
>
> >
>
> > >
>
>
>
> >
>
> > > > from WAS (when client) and Kandula (when client) seems to be
>
> >
>
> > > different.
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > In case of kandula (being client), the standalone client uses the
>
> >
>
> > > stubs
>
> >
>
> > >
>
>
>
> >
>
> > > > (generated from axis wsdl2java) and a client handler does the
>
> >
>
> > > following:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > public void invoke(MessageContext mc) throws AxisFault {
>
> >
>
> > >
>
>
>
> >
>
> > > > System.out.println("handler");
>
> >
>
> > >
>
>
>
> >
>
> > > > CoordinationContext ctx;
>
> >
>
> > >
>
>
>
> >
>
> > > > CoordinationContextType ctxType;
>
> >
>
> > >
>
>
>
> >
>
> > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > > ActivationStub stub = new
>
> >
>
> > > ActivationStub(new EndpointReference(
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > "http://localhost:8081/axis/services/activationCoordinator"));
>
> >
>
> > >
>
>
>
> >
>
> > > > ctx =
>
> >
>
> > > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > }catch (Exception re) {
>
> >
>
> > >
>
>
>
> >
>
> > > > try {
>
> >
>
> > >
>
>
>
> >
>
> > > > ctx =
>
> >
>
> > > null;
>
> >
>
> > >
>
>
>
> >
>
> > > > } catch
>
> >
>
> > > (Exception e) {
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > e.printStackTrace();
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > }
>
> >
>
> > >
>
>
>
> >
>
> > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > > }
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > I am not sure where I am going wrong.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Can you guide me on this.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Thanks.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > > Anshuk
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > Dasarath Weeratunge-3 wrote:
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Have you looked at the banking example? If you are going to
>
> >
>
> > >
>
>
>
> >
>
> > > > > use WAS on one end and Kandula on the other end I would very much
>
> >
>
> > >
>
>
>
> >
>
> > > > > like to see what the result is going to be. I would recommend
>
> >
>
> > >
>
>
>
> >
>
> > > > > that you first try WAS-WAS and Kandula-Kandula before attempting
>
> >
>
> > >
>
>
>
> >
>
> > > > > WAS-Kandula.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > > what
>
> >
>
> > >
>
>
>
> >
>
> > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > This is unfortunately a little too gernal to answer over a mailing
>
> >
>
> > > list.
>
> >
>
> > >
>
>
>
> >
>
> > > > > Please be more specific/discrete about what you are trying to do.
>
> >
>
> > > For
>
> >
>
> > >
>
>
>
> >
>
> > > > > example,
>
> >
>
> > >
>
>
>
> >
>
> > > > > if you say you tried this and got this error, then we can tell you
>
> >
>
> > > why and
>
> >
>
> > >
>
>
>
> >
>
> > > > > what you need to do differently.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > > Thanks,
>
> >
>
> > >
>
>
>
> >
>
> > > > > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Hi Hannes,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Thanks for your input.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did try out using the atomic transaction that comes with the IBM
>
> >
>
> > > WAS
>
> >
>
> > >
>
>
>
> >
>
> > > > >> 6.0. The web service would insert some values in a database. The
>
> >
>
> > > web
>
> >
>
> > >
>
>
>
> >
>
> > > > >> service client was built using the stubs generated by the IBM SOAP
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Engine WSDL2Java and configured in such a way so that it would send
>
> >
>
> > >
>
>
>
> >
>
> > > > >> atomic transaction details in the soap envelope. So, I tested a
>
> >
>
> > > good
>
> >
>
> > >
>
>
>
> >
>
> > > > >> scenario and the values got inserted in the table. While testing
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> error scenario, in the web service after the part of the which does
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> insertion, I threw a runtime exception explicitly and when I
>
> >
>
> > > checked the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> tables, the values were not inserted.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Now I intend to do a similar scenario using Apache Kandula at the
>
> >
>
> > > client
>
> >
>
> > >
>
>
>
> >
>
> > > > >> side. The same web service (deployed on WAS) would be used, but
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> client would now send the soap request using apache Kandula and the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> necessary transaction details (within the soap header) would be
>
> >
>
> > > sent.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I did have a look at the documentation, but I am not exactly sure
>
> >
>
> > > what
>
> >
>
> > >
>
>
>
> >
>
> > > > >> needs to be done.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Can you help/guide me in testing the above.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Thanking you in advance.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Regards,
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Anshuk Pal Chaudhuri
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> -----Original Message-----
>
> >
>
> > >
>
>
>
> >
>
> > > > >> From: Hannes Erven [mailto:herven@apache.org]
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Sent: Sunday, June 29, 2008 4:37 AM
>
> >
>
> > >
>
>
>
> >
>
> > > > >> To: kandula-dev@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Subject: Re: Issues while compiling src code
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Hi Anshuk,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> > What I am not clear is the flow how exactly the client creates
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> > co-ordination context and so on.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> I'm not sure what you are exactly looking for and what you already
>
> >
>
> > > know
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> or have read.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> As a general starting point, I suggest you have a look at the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> WS-Coordination specification and also WS-AtomicTransaction or
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> WS-BusinessActivity, whatever transaction type you are interested
>
> >
>
> > > in.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> In the source code, at the Kandula server it all starts at
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> > > org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
>
> >
>
> > >
>
>
>
> >
>
> > > > >> text
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> , this is where the call from the client is received. From there,
>
> >
>
> > > the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> actual transaction coordinator object is created depending on the
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> requested type of transaction.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> If you have further questions or need reading tips, please reply
>
> >
>
> > > with
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> more details what you are interested in.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Best regards and thank you for your interest in Kandula,
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> -hannes
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> This e-mail and any files transmitted with it are for the sole use
>
> >
>
> > > of the
>
> >
>
> > >
>
>
>
> >
>
> > > > >> intended recipient(s) and may contain confidential and privileged
>
> >
>
> > >
>
>
>
> >
>
> > > > >> information.
>
> >
>
> > >
>
>
>
> >
>
> > > > >> If you are not the intended recipient, please contact the sender by
>
> >
>
> > > reply
>
> >
>
> > >
>
>
>
> >
>
> > > > >> e-mail and destroy all copies of the original message.
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> Any unauthorised review, use, disclosure, dissemination,
>
> >
>
> > > forwarding,
>
> >
>
> > >
>
>
>
> >
>
> > > > >> printing
>
> >
>
> > >
>
>
>
> >
>
> > > > >> or copying of this email or any action taken in reliance on this
>
> >
>
> > > e-mail
>
> >
>
> > >
>
>
>
> >
>
> > > > >> is
>
> >
>
> > >
>
>
>
> >
>
> > > > >> strictly
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >> prohibited and may be unlawful.
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > --
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > View this message in context:
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> > > http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
>
> >
>
> > > 3.html
>
> >
>
> > >
>
>
>
> >
>
> > > > Sent from the Kandula mailing list archive at Nabble.com.
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > > ---------------------------------------------------------------------
>
> >
>
> > >
>
>
>
> >
>
> > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > >
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > This e-mail and any files transmitted with it are for the sole use of
> the
>
> >
>
> > > intended recipient(s) and may contain confidential and privileged
>
> >
>
> > > information.
>
> >
>
> > > If you are not the intended recipient, please contact the sender by
> reply
>
> >
>
> > > e-mail and destroy all copies of the original message.
>
> >
>
> >
>
>
>
> >
>
> > > Any unauthorised review, use, disclosure, dissemination, forwarding,
>
> > printing
>
> >
>
> > > or copying of this email or any action taken in reliance on this e-mail
> is
>
> >
>
> > > strictly
>
> >
>
> >
>
>
>
> >
>
> > > prohibited and may be unlawful.
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
> >
>
> > This e-mail and any files transmitted with it are for the sole use of the
>
> > intended recipient(s) and may contain confidential and privileged
>
> > information.
>
> > If you are not the intended recipient, please contact the sender by reply
>
> > e-mail and destroy all copies of the original message.
>
>
>
> > Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing
>
> > or copying of this email or any action taken in reliance on this e-mail is
>
> > strictly
>
>
>
> > prohibited and may be unlawful.
>
>
>
>
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing
> or copying of this email or any action taken in reliance on this e-mail is
> strictly
> prohibited and may be unlawful.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Hi,
Agreed.
Let's go step by step.
I am using the Kandula activation service. The coordination context is being created. The coordination context is also being embedded in the soap envelope and the web service operation is then invoked.
I am using a client level handler which invokes the Kandula activation service and creates the context and puts the coordination context in the soap header. (similar to what is done in the TM begin() method)
The client handler has the invoke method which does the same.
public void invoke(MessageContext mc) throws AxisFault
{
System.out.println("handler");
CoordinationContext ctx;
CoordinationContextType ctxType;
try {
ActivationStub stub = new ActivationStub(new EndpointReference(
"http://localhost:1234/axis/services/activationCoordinator"));
ctx = stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
SOAPHeader header = mc.getCurrentMessage().getSOAPEnvelope().getHeader();
ctx.toSOAPHeaderElement(header);
}catch (Exception re) {
try {
ctx = null;
} catch (Exception e) {
e.printStackTrace();
}
}
}
(1234 is the tcpmon port monitor directed to 8080 @ axis/services/activationCoordinator)
The coordination context which is being in the soap request header while invoking the web service operation is:
<wscoor:CoordinationContext soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
<wscoor:Identifier>uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</wscoor:Identifier>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
<wscoor:RegistrationService>
<wsa:Address xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/axis/services/registrationCoordinator</wsa:Address>
<wsa:ReferenceProperties xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<ns4:CallbackRef xmlns:ns4="http://ws.apache.org/kandula">uuid:eea888f0-5240-11dd-b7e1-e65028b28b48</ns4:CallbackRef>
</wsa:ReferenceProperties>
</wscoor:RegistrationService>
</wscoor:CoordinationContext>
Now after this is done, you suggested that the WAS should register the Kandula registration service (which would be I suppose http://localhost:8080/axis/services/registrationCoordinator) , I am not really sure how to achieve this.
Any pointers?
Thanking you in advance.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
Sent: Monday, July 14, 2008 7:43 PM
To: kandula-dev@ws.apache.org
Cc: Pal Chaudhuri, Anshuk (Cognizant)
Subject: RE: Issues while compiling src code
Quoting Anshuk.PalChaudhuri@cognizant.com:
You should be able to use either coordinator. To use a different coordinator
with the Kandula provided toy TM, you can specify the end point of the
activation service to the begin() method.
Note that the coordination context is created by the activation service.
There is another Coordinator service which handles termination. Please
make sure that you are not sending the CreateCoordinationContext message to
the coordinator endpoint.
If you are using the Kandula activation service, then once the coordination
context has been created and the service on WAS is invoked with the coordination
context, WAS should register with the Kandula registration service.
If you are using WAS activation service, then service on WAS should register
with the registration service on WAS.
Let me know whether you get this far.
Please post your questions on kandula-dev so that they get archived.
Thanks,
-- dasarath
> That is exactly what I am trying to achieve using the Kandula client. And
> that's where I am facing the issues L L
>
> Since I am using a Kandula client, the coordination context should be created
> using web service activationCoordinator deployed on tomcat
> àhttp://localhost:8080/axis/services/activationCoordinator, which is actually
> being created and also being sent in the soap header in the soap request
> while the web service on WAS. (PFA kandula-soap-request.xml)
>
> But then again, this transaction details is not working as the revoking part
> is not working properly.
>
>
>
> Then I thought may be the coordination service of WAS should be invoked which
> lies at http://localhost:9080/_IBMSYSAPP/wsat/services/Coordinator (which
> might create the correct coordination context as required like attached à
> WAS-Client-SOAP-request.xml ) but the request which is being sent to invoke
> the coordinator service is not correct. (PFA the errors.txt)
>
>
>
> Thanks.
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
>
>
> -----Original Message-----
> From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> Sent: Friday, July 11, 2008 7:43 PM
> To: Pal Chaudhuri, Anshuk (Cognizant)
> Subject: RE: Issues while compiling src code
>
>
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
>
>
> Yes, this can be done. You can replace either the WAS box or MSFT box with
>
> Axis+Kandula or add Axis+Kandula as another branch of the same activity
> along
>
> with the other two.
>
>
>
> If your resource is deployed in WAS then Kandula is only a client. Kandula
>
> will create a coordination context and then attach it to all invocations
>
> of your service methods on WAS and then finally terminate that transaction
>
> using WS-AT. Of course, we could add other resources to this activity
> possibly
>
> residing outside of WAS. How your resource is configured and how the web
> service
>
> is setup in WAS that you have to look at WAS docs. I would recommend that
> you
>
> take the same WSDL of this interop scenario and try to generate a Kandula
>
> client. That way you can follow the same instructions on setting up the WAS
> end.
>
>
>
> The other scenario is, WAS acts as the client and resource is deployed
> inside
>
> Geronimo with Kandula providing the interfacing between WS-AT and JTA. You
> can
>
> even test this with out involving Geronimo by using the toy TM that we have
>
> provided. Since we are only concerned about WS-AT, JTA side is not
> important.
>
>
>
> I have tried inter-op testing Kandula with IBM implementation but had to
> stop
>
> it due to a bug in their code.
>
>
>
> Happy testing!
>
> -- dasarath
>
>
>
>
>
>
>
>
>
> >
>
> > Thanks Dasarath for the input.
>
>
>
> >
>
> >
>
>
>
> >
>
> > I am not trying to integrate Kandula with WAS as Kandula is being done
>
> > today with Geronimo. That is not my objective.
>
> >
>
> >
>
>
>
> >
>
> > The objective is:
>
> >
>
> >
>
>
>
> >
>
> > Web Service Transaction Interoperability (Kandula Implementation and WAS
>
> > Implementation of Web Service Transaction)
>
> >
>
> >
>
>
>
> >
>
> > Web Service Client (build with axis generated stubs and using Kandula to
>
> > attach transaction details) ----------------------------> Web Service on
>
> > WAS (which does some insertion into database) Do you think this is
>
> > feasible or not?
>
> >
>
> >
>
>
>
> >
>
> > The resources are defined (say datasource) within the WAS Container. Now
>
> > the question would be do I need to expose these resources (XAResource)
>
> > deployed within WAS using Kandula?
>
>
>
> >
>
> >
>
>
>
> >
>
> > I was having a look somewhere
>
> > (http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
>
> > o/0707_lo.html ) where there are MS Web Service Clients (Web Service
>
> > Transactions configured) are interoperating with Web Services deployed
>
> > on WAS and the transaction management is happening. That is an excellent
>
> > case of web service transaction interoperability. What I am wondering is
>
> > if that is possible, then why not what I am trying out, where the client
>
> > would be using axis (instead of Microsoft) and the transaction
>
> > configuration would be done using Kandula.
>
> >
>
> >
>
>
>
> >
>
> > Let me know if I am not clear.
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > Regards,
>
> >
>
> > Anshuk Pal Chaudhuri
>
> >
>
> >
>
>
>
> >
>
> > -----Original Message-----
>
> > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
>
>
> > Sent: Thursday, July 10, 2008 10:55 PM
>
> > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Cc: kandula-dev@ws.apache.org
>
> > Subject: RE: Issues while compiling src code
>
> >
>
> >
>
>
>
> >
>
> > Quoting Anshuk <An...@cognizant.com>:
>
> >
>
> >
>
>
>
> >
>
> > Interfacing JTA with WS-AT is completely different from
>
>
>
> >
>
> > looking at web services interoperability between different
>
> > implementations
>
> >
>
> > like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
>
> > this point.
>
> >
>
> >
>
>
>
> >
>
> > If you want to expose some XAResource deployed inside WAS using Kandula,
>
> >
>
> > then you need to interface Kandula with the native JTA implementation in
>
> > WAS.
>
> >
>
> > What Kandula does is it creates a JTA transaction whenever it sees a new
>
> >
>
> >
>
> > coordination context and attaches it to the thread that would execute
>
>
>
> >
>
> > the web service. From there on, the native JTA implementation takes care
>
> >
>
> > of the rest. In the absence of such a native JTA implementation we have
>
> > provided
>
> >
>
> > a toy JTA implementation that could be used but this is mainly for
>
> > testing.
>
> >
>
> > When the WS-AT protocol attempts to terminate the activity, Kandula will
>
> >
>
> > use its private interface with the native JTA implementation to
>
> > terminate
>
> >
>
> > the JTA transaction that was created earlier. Here Kandula uses the
>
> > two-phase
>
> >
>
> > commit protocol.
>
> >
>
> >
>
>
>
> >
>
> > However, the JTA API is not sufficient to completely handle the two
>
> > phase
>
> >
>
> > commit protocol that is used to terminate a transaction. For example, if
>
> >
>
> > you look at how Kandula has been interfaced with Geronimo, you would see
>
> >
>
> > that we have used an API exposed by the Geronimo transaction manager
>
> > which
>
> >
>
> > is non-standard. In the case of WAS it is not possible to study their
>
> >
>
> > internal API s to do the same. In short, it is not possible to do what
>
> > we have
>
> >
>
> > done with Geronimo with WAS.
>
> >
>
> >
>
>
>
> >
>
> > You could however, try the following:
>
> >
>
> > 1) Use a Kandula client with WAS server.
>
> >
>
> > 2) WAS client with Kandula server (in Geronimo server or Tomcat +
>
> > Geronimo
>
> >
>
> > transaction manager)
>
> >
>
> >
>
>
>
> >
>
> > Thanks,
>
> >
>
> > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > > Thanks Dasarath for the input.
>
> >
>
> > >
>
>
>
> >
>
> > > As I mentioned earlier, I did try out the WAS-WAS and it is working
>
> > fine. I
>
> >
>
> > > also tried out the Kandula-Kandula (as you mentioned about the banking
>
> >
>
> > > example)and it is also working fine.
>
> >
>
> > > Now w.r.t. the sceanrio which I described earlier, the first case
>
> > (WAS-WAS),
>
> >
>
> > > the datasource is defined within the WAS container, so the application
>
> > is
>
> >
>
> > > taking care of the rollback.
>
> >
>
> > > In the second case, (correct me if I am wrong), the resources are
>
> > defined in
>
> >
>
> > > the BankOneDBMS which implements NamedXAResource so the resources are
>
> >
>
> > > enlisted there only and the commit and rollback are managed explicitly
>
> >
>
> > > (using the Transaction Manager of Geronimo)
>
> >
>
> > >
>
>
>
> >
>
> > > Now when I am trying to incorporate Kandula (at the client side) and
>
> > WAS (at
>
> >
>
> > > the server side, where the web service is deployed), the transaction
>
> >
>
> > > management is not taking place as expected.
>
> >
>
> > >
>
>
>
> >
>
> > > The co-ordination context (within the soap request) that I have sent
>
> > across
>
> >
>
> > > from WAS (when client) and Kandula (when client) seems to be
>
> > different.
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > In case of kandula (being client), the standalone client uses the
>
> > stubs
>
> >
>
> > > (generated from axis wsdl2java) and a client handler does the
>
> > following:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > public void invoke(MessageContext mc) throws AxisFault {
>
> >
>
> > > System.out.println("handler");
>
> >
>
> > > CoordinationContext ctx;
>
> >
>
> > > CoordinationContextType ctxType;
>
> >
>
> > > try {
>
> >
>
> > > ActivationStub stub = new
>
> > ActivationStub(new EndpointReference(
>
> >
>
> > >
>
> > "http://localhost:8081/axis/services/activationCoordinator"));
>
> >
>
> > > ctx =
>
> > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> >
>
> > >
>
>
>
> >
>
> > > }catch (Exception re) {
>
> >
>
> > > try {
>
> >
>
> > > ctx =
>
> > null;
>
> >
>
> > > } catch
>
> > (Exception e) {
>
> >
>
> > >
>
> > e.printStackTrace();
>
> >
>
> > >
>
> > }
>
> >
>
> > > }
>
> >
>
> > > }
>
> >
>
> > >
>
>
>
> >
>
> > > I am not sure where I am going wrong.
>
> >
>
> > >
>
>
>
> >
>
> > > Can you guide me on this.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks.
>
> >
>
> > >
>
>
>
> >
>
> > > Regards,
>
> >
>
> > > Anshuk
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Dasarath Weeratunge-3 wrote:
>
> >
>
> > > >
>
>
>
> >
>
> > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> > > >
>
>
>
> >
>
> > > > Anshuk,
>
> >
>
> > > >
>
>
>
> >
>
> > > > Have you looked at the banking example? If you are going to
>
> >
>
> > > > use WAS on one end and Kandula on the other end I would very much
>
> >
>
> > > > like to see what the result is going to be. I would recommend
>
> >
>
> > > > that you first try WAS-WAS and Kandula-Kandula before attempting
>
> >
>
> > > > WAS-Kandula.
>
> >
>
> > > >
>
>
>
> >
>
> > > >> I did have a look at the documentation, but I am not exactly sure
>
> > what
>
> >
>
> > > >> needs to be done.
>
> >
>
> > > >
>
>
>
> >
>
> > > > This is unfortunately a little too gernal to answer over a mailing
>
> > list.
>
> >
>
> > > > Please be more specific/discrete about what you are trying to do.
>
> > For
>
> >
>
> > > > example,
>
> >
>
> > > > if you say you tried this and got this error, then we can tell you
>
> > why and
>
> >
>
> > > > what you need to do differently.
>
> >
>
> > > >
>
>
>
> >
>
> > > > Thanks,
>
> >
>
> > > > -- dasarath
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >> Hi Hannes,
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Thanks for your input.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> I did try out using the atomic transaction that comes with the IBM
>
> > WAS
>
> >
>
> > > >> 6.0. The web service would insert some values in a database. The
>
> > web
>
> >
>
> > > >> service client was built using the stubs generated by the IBM SOAP
>
> >
>
> > > >> Engine WSDL2Java and configured in such a way so that it would send
>
> >
>
> > > >> atomic transaction details in the soap envelope. So, I tested a
>
> > good
>
> >
>
> > > >> scenario and the values got inserted in the table. While testing
>
> > the
>
> >
>
> > > >> error scenario, in the web service after the part of the which does
>
> > the
>
> >
>
> > > >> insertion, I threw a runtime exception explicitly and when I
>
> > checked the
>
> >
>
> > > >> tables, the values were not inserted.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Now I intend to do a similar scenario using Apache Kandula at the
>
> > client
>
> >
>
> > > >> side. The same web service (deployed on WAS) would be used, but
>
> > the
>
> >
>
> > > >> client would now send the soap request using apache Kandula and the
>
> >
>
> > > >> necessary transaction details (within the soap header) would be
>
> > sent.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> I did have a look at the documentation, but I am not exactly sure
>
> > what
>
> >
>
> > > >> needs to be done.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Can you help/guide me in testing the above.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Thanking you in advance.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Regards,
>
> >
>
> > > >> Anshuk Pal Chaudhuri
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> -----Original Message-----
>
> >
>
> > > >> From: Hannes Erven [mailto:herven@apache.org]
>
> >
>
> > > >
>
>
>
> >
>
> > > >> Sent: Sunday, June 29, 2008 4:37 AM
>
> >
>
> > > >> To: kandula-dev@ws.apache.org
>
> >
>
> > > >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > > >> Subject: Re: Issues while compiling src code
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Hi Anshuk,
>
> >
>
> > > >>
>
>
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> > What I am not clear is the flow how exactly the client creates
>
> > the
>
> >
>
> > > >> > co-ordination context and so on.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> I'm not sure what you are exactly looking for and what you already
>
> > know
>
> >
>
> > > >
>
>
>
> >
>
> > > >> or have read.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> As a general starting point, I suggest you have a look at the
>
> >
>
> > > >
>
>
>
> >
>
> > > >> WS-Coordination specification and also WS-AtomicTransaction or
>
> >
>
> > > >
>
>
>
> >
>
> > > >> WS-BusinessActivity, whatever transaction type you are interested
>
> > in.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> In the source code, at the Kandula server it all starts at
>
> >
>
> > > >
>
>
>
> >
>
> > > >>
>
> > org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
>
> >
>
> > > >> text
>
> >
>
> > > >
>
>
>
> >
>
> > > >> , this is where the call from the client is received. From there,
>
> > the
>
> >
>
> > > >
>
>
>
> >
>
> > > >> actual transaction coordinator object is created depending on the
>
> >
>
> > > >
>
>
>
> >
>
> > > >> requested type of transaction.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> If you have further questions or need reading tips, please reply
>
> > with
>
> >
>
> > > >
>
>
>
> >
>
> > > >> more details what you are interested in.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Best regards and thank you for your interest in Kandula,
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> -hannes
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> This e-mail and any files transmitted with it are for the sole use
>
> > of the
>
> >
>
> > > >> intended recipient(s) and may contain confidential and privileged
>
> >
>
> > > >> information.
>
> >
>
> > > >> If you are not the intended recipient, please contact the sender by
>
> > reply
>
> >
>
> > > >> e-mail and destroy all copies of the original message.
>
> >
>
> > > >
>
>
>
> >
>
> > > >> Any unauthorised review, use, disclosure, dissemination,
>
> > forwarding,
>
> >
>
> > > >> printing
>
> >
>
> > > >> or copying of this email or any action taken in reliance on this
>
> > e-mail
>
> >
>
> > > >> is
>
> >
>
> > > >> strictly
>
> >
>
> > > >
>
>
>
> >
>
> > > >> prohibited and may be unlawful.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >>
>
> > ---------------------------------------------------------------------
>
> >
>
> > > >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > > >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > > >>
>
>
>
> >
>
> > > >>
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
> > ---------------------------------------------------------------------
>
> >
>
> > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > --
>
>
>
> >
>
> > > View this message in context:
>
> >
>
> > >
>
> > http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
>
> > 3.html
>
> >
>
> > > Sent from the Kandula mailing list archive at Nabble.com.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > ---------------------------------------------------------------------
>
> >
>
> > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
> >
>
> > This e-mail and any files transmitted with it are for the sole use of the
>
> > intended recipient(s) and may contain confidential and privileged
>
> > information.
>
> > If you are not the intended recipient, please contact the sender by reply
>
> > e-mail and destroy all copies of the original message.
>
>
>
> > Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing
>
> > or copying of this email or any action taken in reliance on this e-mail is
>
> > strictly
>
>
>
> > prohibited and may be unlawful.
>
>
>
>
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing
> or copying of this email or any action taken in reliance on this e-mail is
> strictly
> prohibited and may be unlawful.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
RE: Issues while compiling src code
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Anshuk.PalChaudhuri@cognizant.com:
You should be able to use either coordinator. To use a different coordinator
with the Kandula provided toy TM, you can specify the end point of the
activation service to the begin() method.
Note that the coordination context is created by the activation service.
There is another Coordinator service which handles termination. Please
make sure that you are not sending the CreateCoordinationContext message to
the coordinator endpoint.
If you are using the Kandula activation service, then once the coordination
context has been created and the service on WAS is invoked with the coordination
context, WAS should register with the Kandula registration service.
If you are using WAS activation service, then service on WAS should register
with the registration service on WAS.
Let me know whether you get this far.
Please post your questions on kandula-dev so that they get archived.
Thanks,
-- dasarath
> That is exactly what I am trying to achieve using the Kandula client. And
> that's where I am facing the issues L L
>
> Since I am using a Kandula client, the coordination context should be created
> using web service activationCoordinator deployed on tomcat
> àhttp://localhost:8080/axis/services/activationCoordinator, which is actually
> being created and also being sent in the soap header in the soap request
> while the web service on WAS. (PFA kandula-soap-request.xml)
>
> But then again, this transaction details is not working as the revoking part
> is not working properly.
>
>
>
> Then I thought may be the coordination service of WAS should be invoked which
> lies at http://localhost:9080/_IBMSYSAPP/wsat/services/Coordinator (which
> might create the correct coordination context as required like attached à
> WAS-Client-SOAP-request.xml ) but the request which is being sent to invoke
> the coordinator service is not correct. (PFA the errors.txt)
>
>
>
> Thanks.
>
>
>
> Regards,
>
> Anshuk Pal Chaudhuri
>
>
>
>
>
> -----Original Message-----
> From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
> Sent: Friday, July 11, 2008 7:43 PM
> To: Pal Chaudhuri, Anshuk (Cognizant)
> Subject: RE: Issues while compiling src code
>
>
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
>
>
> Yes, this can be done. You can replace either the WAS box or MSFT box with
>
> Axis+Kandula or add Axis+Kandula as another branch of the same activity
> along
>
> with the other two.
>
>
>
> If your resource is deployed in WAS then Kandula is only a client. Kandula
>
> will create a coordination context and then attach it to all invocations
>
> of your service methods on WAS and then finally terminate that transaction
>
> using WS-AT. Of course, we could add other resources to this activity
> possibly
>
> residing outside of WAS. How your resource is configured and how the web
> service
>
> is setup in WAS that you have to look at WAS docs. I would recommend that
> you
>
> take the same WSDL of this interop scenario and try to generate a Kandula
>
> client. That way you can follow the same instructions on setting up the WAS
> end.
>
>
>
> The other scenario is, WAS acts as the client and resource is deployed
> inside
>
> Geronimo with Kandula providing the interfacing between WS-AT and JTA. You
> can
>
> even test this with out involving Geronimo by using the toy TM that we have
>
> provided. Since we are only concerned about WS-AT, JTA side is not
> important.
>
>
>
> I have tried inter-op testing Kandula with IBM implementation but had to
> stop
>
> it due to a bug in their code.
>
>
>
> Happy testing!
>
> -- dasarath
>
>
>
>
>
>
>
>
>
> >
>
> > Thanks Dasarath for the input.
>
>
>
> >
>
> >
>
>
>
> >
>
> > I am not trying to integrate Kandula with WAS as Kandula is being done
>
> > today with Geronimo. That is not my objective.
>
> >
>
> >
>
>
>
> >
>
> > The objective is:
>
> >
>
> >
>
>
>
> >
>
> > Web Service Transaction Interoperability (Kandula Implementation and WAS
>
> > Implementation of Web Service Transaction)
>
> >
>
> >
>
>
>
> >
>
> > Web Service Client (build with axis generated stubs and using Kandula to
>
> > attach transaction details) ----------------------------> Web Service on
>
> > WAS (which does some insertion into database) Do you think this is
>
> > feasible or not?
>
> >
>
> >
>
>
>
> >
>
> > The resources are defined (say datasource) within the WAS Container. Now
>
> > the question would be do I need to expose these resources (XAResource)
>
> > deployed within WAS using Kandula?
>
>
>
> >
>
> >
>
>
>
> >
>
> > I was having a look somewhere
>
> > (http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
>
> > o/0707_lo.html ) where there are MS Web Service Clients (Web Service
>
> > Transactions configured) are interoperating with Web Services deployed
>
> > on WAS and the transaction management is happening. That is an excellent
>
> > case of web service transaction interoperability. What I am wondering is
>
> > if that is possible, then why not what I am trying out, where the client
>
> > would be using axis (instead of Microsoft) and the transaction
>
> > configuration would be done using Kandula.
>
> >
>
> >
>
>
>
> >
>
> > Let me know if I am not clear.
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > Regards,
>
> >
>
> > Anshuk Pal Chaudhuri
>
> >
>
> >
>
>
>
> >
>
> > -----Original Message-----
>
> > From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
>
>
>
> > Sent: Thursday, July 10, 2008 10:55 PM
>
> > To: Pal Chaudhuri, Anshuk (Cognizant)
>
> > Cc: kandula-dev@ws.apache.org
>
> > Subject: RE: Issues while compiling src code
>
> >
>
> >
>
>
>
> >
>
> > Quoting Anshuk <An...@cognizant.com>:
>
> >
>
> >
>
>
>
> >
>
> > Interfacing JTA with WS-AT is completely different from
>
>
>
> >
>
> > looking at web services interoperability between different
>
> > implementations
>
> >
>
> > like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
>
> > this point.
>
> >
>
> >
>
>
>
> >
>
> > If you want to expose some XAResource deployed inside WAS using Kandula,
>
> >
>
> > then you need to interface Kandula with the native JTA implementation in
>
> > WAS.
>
> >
>
> > What Kandula does is it creates a JTA transaction whenever it sees a new
>
> >
>
> >
>
> > coordination context and attaches it to the thread that would execute
>
>
>
> >
>
> > the web service. From there on, the native JTA implementation takes care
>
> >
>
> > of the rest. In the absence of such a native JTA implementation we have
>
> > provided
>
> >
>
> > a toy JTA implementation that could be used but this is mainly for
>
> > testing.
>
> >
>
> > When the WS-AT protocol attempts to terminate the activity, Kandula will
>
> >
>
> > use its private interface with the native JTA implementation to
>
> > terminate
>
> >
>
> > the JTA transaction that was created earlier. Here Kandula uses the
>
> > two-phase
>
> >
>
> > commit protocol.
>
> >
>
> >
>
>
>
> >
>
> > However, the JTA API is not sufficient to completely handle the two
>
> > phase
>
> >
>
> > commit protocol that is used to terminate a transaction. For example, if
>
> >
>
> > you look at how Kandula has been interfaced with Geronimo, you would see
>
> >
>
> > that we have used an API exposed by the Geronimo transaction manager
>
> > which
>
> >
>
> > is non-standard. In the case of WAS it is not possible to study their
>
> >
>
> > internal API s to do the same. In short, it is not possible to do what
>
> > we have
>
> >
>
> > done with Geronimo with WAS.
>
> >
>
> >
>
>
>
> >
>
> > You could however, try the following:
>
> >
>
> > 1) Use a Kandula client with WAS server.
>
> >
>
> > 2) WAS client with Kandula server (in Geronimo server or Tomcat +
>
> > Geronimo
>
> >
>
> > transaction manager)
>
> >
>
> >
>
>
>
> >
>
> > Thanks,
>
> >
>
> > -- dasarath
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> > > Thanks Dasarath for the input.
>
> >
>
> > >
>
>
>
> >
>
> > > As I mentioned earlier, I did try out the WAS-WAS and it is working
>
> > fine. I
>
> >
>
> > > also tried out the Kandula-Kandula (as you mentioned about the banking
>
> >
>
> > > example)and it is also working fine.
>
> >
>
> > > Now w.r.t. the sceanrio which I described earlier, the first case
>
> > (WAS-WAS),
>
> >
>
> > > the datasource is defined within the WAS container, so the application
>
> > is
>
> >
>
> > > taking care of the rollback.
>
> >
>
> > > In the second case, (correct me if I am wrong), the resources are
>
> > defined in
>
> >
>
> > > the BankOneDBMS which implements NamedXAResource so the resources are
>
> >
>
> > > enlisted there only and the commit and rollback are managed explicitly
>
> >
>
> > > (using the Transaction Manager of Geronimo)
>
> >
>
> > >
>
>
>
> >
>
> > > Now when I am trying to incorporate Kandula (at the client side) and
>
> > WAS (at
>
> >
>
> > > the server side, where the web service is deployed), the transaction
>
> >
>
> > > management is not taking place as expected.
>
> >
>
> > >
>
>
>
> >
>
> > > The co-ordination context (within the soap request) that I have sent
>
> > across
>
> >
>
> > > from WAS (when client) and Kandula (when client) seems to be
>
> > different.
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > In case of kandula (being client), the standalone client uses the
>
> > stubs
>
> >
>
> > > (generated from axis wsdl2java) and a client handler does the
>
> > following:
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > public void invoke(MessageContext mc) throws AxisFault {
>
> >
>
> > > System.out.println("handler");
>
> >
>
> > > CoordinationContext ctx;
>
> >
>
> > > CoordinationContextType ctxType;
>
> >
>
> > > try {
>
> >
>
> > > ActivationStub stub = new
>
> > ActivationStub(new EndpointReference(
>
> >
>
> > >
>
> > "http://localhost:8081/axis/services/activationCoordinator"));
>
> >
>
> > > ctx =
>
> > stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> >
>
> > >
>
>
>
> >
>
> > > }catch (Exception re) {
>
> >
>
> > > try {
>
> >
>
> > > ctx =
>
> > null;
>
> >
>
> > > } catch
>
> > (Exception e) {
>
> >
>
> > >
>
> > e.printStackTrace();
>
> >
>
> > >
>
> > }
>
> >
>
> > > }
>
> >
>
> > > }
>
> >
>
> > >
>
>
>
> >
>
> > > I am not sure where I am going wrong.
>
> >
>
> > >
>
>
>
> >
>
> > > Can you guide me on this.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Thanks.
>
> >
>
> > >
>
>
>
> >
>
> > > Regards,
>
> >
>
> > > Anshuk
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > Dasarath Weeratunge-3 wrote:
>
> >
>
> > > >
>
>
>
> >
>
> > > > Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> >
>
> > > >
>
>
>
> >
>
> > > > Anshuk,
>
> >
>
> > > >
>
>
>
> >
>
> > > > Have you looked at the banking example? If you are going to
>
> >
>
> > > > use WAS on one end and Kandula on the other end I would very much
>
> >
>
> > > > like to see what the result is going to be. I would recommend
>
> >
>
> > > > that you first try WAS-WAS and Kandula-Kandula before attempting
>
> >
>
> > > > WAS-Kandula.
>
> >
>
> > > >
>
>
>
> >
>
> > > >> I did have a look at the documentation, but I am not exactly sure
>
> > what
>
> >
>
> > > >> needs to be done.
>
> >
>
> > > >
>
>
>
> >
>
> > > > This is unfortunately a little too gernal to answer over a mailing
>
> > list.
>
> >
>
> > > > Please be more specific/discrete about what you are trying to do.
>
> > For
>
> >
>
> > > > example,
>
> >
>
> > > > if you say you tried this and got this error, then we can tell you
>
> > why and
>
> >
>
> > > > what you need to do differently.
>
> >
>
> > > >
>
>
>
> >
>
> > > > Thanks,
>
> >
>
> > > > -- dasarath
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >> Hi Hannes,
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Thanks for your input.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> I did try out using the atomic transaction that comes with the IBM
>
> > WAS
>
> >
>
> > > >> 6.0. The web service would insert some values in a database. The
>
> > web
>
> >
>
> > > >> service client was built using the stubs generated by the IBM SOAP
>
> >
>
> > > >> Engine WSDL2Java and configured in such a way so that it would send
>
> >
>
> > > >> atomic transaction details in the soap envelope. So, I tested a
>
> > good
>
> >
>
> > > >> scenario and the values got inserted in the table. While testing
>
> > the
>
> >
>
> > > >> error scenario, in the web service after the part of the which does
>
> > the
>
> >
>
> > > >> insertion, I threw a runtime exception explicitly and when I
>
> > checked the
>
> >
>
> > > >> tables, the values were not inserted.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Now I intend to do a similar scenario using Apache Kandula at the
>
> > client
>
> >
>
> > > >> side. The same web service (deployed on WAS) would be used, but
>
> > the
>
> >
>
> > > >> client would now send the soap request using apache Kandula and the
>
> >
>
> > > >> necessary transaction details (within the soap header) would be
>
> > sent.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> I did have a look at the documentation, but I am not exactly sure
>
> > what
>
> >
>
> > > >> needs to be done.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Can you help/guide me in testing the above.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Thanking you in advance.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Regards,
>
> >
>
> > > >> Anshuk Pal Chaudhuri
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> -----Original Message-----
>
> >
>
> > > >> From: Hannes Erven [mailto:herven@apache.org]
>
> >
>
> > > >
>
>
>
> >
>
> > > >> Sent: Sunday, June 29, 2008 4:37 AM
>
> >
>
> > > >> To: kandula-dev@ws.apache.org
>
> >
>
> > > >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
>
> >
>
> > > >> Subject: Re: Issues while compiling src code
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Hi Anshuk,
>
> >
>
> > > >>
>
>
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> > What I am not clear is the flow how exactly the client creates
>
> > the
>
> >
>
> > > >> > co-ordination context and so on.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> I'm not sure what you are exactly looking for and what you already
>
> > know
>
> >
>
> > > >
>
>
>
> >
>
> > > >> or have read.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> As a general starting point, I suggest you have a look at the
>
> >
>
> > > >
>
>
>
> >
>
> > > >> WS-Coordination specification and also WS-AtomicTransaction or
>
> >
>
> > > >
>
>
>
> >
>
> > > >> WS-BusinessActivity, whatever transaction type you are interested
>
> > in.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> In the source code, at the Kandula server it all starts at
>
> >
>
> > > >
>
>
>
> >
>
> > > >>
>
> > org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
>
> >
>
> > > >> text
>
> >
>
> > > >
>
>
>
> >
>
> > > >> , this is where the call from the client is received. From there,
>
> > the
>
> >
>
> > > >
>
>
>
> >
>
> > > >> actual transaction coordinator object is created depending on the
>
> >
>
> > > >
>
>
>
> >
>
> > > >> requested type of transaction.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> If you have further questions or need reading tips, please reply
>
> > with
>
> >
>
> > > >
>
>
>
> >
>
> > > >> more details what you are interested in.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> Best regards and thank you for your interest in Kandula,
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> -hannes
>
> >
>
> > > >>
>
>
>
> >
>
> > > >> This e-mail and any files transmitted with it are for the sole use
>
> > of the
>
> >
>
> > > >> intended recipient(s) and may contain confidential and privileged
>
> >
>
> > > >> information.
>
> >
>
> > > >> If you are not the intended recipient, please contact the sender by
>
> > reply
>
> >
>
> > > >> e-mail and destroy all copies of the original message.
>
> >
>
> > > >
>
>
>
> >
>
> > > >> Any unauthorised review, use, disclosure, dissemination,
>
> > forwarding,
>
> >
>
> > > >> printing
>
> >
>
> > > >> or copying of this email or any action taken in reliance on this
>
> > e-mail
>
> >
>
> > > >> is
>
> >
>
> > > >> strictly
>
> >
>
> > > >
>
>
>
> >
>
> > > >> prohibited and may be unlawful.
>
> >
>
> > > >>
>
>
>
> >
>
> > > >>
>
> > ---------------------------------------------------------------------
>
> >
>
> > > >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > > >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > > >>
>
>
>
> >
>
> > > >>
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
> > ---------------------------------------------------------------------
>
> >
>
> > > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > --
>
>
>
> >
>
> > > View this message in context:
>
> >
>
> > >
>
> > http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
>
> > 3.html
>
> >
>
> > > Sent from the Kandula mailing list archive at Nabble.com.
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> > > ---------------------------------------------------------------------
>
> >
>
> > > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>
> >
>
> > > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
> >
>
> > >
>
>
>
> >
>
> > >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
>
>
> >
>
> >
>
> >
>
> > This e-mail and any files transmitted with it are for the sole use of the
>
> > intended recipient(s) and may contain confidential and privileged
>
> > information.
>
> > If you are not the intended recipient, please contact the sender by reply
>
> > e-mail and destroy all copies of the original message.
>
>
>
> > Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing
>
> > or copying of this email or any action taken in reliance on this e-mail is
>
> > strictly
>
>
>
> > prohibited and may be unlawful.
>
>
>
>
>
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing
> or copying of this email or any action taken in reliance on this e-mail is
> strictly
> prohibited and may be unlawful.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by An...@cognizant.com.
Thanks Dasarath for the input.
I am not trying to integrate Kandula with WAS as Kandula is being done
today with Geronimo. That is not my objective.
The objective is:
Web Service Transaction Interoperability (Kandula Implementation and WAS
Implementation of Web Service Transaction)
Web Service Client (build with axis generated stubs and using Kandula to
attach transaction details) ----------------------------> Web Service on
WAS (which does some insertion into database) Do you think this is
feasible or not?
The resources are defined (say datasource) within the WAS Container. Now
the question would be do I need to expose these resources (XAResource)
deployed within WAS using Kandula?
I was having a look somewhere
(http://www.ibm.com/developerworks/websphere/library/techarticles/0707_l
o/0707_lo.html ) where there are MS Web Service Clients (Web Service
Transactions configured) are interoperating with Web Services deployed
on WAS and the transaction management is happening. That is an excellent
case of web service transaction interoperability. What I am wondering is
if that is possible, then why not what I am trying out, where the client
would be using axis (instead of Microsoft) and the transaction
configuration would be done using Kandula.
Let me know if I am not clear.
Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: Dasarath Weeratunge [mailto:dweeratu@purdue.edu]
Sent: Thursday, July 10, 2008 10:55 PM
To: Pal Chaudhuri, Anshuk (Cognizant)
Cc: kandula-dev@ws.apache.org
Subject: RE: Issues while compiling src code
Quoting Anshuk <An...@cognizant.com>:
Interfacing JTA with WS-AT is completely different from
looking at web services interoperability between different
implementations
like Kandula, WAS, MSFT etc. I'm not sure which one you are after at
this point.
If you want to expose some XAResource deployed inside WAS using Kandula,
then you need to interface Kandula with the native JTA implementation in
WAS.
What Kandula does is it creates a JTA transaction whenever it sees a new
coordination context and attaches it to the thread that would execute
the web service. From there on, the native JTA implementation takes care
of the rest. In the absence of such a native JTA implementation we have
provided
a toy JTA implementation that could be used but this is mainly for
testing.
When the WS-AT protocol attempts to terminate the activity, Kandula will
use its private interface with the native JTA implementation to
terminate
the JTA transaction that was created earlier. Here Kandula uses the
two-phase
commit protocol.
However, the JTA API is not sufficient to completely handle the two
phase
commit protocol that is used to terminate a transaction. For example, if
you look at how Kandula has been interfaced with Geronimo, you would see
that we have used an API exposed by the Geronimo transaction manager
which
is non-standard. In the case of WAS it is not possible to study their
internal API s to do the same. In short, it is not possible to do what
we have
done with Geronimo with WAS.
You could however, try the following:
1) Use a Kandula client with WAS server.
2) WAS client with Kandula server (in Geronimo server or Tomcat +
Geronimo
transaction manager)
Thanks,
-- dasarath
> Thanks Dasarath for the input.
>
> As I mentioned earlier, I did try out the WAS-WAS and it is working
fine. I
> also tried out the Kandula-Kandula (as you mentioned about the banking
> example)and it is also working fine.
> Now w.r.t. the sceanrio which I described earlier, the first case
(WAS-WAS),
> the datasource is defined within the WAS container, so the application
is
> taking care of the rollback.
> In the second case, (correct me if I am wrong), the resources are
defined in
> the BankOneDBMS which implements NamedXAResource so the resources are
> enlisted there only and the commit and rollback are managed explicitly
> (using the Transaction Manager of Geronimo)
>
> Now when I am trying to incorporate Kandula (at the client side) and
WAS (at
> the server side, where the web service is deployed), the transaction
> management is not taking place as expected.
>
> The co-ordination context (within the soap request) that I have sent
across
> from WAS (when client) and Kandula (when client) seems to be
different.
>
> In case of kandula (being client), the standalone client uses the
stubs
> (generated from axis wsdl2java) and a client handler does the
following:
>
>
> public void invoke(MessageContext mc) throws AxisFault {
> System.out.println("handler");
> CoordinationContext ctx;
> CoordinationContextType ctxType;
> try {
> ActivationStub stub = new
ActivationStub(new EndpointReference(
>
"http://localhost:8081/axis/services/activationCoordinator"));
> ctx =
stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> }catch (Exception re) {
> try {
> ctx =
null;
> } catch
(Exception e) {
>
e.printStackTrace();
>
}
> }
> }
>
> I am not sure where I am going wrong.
>
> Can you guide me on this.
>
>
> Thanks.
>
> Regards,
> Anshuk
>
>
> Dasarath Weeratunge-3 wrote:
> >
> > Quoting Anshuk.PalChaudhuri@cognizant.com:
> >
> > Anshuk,
> >
> > Have you looked at the banking example? If you are going to
> > use WAS on one end and Kandula on the other end I would very much
> > like to see what the result is going to be. I would recommend
> > that you first try WAS-WAS and Kandula-Kandula before attempting
> > WAS-Kandula.
> >
> >> I did have a look at the documentation, but I am not exactly sure
what
> >> needs to be done.
> >
> > This is unfortunately a little too gernal to answer over a mailing
list.
> > Please be more specific/discrete about what you are trying to do.
For
> > example,
> > if you say you tried this and got this error, then we can tell you
why and
> > what you need to do differently.
> >
> > Thanks,
> > -- dasarath
> >
> >
> >
> >
> >> Hi Hannes,
> >>
> >> Thanks for your input.
> >>
> >> I did try out using the atomic transaction that comes with the IBM
WAS
> >> 6.0. The web service would insert some values in a database. The
web
> >> service client was built using the stubs generated by the IBM SOAP
> >> Engine WSDL2Java and configured in such a way so that it would send
> >> atomic transaction details in the soap envelope. So, I tested a
good
> >> scenario and the values got inserted in the table. While testing
the
> >> error scenario, in the web service after the part of the which does
the
> >> insertion, I threw a runtime exception explicitly and when I
checked the
> >> tables, the values were not inserted.
> >>
> >> Now I intend to do a similar scenario using Apache Kandula at the
client
> >> side. The same web service (deployed on WAS) would be used, but
the
> >> client would now send the soap request using apache Kandula and the
> >> necessary transaction details (within the soap header) would be
sent.
> >>
> >> I did have a look at the documentation, but I am not exactly sure
what
> >> needs to be done.
> >>
> >> Can you help/guide me in testing the above.
> >>
> >> Thanking you in advance.
> >>
> >> Regards,
> >> Anshuk Pal Chaudhuri
> >>
> >> -----Original Message-----
> >> From: Hannes Erven [mailto:herven@apache.org]
> >
> >> Sent: Sunday, June 29, 2008 4:37 AM
> >> To: kandula-dev@ws.apache.org
> >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> >> Subject: Re: Issues while compiling src code
> >>
> >> Hi Anshuk,
> >>
> >>
> >> > What I am not clear is the flow how exactly the client creates
the
> >> > co-ordination context and so on.
> >>
> >> I'm not sure what you are exactly looking for and what you already
know
> >
> >> or have read.
> >>
> >> As a general starting point, I suggest you have a look at the
> >
> >> WS-Coordination specification and also WS-AtomicTransaction or
> >
> >> WS-BusinessActivity, whatever transaction type you are interested
in.
> >>
> >> In the source code, at the Kandula server it all starts at
> >
> >>
org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
> >> text
> >
> >> , this is where the call from the client is received. From there,
the
> >
> >> actual transaction coordinator object is created depending on the
> >
> >> requested type of transaction.
> >>
> >>
> >> If you have further questions or need reading tips, please reply
with
> >
> >> more details what you are interested in.
> >>
> >>
> >> Best regards and thank you for your interest in Kandula,
> >>
> >> -hannes
> >>
> >> This e-mail and any files transmitted with it are for the sole use
of the
> >> intended recipient(s) and may contain confidential and privileged
> >> information.
> >> If you are not the intended recipient, please contact the sender by
reply
> >> e-mail and destroy all copies of the original message.
> >
> >> Any unauthorised review, use, disclosure, dissemination,
forwarding,
> >> printing
> >> or copying of this email or any action taken in reliance on this
e-mail
> >> is
> >> strictly
> >
> >> prohibited and may be unlawful.
> >>
> >>
---------------------------------------------------------------------
> >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
> >>
> >>
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: kandula-dev-help@ws.apache.org
> >
> >
> >
>
> --
> View this message in context:
>
http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p1837975
3.html
> Sent from the Kandula mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
RE: Issues while compiling src code
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Anshuk <An...@cognizant.com>:
Interfacing JTA with WS-AT is completely different from
looking at web services interoperability between different implementations
like Kandula, WAS, MSFT etc. I'm not sure which one you are after at this point.
If you want to expose some XAResource deployed inside WAS using Kandula,
then you need to interface Kandula with the native JTA implementation in WAS.
What Kandula does is it creates a JTA transaction whenever it sees a new
coordination context and attaches it to the thread that would execute
the web service. From there on, the native JTA implementation takes care
of the rest. In the absence of such a native JTA implementation we have provided
a toy JTA implementation that could be used but this is mainly for testing.
When the WS-AT protocol attempts to terminate the activity, Kandula will
use its private interface with the native JTA implementation to terminate
the JTA transaction that was created earlier. Here Kandula uses the two-phase
commit protocol.
However, the JTA API is not sufficient to completely handle the two phase
commit protocol that is used to terminate a transaction. For example, if
you look at how Kandula has been interfaced with Geronimo, you would see
that we have used an API exposed by the Geronimo transaction manager which
is non-standard. In the case of WAS it is not possible to study their
internal API s to do the same. In short, it is not possible to do what we have
done with Geronimo with WAS.
You could however, try the following:
1) Use a Kandula client with WAS server.
2) WAS client with Kandula server (in Geronimo server or Tomcat + Geronimo
transaction manager)
Thanks,
-- dasarath
> Thanks Dasarath for the input.
>
> As I mentioned earlier, I did try out the WAS-WAS and it is working fine. I
> also tried out the Kandula-Kandula (as you mentioned about the banking
> example)and it is also working fine.
> Now w.r.t. the sceanrio which I described earlier, the first case (WAS-WAS),
> the datasource is defined within the WAS container, so the application is
> taking care of the rollback.
> In the second case, (correct me if I am wrong), the resources are defined in
> the BankOneDBMS which implements NamedXAResource so the resources are
> enlisted there only and the commit and rollback are managed explicitly
> (using the Transaction Manager of Geronimo)
>
> Now when I am trying to incorporate Kandula (at the client side) and WAS (at
> the server side, where the web service is deployed), the transaction
> management is not taking place as expected.
>
> The co-ordination context (within the soap request) that I have sent across
> from WAS (when client) and Kandula (when client) seems to be different.
>
> In case of kandula (being client), the standalone client uses the stubs
> (generated from axis wsdl2java) and a client handler does the following:
>
>
> public void invoke(MessageContext mc) throws AxisFault {
> System.out.println("handler");
> CoordinationContext ctx;
> CoordinationContextType ctxType;
> try {
> ActivationStub stub = new ActivationStub(new EndpointReference(
> "http://localhost:8081/axis/services/activationCoordinator"));
> ctx = stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> }catch (Exception re) {
> try {
> ctx = null;
> } catch (Exception e) {
> e.printStackTrace();
> }
> }
> }
>
> I am not sure where I am going wrong.
>
> Can you guide me on this.
>
>
> Thanks.
>
> Regards,
> Anshuk
>
>
> Dasarath Weeratunge-3 wrote:
> >
> > Quoting Anshuk.PalChaudhuri@cognizant.com:
> >
> > Anshuk,
> >
> > Have you looked at the banking example? If you are going to
> > use WAS on one end and Kandula on the other end I would very much
> > like to see what the result is going to be. I would recommend
> > that you first try WAS-WAS and Kandula-Kandula before attempting
> > WAS-Kandula.
> >
> >> I did have a look at the documentation, but I am not exactly sure what
> >> needs to be done.
> >
> > This is unfortunately a little too gernal to answer over a mailing list.
> > Please be more specific/discrete about what you are trying to do. For
> > example,
> > if you say you tried this and got this error, then we can tell you why and
> > what you need to do differently.
> >
> > Thanks,
> > -- dasarath
> >
> >
> >
> >
> >> Hi Hannes,
> >>
> >> Thanks for your input.
> >>
> >> I did try out using the atomic transaction that comes with the IBM WAS
> >> 6.0. The web service would insert some values in a database. The web
> >> service client was built using the stubs generated by the IBM SOAP
> >> Engine WSDL2Java and configured in such a way so that it would send
> >> atomic transaction details in the soap envelope. So, I tested a good
> >> scenario and the values got inserted in the table. While testing the
> >> error scenario, in the web service after the part of the which does the
> >> insertion, I threw a runtime exception explicitly and when I checked the
> >> tables, the values were not inserted.
> >>
> >> Now I intend to do a similar scenario using Apache Kandula at the client
> >> side. The same web service (deployed on WAS) would be used, but the
> >> client would now send the soap request using apache Kandula and the
> >> necessary transaction details (within the soap header) would be sent.
> >>
> >> I did have a look at the documentation, but I am not exactly sure what
> >> needs to be done.
> >>
> >> Can you help/guide me in testing the above.
> >>
> >> Thanking you in advance.
> >>
> >> Regards,
> >> Anshuk Pal Chaudhuri
> >>
> >> -----Original Message-----
> >> From: Hannes Erven [mailto:herven@apache.org]
> >
> >> Sent: Sunday, June 29, 2008 4:37 AM
> >> To: kandula-dev@ws.apache.org
> >> Cc: Pal Chaudhuri, Anshuk (Cognizant)
> >> Subject: Re: Issues while compiling src code
> >>
> >> Hi Anshuk,
> >>
> >>
> >> > What I am not clear is the flow how exactly the client creates the
> >> > co-ordination context and so on.
> >>
> >> I'm not sure what you are exactly looking for and what you already know
> >
> >> or have read.
> >>
> >> As a general starting point, I suggest you have a look at the
> >
> >> WS-Coordination specification and also WS-AtomicTransaction or
> >
> >> WS-BusinessActivity, whatever transaction type you are interested in.
> >>
> >> In the source code, at the Kandula server it all starts at
> >
> >> org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
> >> text
> >
> >> , this is where the call from the client is received. From there, the
> >
> >> actual transaction coordinator object is created depending on the
> >
> >> requested type of transaction.
> >>
> >>
> >> If you have further questions or need reading tips, please reply with
> >
> >> more details what you are interested in.
> >>
> >>
> >> Best regards and thank you for your interest in Kandula,
> >>
> >> -hannes
> >>
> >> This e-mail and any files transmitted with it are for the sole use of the
> >> intended recipient(s) and may contain confidential and privileged
> >> information.
> >> If you are not the intended recipient, please contact the sender by reply
> >> e-mail and destroy all copies of the original message.
> >
> >> Any unauthorised review, use, disclosure, dissemination, forwarding,
> >> printing
> >> or copying of this email or any action taken in reliance on this e-mail
> >> is
> >> strictly
> >
> >> prohibited and may be unlawful.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
> >>
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: kandula-dev-help@ws.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p18379753.html
> Sent from the Kandula mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by Anshuk <An...@cognizant.com>.
Hi Dasarath,
For your reference,
The soap request that is being sent while using kandula is attached
request.xml (which is not working) and the one which is working using the
WAS is the client is SOAP-REQ-WS1.xml
Can you have a look at them.
Thanks.
Regards,
Anshuk
Anshuk wrote:
>
> Thanks Dasarath for the input.
>
> As I mentioned earlier, I did try out the WAS-WAS and it is working fine.
> I also tried out the Kandula-Kandula (as you mentioned about the banking
> example)and it is also working fine.
> Now w.r.t. the sceanrio which I described earlier, the first case
> (WAS-WAS), the datasource is defined within the WAS container, so the
> application is taking care of the rollback.
> In the second case, (correct me if I am wrong), the resources are defined
> in the BankOneDBMS which implements NamedXAResource so the resources are
> enlisted there only and the commit and rollback are managed explicitly
> (using the Transaction Manager of Geronimo)
>
> Now when I am trying to incorporate Kandula (at the client side) and WAS
> (at the server side, where the web service is deployed), the transaction
> management is not taking place as expected.
>
> The co-ordination context (within the soap request) that I have sent
> across from WAS (when client) and Kandula (when client) seems to be
> different.
>
> In case of kandula (being client), the standalone client uses the stubs
> (generated from axis wsdl2java) and a client handler does the following:
>
>
> public void invoke(MessageContext mc) throws AxisFault {
> System.out.println("handler");
> CoordinationContext ctx;
> CoordinationContextType ctxType;
> try {
> ActivationStub stub = new ActivationStub(new EndpointReference(
> "http://localhost:8081/axis/services/activationCoordinator"));
> ctx =
> stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
>
> }catch (Exception re) {
> try {
> ctx = null;
> } catch (Exception e) {
> e.printStackTrace();
> }
> }
> }
>
> I am not sure where I am going wrong.
>
> Can you guide me on this.
>
>
> Thanks.
>
> Regards,
> Anshuk
>
>
> Dasarath Weeratunge-3 wrote:
>>
>> Quoting Anshuk.PalChaudhuri@cognizant.com:
>>
>> Anshuk,
>>
>> Have you looked at the banking example? If you are going to
>> use WAS on one end and Kandula on the other end I would very much
>> like to see what the result is going to be. I would recommend
>> that you first try WAS-WAS and Kandula-Kandula before attempting
>> WAS-Kandula.
>>
>>> I did have a look at the documentation, but I am not exactly sure what
>>> needs to be done.
>>
>> This is unfortunately a little too gernal to answer over a mailing list.
>> Please be more specific/discrete about what you are trying to do. For
>> example,
>> if you say you tried this and got this error, then we can tell you why
>> and
>> what you need to do differently.
>>
>> Thanks,
>> -- dasarath
>>
>>
>>
>>
>>> Hi Hannes,
>>>
>>> Thanks for your input.
>>>
>>> I did try out using the atomic transaction that comes with the IBM WAS
>>> 6.0. The web service would insert some values in a database. The web
>>> service client was built using the stubs generated by the IBM SOAP
>>> Engine WSDL2Java and configured in such a way so that it would send
>>> atomic transaction details in the soap envelope. So, I tested a good
>>> scenario and the values got inserted in the table. While testing the
>>> error scenario, in the web service after the part of the which does the
>>> insertion, I threw a runtime exception explicitly and when I checked the
>>> tables, the values were not inserted.
>>>
>>> Now I intend to do a similar scenario using Apache Kandula at the client
>>> side. The same web service (deployed on WAS) would be used, but the
>>> client would now send the soap request using apache Kandula and the
>>> necessary transaction details (within the soap header) would be sent.
>>>
>>> I did have a look at the documentation, but I am not exactly sure what
>>> needs to be done.
>>>
>>> Can you help/guide me in testing the above.
>>>
>>> Thanking you in advance.
>>>
>>> Regards,
>>> Anshuk Pal Chaudhuri
>>>
>>> -----Original Message-----
>>> From: Hannes Erven [mailto:herven@apache.org]
>>
>>> Sent: Sunday, June 29, 2008 4:37 AM
>>> To: kandula-dev@ws.apache.org
>>> Cc: Pal Chaudhuri, Anshuk (Cognizant)
>>> Subject: Re: Issues while compiling src code
>>>
>>> Hi Anshuk,
>>>
>>>
>>> > What I am not clear is the flow how exactly the client creates the
>>> > co-ordination context and so on.
>>>
>>> I'm not sure what you are exactly looking for and what you already know
>>
>>> or have read.
>>>
>>> As a general starting point, I suggest you have a look at the
>>
>>> WS-Coordination specification and also WS-AtomicTransaction or
>>
>>> WS-BusinessActivity, whatever transaction type you are interested in.
>>>
>>> In the source code, at the Kandula server it all starts at
>>
>>> org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
>>> text
>>
>>> , this is where the call from the client is received. From there, the
>>
>>> actual transaction coordinator object is created depending on the
>>
>>> requested type of transaction.
>>>
>>>
>>> If you have further questions or need reading tips, please reply with
>>
>>> more details what you are interested in.
>>>
>>>
>>> Best regards and thank you for your interest in Kandula,
>>>
>>> -hannes
>>>
>>> This e-mail and any files transmitted with it are for the sole use of
>>> the
>>> intended recipient(s) and may contain confidential and privileged
>>> information.
>>> If you are not the intended recipient, please contact the sender by
>>> reply
>>> e-mail and destroy all copies of the original message.
>>
>>> Any unauthorised review, use, disclosure, dissemination, forwarding,
>>> printing
>>> or copying of this email or any action taken in reliance on this e-mail
>>> is
>>> strictly
>>
>>> prohibited and may be unlawful.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>>
>>
>>
>
>
http://www.nabble.com/file/p18381004/request.xml request.xml
http://www.nabble.com/file/p18381004/SOAP-REQ-WS1.xml SOAP-REQ-WS1.xml
--
View this message in context: http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p18381004.html
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
RE: Issues while compiling src code
Posted by Anshuk <An...@cognizant.com>.
Thanks Dasarath for the input.
As I mentioned earlier, I did try out the WAS-WAS and it is working fine. I
also tried out the Kandula-Kandula (as you mentioned about the banking
example)and it is also working fine.
Now w.r.t. the sceanrio which I described earlier, the first case (WAS-WAS),
the datasource is defined within the WAS container, so the application is
taking care of the rollback.
In the second case, (correct me if I am wrong), the resources are defined in
the BankOneDBMS which implements NamedXAResource so the resources are
enlisted there only and the commit and rollback are managed explicitly
(using the Transaction Manager of Geronimo)
Now when I am trying to incorporate Kandula (at the client side) and WAS (at
the server side, where the web service is deployed), the transaction
management is not taking place as expected.
The co-ordination context (within the soap request) that I have sent across
from WAS (when client) and Kandula (when client) seems to be different.
In case of kandula (being client), the standalone client uses the stubs
(generated from axis wsdl2java) and a client handler does the following:
public void invoke(MessageContext mc) throws AxisFault {
System.out.println("handler");
CoordinationContext ctx;
CoordinationContextType ctxType;
try {
ActivationStub stub = new ActivationStub(new EndpointReference(
"http://localhost:8081/axis/services/activationCoordinator"));
ctx = stub.createCoordinationContext(ATCoordinator.COORDINATION_TYPE_ID);
}catch (Exception re) {
try {
ctx = null;
} catch (Exception e) {
e.printStackTrace();
}
}
}
I am not sure where I am going wrong.
Can you guide me on this.
Thanks.
Regards,
Anshuk
Dasarath Weeratunge-3 wrote:
>
> Quoting Anshuk.PalChaudhuri@cognizant.com:
>
> Anshuk,
>
> Have you looked at the banking example? If you are going to
> use WAS on one end and Kandula on the other end I would very much
> like to see what the result is going to be. I would recommend
> that you first try WAS-WAS and Kandula-Kandula before attempting
> WAS-Kandula.
>
>> I did have a look at the documentation, but I am not exactly sure what
>> needs to be done.
>
> This is unfortunately a little too gernal to answer over a mailing list.
> Please be more specific/discrete about what you are trying to do. For
> example,
> if you say you tried this and got this error, then we can tell you why and
> what you need to do differently.
>
> Thanks,
> -- dasarath
>
>
>
>
>> Hi Hannes,
>>
>> Thanks for your input.
>>
>> I did try out using the atomic transaction that comes with the IBM WAS
>> 6.0. The web service would insert some values in a database. The web
>> service client was built using the stubs generated by the IBM SOAP
>> Engine WSDL2Java and configured in such a way so that it would send
>> atomic transaction details in the soap envelope. So, I tested a good
>> scenario and the values got inserted in the table. While testing the
>> error scenario, in the web service after the part of the which does the
>> insertion, I threw a runtime exception explicitly and when I checked the
>> tables, the values were not inserted.
>>
>> Now I intend to do a similar scenario using Apache Kandula at the client
>> side. The same web service (deployed on WAS) would be used, but the
>> client would now send the soap request using apache Kandula and the
>> necessary transaction details (within the soap header) would be sent.
>>
>> I did have a look at the documentation, but I am not exactly sure what
>> needs to be done.
>>
>> Can you help/guide me in testing the above.
>>
>> Thanking you in advance.
>>
>> Regards,
>> Anshuk Pal Chaudhuri
>>
>> -----Original Message-----
>> From: Hannes Erven [mailto:herven@apache.org]
>
>> Sent: Sunday, June 29, 2008 4:37 AM
>> To: kandula-dev@ws.apache.org
>> Cc: Pal Chaudhuri, Anshuk (Cognizant)
>> Subject: Re: Issues while compiling src code
>>
>> Hi Anshuk,
>>
>>
>> > What I am not clear is the flow how exactly the client creates the
>> > co-ordination context and so on.
>>
>> I'm not sure what you are exactly looking for and what you already know
>
>> or have read.
>>
>> As a general starting point, I suggest you have a look at the
>
>> WS-Coordination specification and also WS-AtomicTransaction or
>
>> WS-BusinessActivity, whatever transaction type you are interested in.
>>
>> In the source code, at the Kandula server it all starts at
>
>> org.apache.kandula.coordinator.CoordinationService#createCoordinationCon
>> text
>
>> , this is where the call from the client is received. From there, the
>
>> actual transaction coordinator object is created depending on the
>
>> requested type of transaction.
>>
>>
>> If you have further questions or need reading tips, please reply with
>
>> more details what you are interested in.
>>
>>
>> Best regards and thank you for your interest in Kandula,
>>
>> -hannes
>>
>> This e-mail and any files transmitted with it are for the sole use of the
>> intended recipient(s) and may contain confidential and privileged
>> information.
>> If you are not the intended recipient, please contact the sender by reply
>> e-mail and destroy all copies of the original message.
>
>> Any unauthorised review, use, disclosure, dissemination, forwarding,
>> printing
>> or copying of this email or any action taken in reliance on this e-mail
>> is
>> strictly
>
>> prohibited and may be unlawful.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Issues-while-compiling-src-code-tp18028466p18379753.html
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org