Objective-C SOAP Client --Request Problem?
I have generated code with WSDL2OBJC. I have big problem with request in my Objective C client:
CatalogoPortBinding *binding = [[CatalogoSvc CatalogoPortBinding] initWithAddress:@"http://localhost:8080/WSServer/Catalogo_V1"];
binding.logXMLInOut = YES; // to get logging to the console.
CatalogoSvc_hello *request = [[CatalogoSvc_hello alloc] init];
NSString *t = @"David";
request.name = t;
NSLog(@"request: %@",request.name);
CatalogoPortBindingResponse *response = [binding helloUsingParameters:request];
//NSLog(@"%@",resp.bodyParts);
for (id mine in response.bodyParts)
{
NSLog(@"name: %@",[mine return_]);
if ([mine isKindOfClass:[CatalogoSvc_helloResponse class]])
{
if (sec == YES) {
//NSLog(@"name: %@",[mine return_]);
NSString *texto = (NSString*)[mine return_];
[lab setText:(NSString*)texto];
}
}
}
my console show:
2011-08-31 12:29:05.086 Catalogo-V1[3596:207] request: David
2011-08-31 12:29:05.088 Catalogo-V1[3596:207] OutputHeaders:
{
"Content-Length" = 434;
"Content-Type" = "text/xml; charset=utf-8";
Host = localhost;
Soapaction = "";
"User-Agent" = wsdl2objc;
}
2011-08-31 12:29:05.088 Catalogo-V1[3596:207] OutputBody:
<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:CatalogoSvc="http://org/" xsl:version="1.0">
<soap:Body>
<CatalogoSvc:hello>
<CatalogoSvc:name>David</CatalogoSvc:name>
</CatalogoSvc:hello>
</soap:Body>
</soap:Envelope>
2011-08-31 12:29:05.093 Catalogo-V1[3596:207] ResponseStatus: 200
2011-08-开发者_运维知识库31 12:29:05.094 Catalogo-V1[3596:207] ResponseHeaders:
{
"Content-Type" = "text/xml;charset=utf-8";
Date = "Wed, 31 Aug 2011 10:29:05 GMT";
Server = "GlassFish Server Open Source Edition 3.1.1";
"Transfer-Encoding" = Identity;
"X-Powered-By" = "Servlet/3.0 JSP/2.2 (GlassFish Server Open Source Edition 3.1.1 Java/Apple Inc./1.6)";
}
2011-08-31 12:29:05.094 Catalogo-V1[3596:207] ResponseBody:
<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:helloResponse xmlns:ns2="http://org/"><return>Hello null !</return></ns2:helloResponse></S:Body></S:Envelope>
2011-08-31 12:29:05.095 Catalogo-V1[3596:207] name: Hello null !
I need to show this message: "Hello David !" and i receive: "Hello null!".
i had same problem until suggestion at below...
According to what you've shown from your console, the XML request you formulated is invalid. You have
<ns2:hello xmlns:ns2="http://org/" />
<name>david</name>
</ns2:hello>
But you should have (note the removal of the invalid XML tag termination):
<ns2:hello xmlns:ns2="http://org/>
<name>david</name>
</ns2:hello>
Also note that your working sample request includes a soap:Header element, and yours does not. That is unlikely to be the problem here though.
Based on comparing this request to what you have in your question posted about a manual solution, it looks like you've got namespace issues happening here. The SOAP request generated here applies the http://org/ namespace (via the identifier CatalogoSvc) to the "name" element:
<CatalogoSvc:hello>
<CatalogoSvc:name>David</CatalogoSvc:name>
</CatalogoSvc:hello>
In the manual scenario where you have gotten this to work, the http://org/ namespace is applied to the surrounding "hello" element but not the "name" element:
<ns2:hello xmlns:ns2="http://org/>
<name>david</name>
</ns2:hello>
Based on this observation, I would deduce that your service is not expecting a namespace to be applied to the name element, so it is not finding that parameter when it is sent with a namespace.
To fix this problem you will need to either:
- Figure out how to tell the SOAP client stub generation to NOT apply a namespace to your parameter, or
- Update your service to make it expect a namespaced "name" element.
Since the client side code is presumably generated from the service's WSDL, I suspect that the Objective-C code is doing it right and your service code has it wrong, but that's just a suspicion. Either way, you need to find a way to make client and server side "agree"
精彩评论