Lovely. If they have a support email address or something, you should definitely contact them. That soap message definitely does not match the schema/wsdl they are publishing. Thus, anything that actually validates the response should barf on it.

Feel free to have them contact me if they need more information or would like someone to help them test it with CXF or something.

Dan



On Jul 10, 2008, at 2:42 PM, Zemian Deng wrote:

Same result :(

On Thu, Jul 10, 2008 at 2:39 PM, Zemian Deng <[EMAIL PROTECTED]> wrote:
Hum... that service is a vendor supplied. The sad news is that I can
use SoapUI tool to get the response and see it clearly without
problem. The vendor claimed it works fine with Axis. I like Cxf and
want to give it best try before using other one.

I am going to try without -p now and let you guys know.
-Z

On Thu, Jul 10, 2008 at 2:32 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:


You can try, but if it still returns that same soap message, it's not going to work. That webservice is not valid. You would have to do some major
editing to the wsdl/schemas to get it to match that message.

Dan


On Jul 10, 2008, at 2:28 PM, Zemian Deng wrote:

Ahh.. that's good to konw.

So you think the solution is to regenerate the stub without -p option?
I am not sure what else to try to get that namespace matching.

-Z

On Thu, Jul 10, 2008 at 2:23 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:

On Jul 10, 2008, at 2:21 PM, Zemian Deng wrote:

By the way, I generated my client stub using this command:

$ wsdl2java -d target -p cnx.smartturn.ws.client
https://stdemo.smartturn.com/occam/services/OccamService?wsdl

Ick... the -p is also going to cause a problem. Definitely need to get:
https://issues.apache.org/jira/browse/CXF-1662
fixed.






Ofcourse I have to add the site's CA into my jdk's cacerts file
because it's from GoDaddyCA and not provided as default. After this, I
was able to run above command successfully.

So do you think I might have missed something with that step?

Thanks,
-Z

On Thu, Jul 10, 2008 at 2:09 PM, Zemian Deng <[EMAIL PROTECTED] >
wrote:

Sure Dan. Can you see this demo wsdl here:

https://stdemo.smartturn.com/occam/services/OccamService?wsdl

Thanks,
-Z

On Thu, Jul 10, 2008 at 1:42 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:

We'd need to see the wsdl and schema to see if that message really
matches
what the wsdl/xsd says it should look like.

Dan



On Jul 10, 2008, at 1:19 PM, Zemian Deng wrote:

Hello list,

I have generated client sources using wsdl2java for a WS, and I can send a request to service just fine. But when receiving a response from a proxy client service method (the return type is String), I always get null. I turned on the logging, and I can see a respond payload did return a string, but no from my service method returned.
Any reason for this?

Here is a sample of response received:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";



xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance"><soapenv:Body><authenticateResponse
xmlns="http://client.ws.smartturn.cnx/";><ns1:response



xmlns:ns1="http://www.smartturn.com/services/OccamService/authenticate ">authentication
-


success</ns1:response></authenticateResponse></ soapenv:Body></soapenv:Envelope>

I don't get "authentication - success", but a null instead. Can
someone help me?

Thanks,
--
Sweet - a Scala web framework:
http://code.google.com/p/sweetscala

---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog








--
Sweet - a Scala web framework:
http://code.google.com/p/sweetscala




--
Sweet - a Scala web framework:
http://code.google.com/p/sweetscala

---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog








--
Sweet - a Scala web framework:
http://code.google.com/p/sweetscala

---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog








--
Sweet - a Scala web framework:
http://code.google.com/p/sweetscala




--
Sweet - a Scala web framework:
http://code.google.com/p/sweetscala

---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog




Reply via email to