Hi Andrew, JAX-RPC does not matter. What does matter is the version of the WS-Addressing spec that is supported. Axis2 supports both [1] and [2].
[1] http://www.w3.org/2002/ws/addr/ [2] http://www.w3.org/Submission/ws-addressing/ Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? "Whelan, Andy" <[email protected]> wrote on 30/11/2009 17:47:05: > [image removed] > > RE: Message Addressing Property error > > Whelan, Andy > > to: > > [email protected] > > 30/11/2009 17:47 > > Please respond to axis-user > > Brian > Does WS-Addressing work if it is being sent to an older style JAX- > RPC service? > > From: Brian De Pradine [mailto:[email protected]] > Sent: Monday, November 30, 2009 12:43 PM > To: [email protected] > Cc: [email protected] > Subject: Re: Message Addressing Property error > > > Hello Andrew, > > The message indicates that one of the WS-Addressing related headers > being sent by your client is not valid, as far as Axis2 is > concerned. In order to work out which header you should try again to > get TCPMon working, or use the SOAP Monitor described here, [1] > > [1] http://ws.apache.org/axis2/1_5/soapmonitor-module.html > > Cheers > > Brian DePradine > Web Services Development > IBM Hursley > External +44 (0) 1962 816319 Internal 246319 > > If you can't find the time to do it right the first time, where will > you find the time to do it again? > > > "Whelan, Andy" <[email protected]> wrote on 30/11/2009 15:23:59: > > > [image removed] > > > > Message Addressing Property error > > > > Whelan, Andy > > > > to: > > > > [email protected] > > > > 30/11/2009 15:24 > > > > Please respond to axis-user > > > > Hello, > > > > I am using Apache Axis 2 version 2-1.5. > > > > I have an application that uses JAX-RPC and a document/literal style > > WSDL, with xmlbeans as the java to XML binding. It is running in a > > Tomcat 6.0.20 container. > > > > I am trying to call it from an Oracle SOA Suite configuration > > (remotely). When the SOA Suite goes to invoke an operation on my > > Axis2 application I get the following error: > > > > org.apache.axis2.AxisFault: A header representing a Message > > Addressing Property > > is not valid and the message cannot be processed > > > > I?ve tried using TCPMon , setting it up between the SOA Suite and > > the tomcat server to get a look at the SOAP being passed around. > > During the SOA Suite set up I can see the SOA Suite reading the WSDL > > and schemas but when the operation gets invoked, nothing shows up in > > TCPMon, yet somehow axis is still invoked. > > > > The same thing happens whether I have the TCPMon in between or not. > > Can anyone tell me what the AxisFault message might be an indicator of? > > > > org.apache.axis2.AxisFault: A header representing a Message > > Addressing Property > > is not valid and the message cannot be processed > > > > Thanks > > -Andrew > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with > number 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
