Hannes Erven schrieb:
Hi folks,
Dasarath Weeratunge wrote:
>
However, I do not
know whether ws-addressing implementation extracts reference
parameters in the
first place.
as far as I know WS-Addr extracts only those parameters whose QNames
have been configured in the server-config.wsdd file.
For example, for WS-BA support, we had to add the InitiatorRef element
to the enumeration for Kandula to see it:
client-config.wsdd, /deployment/globalConfiguration/requestFlow:
<handler
type="java:org.apache.axis.message.addressing.handler.AddressingHandler">
<parameter name="referencePropertyNames"
value="{http://ws.apache.org/kandula}CoordinatorRef,
{http://ws.apache.org/kandula}ParticipantRef,
{http://ws.apache.org/kandula}CallbackRef,
{http://ws.apache.org/kandula}InitiatorRef"/>
</handler>
Perhaps it works if you put JBoss' property names in there, but this
is kind of ugly. It would be better if Kandula always used the
properties and/or elements provided, regardless of this configuration.
I'm not sure how easy (or difficult) it would actually be to change
this, but I will also look at it.
In the mean time, best regards aus Wien and merry christmas,
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hey there,
well I am not sure if I got this right but so far I guess that
referenceParameters are extractet by ws addressing regarding to the
specifications of ws addressing. Anyways the more important question is
if Kandula is able to deal with them and if there is an easy way to
modify the context that will be send out to the registration coordinator
from JBoss so that there will be a communication.
I will try Hannes suggestion to modify the server-config on monday and
inform you guys about the result. I have another issue which I
encountered some time ago but unfortunately I am a little bit short on
time right now so that I can't take care about it. Some time ago I had
the problem with a scenario where a client was invoking two web services
A and B where A was preparing and B was aborting the coordinator send
rollback to A which it didn't understood and so A send back a prepared.
The coordinator and A were doing this so long that they were running
into a timeout. I have tried out the testSuite where there is the same
problem simulated and it worked well. Does someone has encountered
similar problems?
well so far I wish u a merry chistmas, best regards from Konstanz/Bodensee
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
