[Axis2] Best place to setWSAAction() for request messages?

[Chuck Williams <ch...@manawiz.com>]

Resending with proper [Axis2] labeling:

Hi All,

I want to use WS Addressing based dispatch for messages sent over the
tcp transport.  As best I can tell, the WSA Action attribute is never
set in the code path starting from the PortTypeStub generated for the
client.  The natural place to set this would seem to be in each client
operation method in the PortTypeStub, since this method knows the
operation to be invoked.  That would seem to be a fairly simple
extension to the code generator that should be there by default.

Does this seem right?  Is there a better place to do this?  The
documentation for the tcp transport specifically mentions WS Addressing
as a supported dispatch method, but I don't see any way for this to
work, at least not if using the generated PortTypeStub.  Is the
infrastructure already there in some mechanism I've missed?

Thanks for any info,

Chuck

Re: [Axis2] Best place to setWSAAction() for request messages?

[Ajith Ranabahu <aj...@gmail.com>]

Hi Chuck,
We are working on incorporating the WSA:Action into the stubs and just
as you anticipated  it will be inside each client operation. Why it's
being a little late is that the WSDL readers still don't understand
WSA parts and we've to fix the the WOM reader first.

On 2/7/06, Chuck Williams <ch...@manawiz.com> wrote:
> Resending with proper [Axis2] labeling:
>
> Hi All,
>
> I want to use WS Addressing based dispatch for messages sent over the
> tcp transport.  As best I can tell, the WSA Action attribute is never
> set in the code path starting from the PortTypeStub generated for the
> client.  The natural place to set this would seem to be in each client
> operation method in the PortTypeStub, since this method knows the
> operation to be invoked.  That would seem to be a fairly simple
> extension to the code generator that should be there by default.
>
> Does this seem right?  Is there a better place to do this?  The
> documentation for the tcp transport specifically mentions WS Addressing
> as a supported dispatch method, but I don't see any way for this to
> work, at least not if using the generated PortTypeStub.  Is the
> infrastructure already there in some mechanism I've missed?
>
> Thanks for any info,
>
> Chuck
>
>
>


--
Ajith Ranabahu