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]
