Can I see the <wsdl:message> corresponding to the getAccounts message? I'd like to see how arg1 is defined.
It LOOKS like XMLSpy is not doing something correctly: <arg1 xsi:type="xsd:string">Stringo</arg1> That element isn't namespace qualified. All "top level" elements should be namespace qualified. Dan On Sunday 28 December 2008 8:41:56 pm Sebastian Mauer wrote: > Hello there, > > I am currently trying to implement a SOAP based WebService with CFX 2.1.3. > I opted to use JAX-WS / +Annotations rather than using the > ServerFactoryBean to make sure the generated WSDL specifies my SoapHeaders > (btw is that possible with ServerFactoryBean too?) > > My Service Class Interface does define my getAccount method like this > > Konto[] getAccounts(String test, @WebParam(header=true)String auth); > > The resulting WSDL looks also fine: > > <wsdl:operation name="getAccounts"> > <soap:operation soapAction="" style="document"></soap:operation> > <wsdl:input name="getAccounts"> > <soap:header message="tns:getAccounts" part="arg1" use="literal"> > </soap:header> > <soap:body parts="parameters" use="literal"></soap:body> > </wsdl:input> > <wsdl:output name="getAccountsResponse"> > <soap:body use="literal"></soap:body> > > </wsdl:output> > </wsdl:operation> > > My XMLSpy does generate the request as follows: > > <SOAP-ENV:Envelope > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > <SOAP-ENV:Header> > <arg1 xsi:type="xsd:string">Stringo</arg1> > </SOAP-ENV:Header> > <SOAP-ENV:Body> > <m:getAccounts xmlns:m="http://cli/";> > <arg0>String</arg0> > </m:getAccounts> > </SOAP-ENV:Body> > </SOAP-ENV:Envelope> > > This also looks fine to me, but in the end there is never passed anything > to method parameter auth (the SoapHeader) and it will be always null. Am I > missing something, shouldn't CXF pass that trough, too? > > Greetings, > > Sebastian Mauer -- Daniel Kulp [email protected] http://dankulp.com/blog
