One error in the schema definition:

You must import the "urn:BoldTBSearch/ns3.xsd" namespace into the
"urn:BoldTBSearch" namespace in order to reference the "ns3:docTypes",
"ns3:searchResults", and "ns3:docHits" types.

Also, I'm assuming you're using Axis 1.x. (Axis2 does not support SOAP
Encoding.)

It would help if you could supply a trace of the gSOAP message and the
Axis message. Per the rules defined by the WS-I Basic Profile, the
accessor elements that represent the parameters must be unqualified.
If gSOAP is expecting the supplierName element to be qualified, that's
a bug in gSOAP.

Anne

On 2/4/07, Vogel, Charles H <[EMAIL PROTECTED]> wrote:
Hi, I have developed a soap service using Gsoap that works fine when I
call te service from the gsoap client. I then used the Axis WSDL2Java
program to generate Java stubs from the WSDL generated by Gsoap. I have
the Java client running but when it calls the Gsoap method I see in the
Gsoap log file called TEST.log a bunch of messages saying:

Tags 'supplierName' and 'ns1:supplierName' match but namespaces differ
Unknown element 'supplierName' (level=3, 1)
IGNORING element 'supplierName'

Here supplierName is an xsd__string which is a typedef tochar*. But it
does not seem to matter what the type is. The namespaces differ and so
the element is ignored and comes through to the make empty/null even
though I know the Java client is setting it.

Here's the two WSDL's , one on the Gsoap side and the other that I
generated by using Java2WSDL by pointing Java2WSDL at the Java code I
generated by running WSDL2Java against the Gsoap WSDL.

 <<GSOAP_WSDL.txt>>  <<AXIS_WSDL.txt>>


Charlie Vogel
Bold Web Development
Work (206) 766-3856 Cell (206) 679-2699 M/S 2J-53
Email <mailto:[EMAIL PROTECTED]>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to