The prefix used shouldn't matter (whether wsk: or ws:), all that matters is that the namespace that it points to is correct (is it?)

Glen

On 05/20/2013 04:20 PM, Diego Cando wrote:
Hi Glenn, thanx 4 ur answer , I'm trying to publish a webservice that works
like this (sample of a client call)

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:wsk="http://www.randomweb.com/WStest/";>
             <soapenv:Header/>
             <soapenv:Body>
              <wsk:EntradaObtenerLogin>

I've done a regular WS with netbeans and glassfish and the only thing I'm
not able to set is that wsk thing, mine is published with ws instead.

Saludos cordiales/kind regards,
Diego Cando
JR Electric Supply / Consorcio MTE Latinus


-----Mensaje original-----
De: Glen Mazza [mailto:[email protected]]
Enviado el: lunes, 20 de mayo de 2013 15:08
Para: [email protected]
Asunto: Re: Question

I guess you're referring to this:
http://www.lexisnexis.com/webserviceskit/ ?  And when you say "get" you mean
make a SOAP client to be able to retrieve data from that web service?  I
can't see the WSDL without a developer ID but the web site says its WSDL is
Axis 1.x compliant which probably means it's the older RPC/encoded type
WSDL, not well supported by modern JAX-WS implementations.  You may need to
drag out the Axis 1.x (not Axis2) to get it working or use cumbersome JAX-WS
hacks if you want to stay with
CXF: http://www.jroller.com/gmazza/entry/calling_rpc_encoded_web_services.

*Sometimes*, if you remove the 'encoded' attributes from the WSDL, if no
encoding is actually occurring, you may be able to create a web service as
normal with CXF:
http://www.jroller.com/gmazza/entry/soap_client_tutorial.  YMMV though, and
I'm not sure how reliable/safe that would be.

Glen

On 05/20/2013 03:47 PM, Diego Cando wrote:
Hi, I wonder if you can help me, I'm trying to get a wsk type web
service with cxf, do you know how can I do that?

Saludos cordiales/kind regards,

Diego Cando

JR Electric Supply / Consorcio MTE Latinus



Reply via email to