Does the axis2.xml you are specifying engage the addressing module.
If it's not engaged then no validation of the WS-Addressing headers
occurs so the mission wsa:Action will be ignored.
David

On 08/11/06, Chris Iken <[EMAIL PROTECTED]> wrote:
Hi David,

Thanks for your response.

The Axis2 TCP transport puts no wsa:Action element into the message, but it
works (see below). So I think my implementation misses something.

I recently found out that the TCP transport doesn't work when I add
explicitly an axis2.xml (even with the axis2.xml from
axis2-kernel-1.1-RC2.jar:

System.setProperty(org.apache.axis2.Constants.AXIS2_CONF,
"G:\\2006\\axis2\\axis2.xml");

When adding an axis2.xml I also receive the same exception: "A required
header representing a Message Addressing Property is not present".

With the standard configuration it's working very well:
ConfigurationContextFactory

.createConfigurationContextFromFileSystem(dir, null)


Thanks for any help,
Chris


<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing";
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
<soapenv:Header>
<wsa:To>tcp://localhost:6060/axis2/services/MyService</wsa:To>
<wsa:ReplyTo>
<wsa:Address>http://www.w3.org/2005/08/addressing/anonymous
/wsa:Address>
</wsa:ReplyTo>
<wsa:MessageID>urn:uuid:7736F16A48C252BD5F11629790178581</wsa:MessageID>
</soapenv:Header>
<soapenv:Body>
<example1:echo
xmlns:example1="tcp://localhost:6060/axis2/services/MyService">
<example1:Text>Axis2 Echo String </example1:Text>
</example1:echo>
</soapenv:Body>
</soapenv:Envelope>


-----Ursprüngliche Nachricht-----
Von: David Illsley [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 8. November 2006 09:49
An: axis-user@ws.apache.org
Betreff: Re: [Axis2] Message Addressing Property is not present

It's not valid to use some WS-Addressing headers but leave out wsa:Action.
You should either generate the correct action or turn off WS-Addressing.
David

On 07/11/06, Chris Iken <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I try to start my custom transport on axis2 (1.1 RC2, Win XP) with the
> MyService example.
> On the receiver side I get the following exception:
>
> "A required header representing a Message Addressing Property is not
> present".
>
> In detail:
> <wsa:FaultDetail>
> <wsa:ProblemHeaderQName>wsa:Action</wsa:ProblemHeaderQName>
> </wsa:FaultDetail></soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <faultcode>wsa:MessageAddressingHeaderRequired</faultcode>
> <faultstring>A required header representing a Message Addressing Property
is
> not present</faultstring>
> <detail/>
>
> Obviously, the attribute wsa:Action can't be automatically computed. I
take
> the TCP example as template. Why it works there?
>
>
> Thanks for any hints,
> Chris
>
>
>
> Received SOAP on receiver side:
>
> <?xml version='1.0' encoding='utf-8'?>
> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing";
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <soapenv:Header>
> <wsa:To>pure://localhost:5000/axis2/services/MyService</wsa:To>
> <wsa:ReplyTo>
> <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
> </wsa:ReplyTo>
> <wsa:MessageID>urn:uuid:5FC41846E89DADC73D11629095719191</wsa:MessageID>
> </soapenv:Header>
> <soapenv:Body><example1:echo
> xmlns:example1="pure://localhost:5000/axis2/services/MyService">
> <example1:Text>Axis2 Echo String </example1:Text>
> </example1:echo>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> Axis2 Fault SOAP:
>
> <?xml version='1.0' encoding='utf-8'?>
> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing";
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <soapenv:Header>
> <wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To>
> <wsa:ReplyTo>
> <wsa:Address>http://www.w3.org/2005/08/addressing/none</wsa:Address>
> </wsa:ReplyTo>
> <wsa:MessageID>urn:uuid:B7A6B83EC42774F1F311629117150911</wsa:MessageID>
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> <wsa:RelatesTo
>
wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply";>urn:uuid:D
> 1FC51978E28C164D011629116118831
> </wsa:RelatesTo>
> <wsa:FaultDetail>
> <wsa:ProblemHeaderQName>wsa:Action</wsa:ProblemHeaderQName>
> </wsa:FaultDetail></soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <faultcode>wsa:MessageAddressingHeaderRequired</faultcode>
> <faultstring>A required header representing a Message Addressing Property
is
> not present</faultstring>
> <detail/>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
David Illsley - IBM Web Services Development

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
David Illsley - IBM Web Services Development

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to