axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Resolved: (AXIS2C-1444) WS addressing enabled service returns just an acknowledgement and not the response
Date Thu, 04 Mar 2010 14:41:27 GMT


Samisa Abeysinghe resolved AXIS2C-1444.

    Resolution: Not A Problem

I have tested Axis2/C for WS-Addressing test suite at

If there are any problems, please point the case from this suite that fails, so that we can
fix it. 

AFAICT, your scenario should work, in sync with the test cases. So there has to be something
wrong with the setup, if you have it failing, as we pass all the test cases. 

> WS addressing enabled service returns just an acknowledgement and not the response
> ----------------------------------------------------------------------------------
>                 Key: AXIS2C-1444
>                 URL:
>             Project: Axis2-C
>          Issue Type: Task
>          Components: core/addressing
>    Affects Versions: 1.6.0
>         Environment: Unix
>            Reporter: Gautham Varada
>            Priority: Blocker
> Hello,
> I'm trying to implement a service that implements ws addressing in the axis2c framework.

> The service is mediated through a ESB flow(Message broker).
> I send a asynchronous soap request and I get an ack back from the http server but no
> There is not much information in the logs, the only information in log says
> "Starting addressing out handler Starting addressing in handler Starting addressing out
handler soap_builder.c(852) SOAP message does not have a SOAP envelope element "
> To enable ws addressing in axis 2c. I have made sure that the addressing module is enabled
in the axis2.xml and the services.xml has the wsmapping which matches the ws:action attribute
I send out.
> Am I missing anything? Do I neeed to add any additonal metadata in the WSDL to enable
ws addressing.
> Any help is much appreciated.
> It appears that this issue is common. I'm hoping there is a fix to this.
> Thanks
> GV

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message