Soumen,
I am glad you feel the same way. Only at the moment I have a challange. I am trying to modify the two sources of soap the way that all will also work without the namespacing.
The sources i try to modify are:
- QName.java
- Deserialize.java
If I have the wrong ones, or if someone have a better idea, please let me know. I just can't ask the originator client to add a patch or something else, because all other servers are unfortunately NT servers with MS Soap.
It all works if they include the 'xmlns' in the requester tag, but thay can't with all the other servers.
I hope that there is someone else who had the same problem and found a solution.
Thanks in advance.
Henk.
Soumen Sarkar <[EMAIL PROTECTED]>
11/08/2001 11:26 AM PST
Please respond to soap-dev
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
bcc:
Subject: RE: XML namespacing
I followed this message exchange and similar in past.
They all refer to interoperability problem. Could
SOAP experts clarify the following:
1. Without seamless interoperability, how web service
community may prosper. Hand plumbing (e.g take out
namespace from SOAP request) is not good for web
service prosperity. SOAP spec is permissible of
many forms of encoding (all SOAP spec compliant).
There has to be some encoding negotiation (like OSI
presentation layer) which if successful, would
gurantee seamless interoperability (from that point).
What is being done in this respect, from a specification
perspective?
Please note that this kind of problems are not there
in CORBA/IIOP. The spec is rock solid. At least client
side portability is pretty much taken for granted.
2. I have evaluated some application servers regarding their
web service support. In many cases I had problems with
namespace issues. Sometimes it looks very trivial like
this particular thread (all parameters are there in the
message but namespace issues are blocking interop). I
think namespace issue is seperate from soap encoding
issues. Should there be negotioations on namespaces as well?
Overall, from interoperability standpoint, my feeling is that
SOAP is pretty immature from a specification perspective. This
will hinder industry wide adoptability. I welcome clarifications
on this point.
Thanks,
Soumen Sarkar.
-----Original Message-----
From: Henk Schipper [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 08, 2001 5:26 AM
To: [EMAIL PROTECTED]
Subject: RE: XML namespacing
2.0 they say. I only saw the client they are running to get requests. And
this request is shown at the bottom at this mail.
I one way I have to get rid of the 'xmlns' in the 'my_request' tag.
How would I do that.
The only thing I read is that from the apache site, its a bug in the ms soap
toolkit. On the other hand it is the most normal case within microsoft.
Please HELP. I also read a lot of interoperabillity tests, but this specific
thing is not clear enough anymore for me.
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV :Body>
<my_request xmlns="get.details">
<field1>010100970</field1>
</my_request>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks in advance.
Henk.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 08 November, 2001 2:16 PM
To: [EMAIL PROTECTED]
Subject: Re: XML namespacing
Henk,
After looking harder at requests coming from a Java client vs MS
client I see they do not include a namespace...and your deployment
descriptor is counting on a namespace....What version of the MS toolkit are
your clients using?
//java client
<SOAP-ENV:Envelope xmlns:SOAP-ENV
="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi
="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd
="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:GetItemMaster xmlns:ns1
="urn:http://localhost:80/mesapi/MESGetData.xml" SOAP-ENV:encodingStyle
="http://schemas.xmlsoap.org/soap/encoding/">
<sXML xsi:type="xsd:string"><![CDATA
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
///And here is the request coming from a MS SOAP client
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP:Body>
<GetItemMaster>
<sXML><![CDATA
</SOAP:Body>
</SOAP:Envelope>
Both are hitting a MS SOAP server...asp listener etc...
Henk.Schipper@softw
are684.com To: [EMAIL PROTECTED]
cc: (bcc: Doug
Swanson/US-Corporate/3M/US)
11/08/2001 02:49 AM Subject: XML namespacing
Please respond to
soap-dev
(See attached file: att1.htm)
