axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Antonio (JIRA)" <>
Subject [jira] Commented: (AXIS2-2571) SOAPAction mismatch invoking service
Date Tue, 12 Jun 2007 10:38:25 GMT


Jose Antonio commented on AXIS2-2571:

I developed the service I was writing in Muse using plain Axis2 and it doesn't have that problem,
so I gess it's a Muse issue. As Muse is not using Axis2's WSA implementation, it may mess
the outgoing messages and it may enter a phase with null  soapaction and wsaaction so the
default is created. I don't know. Anyway, if you are still interested in the code, I can send

> SOAPAction mismatch invoking service
> ------------------------------------
>                 Key: AXIS2-2571
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Addressing
>         Environment: Ubuntu Linux 6.10, Sun JDK 1.4.2, Apache Tomcat 5.5.23
>            Reporter: Jose Antonio
>            Assignee: Brian DePradine
> I'm trying to invoke an Axis2 service inside a Muse service. To do
> this I'm using the Axis2 service stub I generated but when I send a
> message I get the following:
> POST /axis2/services/RegistrationService HTTP/1.1
> SOAPAction: ""
> User-Agent: Axis2
> Host:
> Transfer-Encoding: chunked
> Content-Type: text/xml; charset=UTF-8
> 545
> <?xml version='1.0' encoding='UTF-8'?>
>  <soapenv:Envelope xmlns:wsa=""
> xmlns:soapenv="">
>     <soapenv:Header>
>        <wsa:To>http://localhost:8081/axis2/services/RegistrationService</wsa:To>
>        <wsa:ReplyTo>
>           <wsa:Address></wsa:Address>
>        </wsa:ReplyTo>
>        <wsa:MessageID>urn:uuid:63015A36B234BC96B8117708283322511</wsa:MessageID>
>        <wsa:Action></wsa:Action>
>     </soapenv:Header>
> ........................
> As you can see, the SOAPAction and wsa Action elements are different
> and I don't know why. Using this same Stub in a local program I get
> the same text in both elements and the call succeed but using it in
> Muse gets this 'Response' part added.
> Is it a Muse or an Axis2 problem? Does Axis2 add a 'Response' element
> for every outgoing message in a service?

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