You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Benjamin Schmeling <Be...@gmx.de> on 2006/05/20 12:20:24 UTC
WSBA, Volatile2PC
Hi,
I have questions on two features of WS-Transactions:
Will Kandula for Axis 1.x support WS-BA in the near future (or is
this extension only planned for Axis2)?
How can I use Volatile2PC instead of Durable2PC with Kandula?
Thanks,
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: MSFT enpoints for WS-AT/C
Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi,
http://mssoapinterop.org/ilab/
Seems the endpoint are still up..
Enjoy :)
Thanks,
~Thilina
On 5/21/06, Dasarath Weeratunge <dw...@purdue.edu> wrote:
>
> Hi Thilina,
>
> could you please check whether those MSFT endpoints are still up (or get
> them
> up using your contacts:)) and post the links to the mailing list? I could
> not
> locate the earlier posts on this in my mailbox:(
>
> thanks,
> --dasarath
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/
http://www.bloglines.com/blog/Thilina
Re: MSFT enpoints for WS-AT/C
Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi,
http://mssoapinterop.org/ilab/
Seems the endpoint are still up..
Enjoy :)
Thanks,
~Thilina
On 5/21/06, Dasarath Weeratunge <dw...@purdue.edu> wrote:
>
> Hi Thilina,
>
> could you please check whether those MSFT endpoints are still up (or get
> them
> up using your contacts:)) and post the links to the mailing list? I could
> not
> locate the earlier posts on this in my mailbox:(
>
> thanks,
> --dasarath
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/
http://www.bloglines.com/blog/Thilina
MSFT enpoints for WS-AT/C
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Hi Thilina,
could you please check whether those MSFT endpoints are still up (or get them
up using your contacts:)) and post the links to the mailing list? I could not
locate the earlier posts on this in my mailbox:(
thanks,
--dasarath
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
MSFT enpoints for WS-AT/C
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Hi Thilina,
could you please check whether those MSFT endpoints are still up (or get them
up using your contacts:)) and post the links to the mailing list? I could not
locate the earlier posts on this in my mailbox:(
thanks,
--dasarath
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: WSBA, Volatile2PC
Posted by Thilina Gunarathne <cs...@gmail.com>.
Great...
Axis2 1.0 is released and now it's stable enough... With that we are hoping
to do a Kandula2 release in around July.. Kandula2 works fine for simple
things at this moment...Currently It uses a resource based generic
participant model opposed to the j2ee participants in Kandula1.
Waiting to have your WS-BA impl integrated to Kandula...
~Thilina
On 5/20/06, Hannes Erven <ha...@erven.at> wrote:
>
> Hi folks,
>
>
> > at the moment Hannes is working on a BA implementation for Axis2. all
> this
> > depends on the need. if there are forks who want BA for Kandula1, we
> will do a
> > port, otherwise all future work will be on Axis2.
>
> In fact, Georg and I are currently working on an Kandula_1
> implementation of WS-BA since Axis2 and hence Kandula2 didn't seem
> reasonably stable at the time of our decision.
> We got activiation and registration up and running and are currently
> working on the protocol implementation and custom extensions.
>
> Having said that, it seems to me that a port to Kandula_2 won't be a big
> challenge: the protocol specific parts are seperated from the web
> service/axis specific parts, so all we'd need are some extensions of the
> kandula2 services and it's done.
>
>
>
> -hannes
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/
http://www.bloglines.com/blog/Thilina
Re: WSBA, Volatile2PC
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Please keep sending patches - once the current committers are ready to
vote you in you'll have write access directly.
Keeping another private repo is against the community centric
development model that Apache projects follow- all work is open and in
the community.
Sanjiva.
On Sun, 2006-05-21 at 12:07 +0200, Hannes Erven wrote:
> Hi Dasarath,
>
>
> > if you are generating stubs for WS-BA using wsdl/xsd please send in the
> > wsdl/xsd so that we can add it in as a test case for axis2. at the moment axis2
> > 1.0 does not generate code for kandula1 wsdl/xsd.
>
> Yes, we've modified the official WS-BA wsdl file (it contains errors
> anyways) and added a maven task to generate BA stubs. (We've just c&p'd
> the Coord/AT sections... works fine!)
>
> I attach the XSD/WSDL files, please place them in
> kandula\branches\Kandula_1\src\schema .
> Also attached is the updated maven.xml that includes the new BA stub
> generating task.
>
> For our development, we've set up a mirroring SVK repository so we can
> check in our work independently from apache.org (where we don't have
> write permission). If you're interested, we can always put online or
> send a patch with a current development snapshot.
>
>
> Best regards,
>
> -hannes
> ---------------------------------------------------------------------
> 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: WSBA, Volatile2PC
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Hannes Erven <ha...@erven.at>:
> For our development, we've set up a mirroring SVK repository so we can
> check in our work independently from apache.org (where we don't have
> write permission). If you're interested, we can always put online or
> send a patch with a current development snapshot.
>
thanks Hannes, I will forward these to axis2 forks. Let us commit your code to
svn. That way all of us can have a look at it. You can send in regular patches
and thilina (:)) and myself can apply them for the time being. I will create a
new branch of Kandula1 so that you can freely modify any part of the Kandula
code.
--dasarath
>
> Best regards,
>
> -hannes
>
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: WSBA, Volatile2PC
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Please keep sending patches - once the current committers are ready to
vote you in you'll have write access directly.
Keeping another private repo is against the community centric
development model that Apache projects follow- all work is open and in
the community.
Sanjiva.
On Sun, 2006-05-21 at 12:07 +0200, Hannes Erven wrote:
> Hi Dasarath,
>
>
> > if you are generating stubs for WS-BA using wsdl/xsd please send in the
> > wsdl/xsd so that we can add it in as a test case for axis2. at the moment axis2
> > 1.0 does not generate code for kandula1 wsdl/xsd.
>
> Yes, we've modified the official WS-BA wsdl file (it contains errors
> anyways) and added a maven task to generate BA stubs. (We've just c&p'd
> the Coord/AT sections... works fine!)
>
> I attach the XSD/WSDL files, please place them in
> kandula\branches\Kandula_1\src\schema .
> Also attached is the updated maven.xml that includes the new BA stub
> generating task.
>
> For our development, we've set up a mirroring SVK repository so we can
> check in our work independently from apache.org (where we don't have
> write permission). If you're interested, we can always put online or
> send a patch with a current development snapshot.
>
>
> Best regards,
>
> -hannes
> ---------------------------------------------------------------------
> 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: WSBA, Volatile2PC
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Hannes Erven <ha...@erven.at>:
> For our development, we've set up a mirroring SVK repository so we can
> check in our work independently from apache.org (where we don't have
> write permission). If you're interested, we can always put online or
> send a patch with a current development snapshot.
>
thanks Hannes, I will forward these to axis2 forks. Let us commit your code to
svn. That way all of us can have a look at it. You can send in regular patches
and thilina (:)) and myself can apply them for the time being. I will create a
new branch of Kandula1 so that you can freely modify any part of the Kandula
code.
--dasarath
>
> Best regards,
>
> -hannes
>
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: WSBA, Volatile2PC
Posted by Hannes Erven <ha...@erven.at>.
Hi Dasarath,
> if you are generating stubs for WS-BA using wsdl/xsd please send in the
> wsdl/xsd so that we can add it in as a test case for axis2. at the moment axis2
> 1.0 does not generate code for kandula1 wsdl/xsd.
Yes, we've modified the official WS-BA wsdl file (it contains errors
anyways) and added a maven task to generate BA stubs. (We've just c&p'd
the Coord/AT sections... works fine!)
I attach the XSD/WSDL files, please place them in
kandula\branches\Kandula_1\src\schema .
Also attached is the updated maven.xml that includes the new BA stub
generating task.
For our development, we've set up a mirroring SVK repository so we can
check in our work independently from apache.org (where we don't have
write permission). If you're interested, we can always put online or
send a patch with a current development snapshot.
Best regards,
-hannes
Re: WSBA, Volatile2PC
Posted by Hannes Erven <ha...@erven.at>.
Hi Dasarath,
> if you are generating stubs for WS-BA using wsdl/xsd please send in the
> wsdl/xsd so that we can add it in as a test case for axis2. at the moment axis2
> 1.0 does not generate code for kandula1 wsdl/xsd.
Yes, we've modified the official WS-BA wsdl file (it contains errors
anyways) and added a maven task to generate BA stubs. (We've just c&p'd
the Coord/AT sections... works fine!)
I attach the XSD/WSDL files, please place them in
kandula\branches\Kandula_1\src\schema .
Also attached is the updated maven.xml that includes the new BA stub
generating task.
For our development, we've set up a mirroring SVK repository so we can
check in our work independently from apache.org (where we don't have
write permission). If you're interested, we can always put online or
send a patch with a current development snapshot.
Best regards,
-hannes
Re: WSBA, Volatile2PC
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
> In fact, Georg and I are currently working on an Kandula_1
> implementation of WS-BA since Axis2 and hence Kandula2 didn't seem
> reasonably stable at the time of our decision.
> We got activiation and registration up and running and are currently
> working on the protocol implementation and custom extensions.
this great news:) I'd say at this point, just get it working on either Kandula1
or Kandula2. once we have the things figured out, we can then worry about the
particular axis flavour. In fact I'm trying to port the current Kandula1 code
to Axis2 these days so that we have a single/stable Kandula code base across
both axis versions.
if you are generating stubs for WS-BA using wsdl/xsd please send in the
wsdl/xsd so that we can add it in as a test case for axis2. at the moment axis2
1.0 does not generate code for kandula1 wsdl/xsd.
Presently, Kandula2 uses the OM directly to generate messages but I'm not too
happy with this approach.
thanks,
--dasarath
> Having said that, it seems to me that a port to Kandula_2 won't be a big
> challenge: the protocol specific parts are seperated from the web
> service/axis specific parts, so all we'd need are some extensions of the
> kandula2 services and it's done.
>
>
>
> -hannes
>
> ---------------------------------------------------------------------
> 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: WSBA, Volatile2PC
Posted by Thilina Gunarathne <cs...@gmail.com>.
Great...
Axis2 1.0 is released and now it's stable enough... With that we are hoping
to do a Kandula2 release in around July.. Kandula2 works fine for simple
things at this moment...Currently It uses a resource based generic
participant model opposed to the j2ee participants in Kandula1.
Waiting to have your WS-BA impl integrated to Kandula...
~Thilina
On 5/20/06, Hannes Erven <ha...@erven.at> wrote:
>
> Hi folks,
>
>
> > at the moment Hannes is working on a BA implementation for Axis2. all
> this
> > depends on the need. if there are forks who want BA for Kandula1, we
> will do a
> > port, otherwise all future work will be on Axis2.
>
> In fact, Georg and I are currently working on an Kandula_1
> implementation of WS-BA since Axis2 and hence Kandula2 didn't seem
> reasonably stable at the time of our decision.
> We got activiation and registration up and running and are currently
> working on the protocol implementation and custom extensions.
>
> Having said that, it seems to me that a port to Kandula_2 won't be a big
> challenge: the protocol specific parts are seperated from the web
> service/axis specific parts, so all we'd need are some extensions of the
> kandula2 services and it's done.
>
>
>
> -hannes
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/
http://www.bloglines.com/blog/Thilina
Re: WSBA, Volatile2PC
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
> In fact, Georg and I are currently working on an Kandula_1
> implementation of WS-BA since Axis2 and hence Kandula2 didn't seem
> reasonably stable at the time of our decision.
> We got activiation and registration up and running and are currently
> working on the protocol implementation and custom extensions.
this great news:) I'd say at this point, just get it working on either Kandula1
or Kandula2. once we have the things figured out, we can then worry about the
particular axis flavour. In fact I'm trying to port the current Kandula1 code
to Axis2 these days so that we have a single/stable Kandula code base across
both axis versions.
if you are generating stubs for WS-BA using wsdl/xsd please send in the
wsdl/xsd so that we can add it in as a test case for axis2. at the moment axis2
1.0 does not generate code for kandula1 wsdl/xsd.
Presently, Kandula2 uses the OM directly to generate messages but I'm not too
happy with this approach.
thanks,
--dasarath
> Having said that, it seems to me that a port to Kandula_2 won't be a big
> challenge: the protocol specific parts are seperated from the web
> service/axis specific parts, so all we'd need are some extensions of the
> kandula2 services and it's done.
>
>
>
> -hannes
>
> ---------------------------------------------------------------------
> 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: WSBA, Volatile2PC
Posted by Hannes Erven <ha...@erven.at>.
Hi folks,
> at the moment Hannes is working on a BA implementation for Axis2. all this
> depends on the need. if there are forks who want BA for Kandula1, we will do a
> port, otherwise all future work will be on Axis2.
In fact, Georg and I are currently working on an Kandula_1
implementation of WS-BA since Axis2 and hence Kandula2 didn't seem
reasonably stable at the time of our decision.
We got activiation and registration up and running and are currently
working on the protocol implementation and custom extensions.
Having said that, it seems to me that a port to Kandula_2 won't be a big
challenge: the protocol specific parts are seperated from the web
service/axis specific parts, so all we'd need are some extensions of the
kandula2 services and it's done.
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: WSBA, Volatile2PC
Posted by Hannes Erven <ha...@erven.at>.
Hi folks,
> at the moment Hannes is working on a BA implementation for Axis2. all this
> depends on the need. if there are forks who want BA for Kandula1, we will do a
> port, otherwise all future work will be on Axis2.
In fact, Georg and I are currently working on an Kandula_1
implementation of WS-BA since Axis2 and hence Kandula2 didn't seem
reasonably stable at the time of our decision.
We got activiation and registration up and running and are currently
working on the protocol implementation and custom extensions.
Having said that, it seems to me that a port to Kandula_2 won't be a big
challenge: the protocol specific parts are seperated from the web
service/axis specific parts, so all we'd need are some extensions of the
kandula2 services and it's done.
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: WSBA, Volatile2PC
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Benjamin Schmeling <Be...@gmx.de>:
> > when you call enlistParticipant on a transaction object, pass 'false'
> > as the first argument.
> >
> > TransactionImpl:
> >
> > public void enlistParticipant(boolean durable,
> > AbstractParticipant participant) throws RemoteException
> >
> >
> Okay, this depends on the participant. When you commit a transaction,
> then there is first a phase where Volatile2PC is done and then a phase
> for Durable2PC automatically. Is that right?
correct.
--dasarath
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: WSBA, Volatile2PC
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Benjamin Schmeling <Be...@gmx.de>:
> > when you call enlistParticipant on a transaction object, pass 'false'
> > as the first argument.
> >
> > TransactionImpl:
> >
> > public void enlistParticipant(boolean durable,
> > AbstractParticipant participant) throws RemoteException
> >
> >
> Okay, this depends on the participant. When you commit a transaction,
> then there is first a phase where Volatile2PC is done and then a phase
> for Durable2PC automatically. Is that right?
correct.
--dasarath
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: WSBA, Volatile2PC
Posted by Benjamin Schmeling <Be...@gmx.de>.
> Quoting Benjamin Schmeling <Be...@gmx.de>:
>
>
>> Will Kandula for Axis 1.x support WS-BA in the near future (or is
>> this extension only planned for Axis2)?
>>
>
> at the moment Hannes is working on a BA implementation for Axis2. all this
> depends on the need. if there are forks who want BA for Kandula1, we will do a
> port, otherwise all future work will be on Axis2.
>
>
>> How can I use Volatile2PC instead of Durable2PC with Kandula?
>>
>
> when you call enlistParticipant on a transaction object, pass 'false'
> as the first argument.
>
> TransactionImpl:
>
> public void enlistParticipant(boolean durable,
> AbstractParticipant participant) throws RemoteException
>
>
Okay, this depends on the participant. When you commit a transaction,
then there is first a phase where Volatile2PC is done and then a phase
for Durable2PC automatically. Is that right?
> when a j2ee participant registers for a transaction, Durable2PC is always used.
> there is no way to change this at present. if you could illaborate your
> scenario I may be able to provide you with a fix.
>
> thanks,
> --dasarath
>
> ---------------------------------------------------------------------
> 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: WSBA, Volatile2PC
Posted by Benjamin Schmeling <Be...@gmx.de>.
> Quoting Benjamin Schmeling <Be...@gmx.de>:
>
>
>> Will Kandula for Axis 1.x support WS-BA in the near future (or is
>> this extension only planned for Axis2)?
>>
>
> at the moment Hannes is working on a BA implementation for Axis2. all this
> depends on the need. if there are forks who want BA for Kandula1, we will do a
> port, otherwise all future work will be on Axis2.
>
>
>> How can I use Volatile2PC instead of Durable2PC with Kandula?
>>
>
> when you call enlistParticipant on a transaction object, pass 'false'
> as the first argument.
>
> TransactionImpl:
>
> public void enlistParticipant(boolean durable,
> AbstractParticipant participant) throws RemoteException
>
>
Okay, this depends on the participant. When you commit a transaction,
then there is first a phase where Volatile2PC is done and then a phase
for Durable2PC automatically. Is that right?
> when a j2ee participant registers for a transaction, Durable2PC is always used.
> there is no way to change this at present. if you could illaborate your
> scenario I may be able to provide you with a fix.
>
> thanks,
> --dasarath
>
> ---------------------------------------------------------------------
> 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: WSBA, Volatile2PC
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Benjamin Schmeling <Be...@gmx.de>:
> Will Kandula for Axis 1.x support WS-BA in the near future (or is
> this extension only planned for Axis2)?
at the moment Hannes is working on a BA implementation for Axis2. all this
depends on the need. if there are forks who want BA for Kandula1, we will do a
port, otherwise all future work will be on Axis2.
>
> How can I use Volatile2PC instead of Durable2PC with Kandula?
when you call enlistParticipant on a transaction object, pass 'false'
as the first argument.
TransactionImpl:
public void enlistParticipant(boolean durable,
AbstractParticipant participant) throws RemoteException
when a j2ee participant registers for a transaction, Durable2PC is always used.
there is no way to change this at present. if you could illaborate your
scenario I may be able to provide you with a fix.
thanks,
--dasarath
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: WSBA, Volatile2PC
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Benjamin Schmeling <Be...@gmx.de>:
> Will Kandula for Axis 1.x support WS-BA in the near future (or is
> this extension only planned for Axis2)?
at the moment Hannes is working on a BA implementation for Axis2. all this
depends on the need. if there are forks who want BA for Kandula1, we will do a
port, otherwise all future work will be on Axis2.
>
> How can I use Volatile2PC instead of Durable2PC with Kandula?
when you call enlistParticipant on a transaction object, pass 'false'
as the first argument.
TransactionImpl:
public void enlistParticipant(boolean durable,
AbstractParticipant participant) throws RemoteException
when a j2ee participant registers for a transaction, Durable2PC is always used.
there is no way to change this at present. if you could illaborate your
scenario I may be able to provide you with a fix.
thanks,
--dasarath
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org