Hi Daniel...
Thanks very much...
I trust the WSDL is specified correctly. It defines both: 1.2, 1.1
namespaces.
(see snippet below
xmlns:soap
xmlns:soap12)
The CXF wsdl2java utility generates stubs to support both these spec.
versions I believe.
The WSDL I generated my code from begins like this:
<?xml version="1.0" encoding="utf-8" ?>
<wsdl:definitions
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/";
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
xmlns:tns="http://www.vendorcare.com/";
xmlns:s="http://www.w3.org/2001/XMLSchema";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
targetNamespace="http://www.vendorcare.com/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
Once I generated my code - I don't use the WSDL again (at runtime).
I'm assuming that Mule/CXF-EndPoint figures everything out by leveraging the
auto-generated classes to
produce SOAP that conforms to the WSDL I supplied when doing the one time
wsdl2java compilation.
I've only ever had to change endpoint-urls at runtime; if namespaces change
- I usually regenerate...
Please see the attached image...
Any thoughts would be greatly appreciated.
Thanks
Frank
On Fri, Oct 29, 2010 at 3:39 PM, Daniel Kulp <[email protected]> wrote:
>
> CXF is sending a SOAP 1.1 envelope, but it looks like you are expecting a
> 1.2
> envelope. Does the WSDL properly say it's supposed to be 1.2 and are you
> using the WSDL at runtime?
>
> Dan
>
>
> On Friday 29 October 2010 1:28:51 pm Frank Misa wrote:
> > Hi CXF Users, Developers....
> >
> > I'm using CXFv2.2.2 - "wsdl first scenario" - in Mule3.0 by configuring a
> > CXF endpoint and using CXF wsdl2java utility to generate
> stubs/skeletons...
> > NOTE: The web service that CXF will be sending a message to is Axis1.2.1
> > based.
> >
> > CXF seems to be returning the desired SOAP response - but the namespaces
> > are off ?
> >
> > https://issues.apache.org/jira/browse/CXF-1993
> >
> > Question1: Is SoapOutInterceptor the only way I can force my CXF to use a
> > certain namespace on soap:envelope ?
> > I can't find any decent examples of doing this. Can
> > someone please forward a link/example.
> > Where do I register my "SoapOutInterceptor" - any usage
> > documentation out there.
> >
> > Question2: Are there other better, declarative ways of configuring this
> > information ?
> > Seems like a common scenario to me.
> >
> > It's confusing how some configuration is done using annotations on
> > generated clases...
> > While "interceptors" need to be registered to control other parts of the
> > CXF messaging...
> >
> > THIS IS WHAT I WANT:
> >
> > <soap:Envelope xmlns:soap="*http://www.w3.org/2003/05/soap-envelope*";
> >
> > xmlns:vendor="http://www.vendorcare.com/";>
> >
> > <soap:Header/>
> >
> > <soap:Body>
> >
> > < vendor:MessageBrokerv2Response>
> >
> > < vendor:MessageBrokerv2Result>MESSAGE_CONTENT</
> > vendor:MessageBrokerv2Result>
> >
> > </ vendor:MessageBrokerv2Response>
> >
> > </soap:Body>
> >
> > </soap:Envelope>
> >
> >
> > THIS IS WHAT CXF/MULE IS PRODUCING
> >
> > <soap:Envelope xmlns:soap="*http://schemas.xmlsoap.org/soap/envelope/*";>
> >
> > <soap:Body>
> >
> > < vendor:MessageBrokerv2Response xmlns="
> > http://www.vendorcare.com/ <http://www.omnicare.com/>">
> >
> > <
> > vendor:MessageBrokerv2Result>MESSAGE_CONTENT</
> > vendor:MessageBrokerv2Result>
> >
> > </ vendor:MessageBrokerv2Response>
> >
> > </soap:Body>
> >
> > </soap:Envelope>
> >
> >
> > Thanks
> > Frank
>
> --
> Daniel Kulp
> [email protected]
> http://dankulp.com/blog
>
--
________________________________________________
Frank Misa Was Here
\|||/
(o o)
----ooO-(_)-Ooo--------
Cell: (416) 721-3466 <[email protected]>
[email protected]
________________________________________________
