You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Simon Fell <so...@zaks.demon.co.uk> on 2000/06/27 07:21:20 UTC
Bean Serializer Question
I'm working on the support for structs in 4S4C, and ideally, i'd like
it to inter-op with the bean serializer in apache-soap, here's the
relevant part of the return message for the GetAddress demo.
<ns1:getAddressFromNameResponse xmlns:ns1="urn:AddressFetcher"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<return xmlns:ns2="urn:ibm-soap-address-demo" xsi:type="ns2:address">
<phoneNumber xsi:type="ns2:phone">
...
I can see in the client code where is provides the mapping from
namespace URI's to Beans, is there any required format to the URI's,
i'm currently generating namespace URI's like
uuid:6B9EC0AC-C0C2-4FF9-894A-24CB77CDDAAD will this cause a problem ?
(other than headaches from staring at GUID's for too long !)
BTW, are there any views on the xsd & xsi namespace issues ? (the
URI's don't match the SOAP spec)
Thanks
Simon
Re: Bean Serializer Question
Posted by Simon Fell <so...@zaks.demon.co.uk>.
Hi,
i agree that it's COMish, however the URI is only used to map to a
bean at the client end, so in some respects as long as its consistent,
its meaningless. I think i'm going to go with GUID's but with the
option to override them with your own URI's.
Cheers
Simon
On Tue, 27 Jun 2000 00:23:37 -0600, in soap you wrote:
>Using a GUID seems too COMish. Can't you instead map a URI like
>"urn:ibm-soap-address-demo" to a GUID internally. For example, if a COM
>server could read a file like the DeploymentDescriptor.xml file that the
>Apache-SOAP server uses, then you could map the URI to a concrete COM object
>and a serializer/deserializer for that COM object.
>
>As far as I can tell about xsd and xsi, these are W3C specs, which SOAP
>builds on top of. Although I may be wrong as I'm new to SOAP.
>
>Blaine
>
>----- Original Message -----
>From: "Simon Fell" <so...@zaks.demon.co.uk>
>To: <so...@xml.apache.org>
>Sent: Monday, June 26, 2000 11:21 PM
>Subject: Bean Serializer Question
>
>
>I'm working on the support for structs in 4S4C, and ideally, i'd like
>it to inter-op with the bean serializer in apache-soap, here's the
>relevant part of the return message for the GetAddress demo.
>
><ns1:getAddressFromNameResponse xmlns:ns1="urn:AddressFetcher"
>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
><return xmlns:ns2="urn:ibm-soap-address-demo" xsi:type="ns2:address">
> <phoneNumber xsi:type="ns2:phone">
> ...
>
>I can see in the client code where is provides the mapping from
>namespace URI's to Beans, is there any required format to the URI's,
>i'm currently generating namespace URI's like
>uuid:6B9EC0AC-C0C2-4FF9-894A-24CB77CDDAAD will this cause a problem ?
>(other than headaches from staring at GUID's for too long !)
>
>
>BTW, are there any views on the xsd & xsi namespace issues ? (the
>URI's don't match the SOAP spec)
>
>
>Thanks
>Simon
Re: Bean Serializer Question
Posted by Simon Fell <so...@zaks.demon.co.uk>.
Hi,
i agree that it's COMish, however the URI is only used to map to a
bean at the client end, so in some respects as long as its consistent,
its meaningless. I think i'm going to go with GUID's but with the
option to override them with your own URI's.
Cheers
Simon
On Tue, 27 Jun 2000 00:23:37 -0600, in soap you wrote:
>Using a GUID seems too COMish. Can't you instead map a URI like
>"urn:ibm-soap-address-demo" to a GUID internally. For example, if a COM
>server could read a file like the DeploymentDescriptor.xml file that the
>Apache-SOAP server uses, then you could map the URI to a concrete COM object
>and a serializer/deserializer for that COM object.
>
>As far as I can tell about xsd and xsi, these are W3C specs, which SOAP
>builds on top of. Although I may be wrong as I'm new to SOAP.
>
>Blaine
>
>----- Original Message -----
>From: "Simon Fell" <so...@zaks.demon.co.uk>
>To: <so...@xml.apache.org>
>Sent: Monday, June 26, 2000 11:21 PM
>Subject: Bean Serializer Question
>
>
>I'm working on the support for structs in 4S4C, and ideally, i'd like
>it to inter-op with the bean serializer in apache-soap, here's the
>relevant part of the return message for the GetAddress demo.
>
><ns1:getAddressFromNameResponse xmlns:ns1="urn:AddressFetcher"
>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
><return xmlns:ns2="urn:ibm-soap-address-demo" xsi:type="ns2:address">
> <phoneNumber xsi:type="ns2:phone">
> ...
>
>I can see in the client code where is provides the mapping from
>namespace URI's to Beans, is there any required format to the URI's,
>i'm currently generating namespace URI's like
>uuid:6B9EC0AC-C0C2-4FF9-894A-24CB77CDDAAD will this cause a problem ?
>(other than headaches from staring at GUID's for too long !)
>
>
>BTW, are there any views on the xsd & xsi namespace issues ? (the
>URI's don't match the SOAP spec)
>
>
>Thanks
>Simon
Source Snapshot?
Posted by Troy Mac Neil <tm...@trakonic.com>.
Is there a source distribution of SOAP available for download? I have the
binary distribution and would like to start playing with the source,
hopefully without rsorting to a cvs install. I've looked around
xml.apache.org, but it wouldn't be the first time I missed something right
in front of me.
Thanks,
Troy
Source Snapshot?
Posted by Troy Mac Neil <tm...@trakonic.com>.
Is there a source distribution of SOAP available for download? I have the
binary distribution and would like to start playing with the source,
hopefully without rsorting to a cvs install. I've looked around
xml.apache.org, but it wouldn't be the first time I missed something right
in front of me.
Thanks,
Troy
Re: Bean Serializer Question
Posted by Blaine Brysh <bb...@v-wave.com>.
Using a GUID seems too COMish. Can't you instead map a URI like
"urn:ibm-soap-address-demo" to a GUID internally. For example, if a COM
server could read a file like the DeploymentDescriptor.xml file that the
Apache-SOAP server uses, then you could map the URI to a concrete COM object
and a serializer/deserializer for that COM object.
As far as I can tell about xsd and xsi, these are W3C specs, which SOAP
builds on top of. Although I may be wrong as I'm new to SOAP.
Blaine
----- Original Message -----
From: "Simon Fell" <so...@zaks.demon.co.uk>
To: <so...@xml.apache.org>
Sent: Monday, June 26, 2000 11:21 PM
Subject: Bean Serializer Question
I'm working on the support for structs in 4S4C, and ideally, i'd like
it to inter-op with the bean serializer in apache-soap, here's the
relevant part of the return message for the GetAddress demo.
<ns1:getAddressFromNameResponse xmlns:ns1="urn:AddressFetcher"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<return xmlns:ns2="urn:ibm-soap-address-demo" xsi:type="ns2:address">
<phoneNumber xsi:type="ns2:phone">
...
I can see in the client code where is provides the mapping from
namespace URI's to Beans, is there any required format to the URI's,
i'm currently generating namespace URI's like
uuid:6B9EC0AC-C0C2-4FF9-894A-24CB77CDDAAD will this cause a problem ?
(other than headaches from staring at GUID's for too long !)
BTW, are there any views on the xsd & xsi namespace issues ? (the
URI's don't match the SOAP spec)
Thanks
Simon
RE: Bean Serializer Question
Posted by Steven McDowall <sj...@aptest.com>.
LOL!
Are you a chartered accountant or something?? :-)
You are correct again.. Here is a diff that fixes both those issues:
Index: Constants.java
===================================================================
RCS file: /home/cvspublic/xml-soap/java/src/org/apache/soap/Constants.java,v
retrieving revision 1.3
diff -u -r1.3 Constants.java
--- Constants.java 2000/06/01 16:56:46 1.3
+++ Constants.java 2000/07/25 18:01:38
@@ -83,9 +83,9 @@
public static String NS_URI_SOAP_ENC =
"http://schemas.xmlsoap.org/soap/encoding/";
public static String NS_URI_SCHEMA_XSI =
- "http://www.w3.org/1999/XMLSchema/instance/";
+ "http://www.w3.org/1999/XMLSchema-instance";
public static String NS_URI_SCHEMA_XSD =
- "http://www.w3.org/1999/XMLSchema/";
+ "http://www.w3.org/1999/XMLSchema";
public static String NS_URI_IBM_SOAP =
"http://xml.apache.org/xml-soap";
public static String NS_URI_IBM_DEPLOYMENT =
-----Original Message-----
From: Simon Fell [mailto:simon@zaks.demon.co.uk]
Sent: Tuesday, July 25, 2000 12:19 PM
To: soap-dev@xml.apache.org
Subject: Re: Bean Serializer Question
also the XSD namespace shouldn't have a trailing /
Cheers
Simon
On Tue, 25 Jul 2000 11:59:08 -0500, in soap you wrote:
>
>Hmm..
>
>Considering that, from what I can tell, both the W3C Schema doc AND the
>Soap 1.1 doc both specify XMLSchema-instance, we probably should too.. :-)
>
>Here is the diff, which I believe is all we need, to Constants.java
>
>Index: Constants.java
>===================================================================
>RCS file:
/home/cvspublic/xml-soap/java/src/org/apache/soap/Constants.java,v
>retrieving revision 1.3
>diff -u -r1.3 Constants.java
>--- Constants.java 2000/06/01 16:56:46 1.3
>+++ Constants.java 2000/07/25 16:56:17
>@@ -83,7 +83,7 @@
> public static String NS_URI_SOAP_ENC =
> "http://schemas.xmlsoap.org/soap/encoding/";
> public static String NS_URI_SCHEMA_XSI =
>- "http://www.w3.org/1999/XMLSchema/instance/";
>+ "http://www.w3.org/1999/XMLSchema-instance";
> public static String NS_URI_SCHEMA_XSD =
> "http://www.w3.org/1999/XMLSchema/";
> public static String NS_URI_IBM_SOAP =
>
>
>
>
>-----Original Message-----
>From: Simon Fell [mailto:soap@zaks.demon.co.uk]
>Sent: Tuesday, July 25, 2000 12:14 AM
>To: soap-dev@xml.apache.org
>Subject: Re: Bean Serializer Question
>
>
>On Wed, 28 Jun 2000 01:29:41 -0400, in soap you wrote:
>
>>Simon Fell writes:
>>> section 1.2 says
>>> Throughout this document, the namespace prefix "xsi" is assumed to be
>>> associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
>>> which is defined in the XML Schemas specification [11]. Similarly, the
>>> namespace prefix "xsd" is assumed to be associated with the URI
>>> "http://www.w3.org/1999/XMLSchema" which is defined in [10].
>>>
>>> whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
>>> that i'm currently testing with, have these been changed ?)
>>
>>Nope.
>>
>>> xsd = http://www.w3.org/1999/XMLSchema/
>>> xsi = http://www.w3.org/1999/XMLSchema/instance/
>>>
>>> I've had a quick look at the schema specs, and the soap spec'd URI's
>>> do appear to be as per the schema specs.
>>
>>Ouch. If we screwed up we'll change it. I'm surprised James Snell's
>>interop testing didn't point this out .. James?
>>
>>Sanjiva.
>
>did we come to any conclusions here ?, i notice that the MS .net SOAP
>serializer uses
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/1999/XMLSchema"
>
>as per the SOAP 1.1 spec.
>
>Cheers
>Simon
RE: Bean Serializer Question
Posted by Steven McDowall <sj...@aptest.com>.
LOL!
Are you a chartered accountant or something?? :-)
You are correct again.. Here is a diff that fixes both those issues:
Index: Constants.java
===================================================================
RCS file: /home/cvspublic/xml-soap/java/src/org/apache/soap/Constants.java,v
retrieving revision 1.3
diff -u -r1.3 Constants.java
--- Constants.java 2000/06/01 16:56:46 1.3
+++ Constants.java 2000/07/25 18:01:38
@@ -83,9 +83,9 @@
public static String NS_URI_SOAP_ENC =
"http://schemas.xmlsoap.org/soap/encoding/";
public static String NS_URI_SCHEMA_XSI =
- "http://www.w3.org/1999/XMLSchema/instance/";
+ "http://www.w3.org/1999/XMLSchema-instance";
public static String NS_URI_SCHEMA_XSD =
- "http://www.w3.org/1999/XMLSchema/";
+ "http://www.w3.org/1999/XMLSchema";
public static String NS_URI_IBM_SOAP =
"http://xml.apache.org/xml-soap";
public static String NS_URI_IBM_DEPLOYMENT =
-----Original Message-----
From: Simon Fell [mailto:simon@zaks.demon.co.uk]
Sent: Tuesday, July 25, 2000 12:19 PM
To: soap-dev@xml.apache.org
Subject: Re: Bean Serializer Question
also the XSD namespace shouldn't have a trailing /
Cheers
Simon
On Tue, 25 Jul 2000 11:59:08 -0500, in soap you wrote:
>
>Hmm..
>
>Considering that, from what I can tell, both the W3C Schema doc AND the
>Soap 1.1 doc both specify XMLSchema-instance, we probably should too.. :-)
>
>Here is the diff, which I believe is all we need, to Constants.java
>
>Index: Constants.java
>===================================================================
>RCS file:
/home/cvspublic/xml-soap/java/src/org/apache/soap/Constants.java,v
>retrieving revision 1.3
>diff -u -r1.3 Constants.java
>--- Constants.java 2000/06/01 16:56:46 1.3
>+++ Constants.java 2000/07/25 16:56:17
>@@ -83,7 +83,7 @@
> public static String NS_URI_SOAP_ENC =
> "http://schemas.xmlsoap.org/soap/encoding/";
> public static String NS_URI_SCHEMA_XSI =
>- "http://www.w3.org/1999/XMLSchema/instance/";
>+ "http://www.w3.org/1999/XMLSchema-instance";
> public static String NS_URI_SCHEMA_XSD =
> "http://www.w3.org/1999/XMLSchema/";
> public static String NS_URI_IBM_SOAP =
>
>
>
>
>-----Original Message-----
>From: Simon Fell [mailto:soap@zaks.demon.co.uk]
>Sent: Tuesday, July 25, 2000 12:14 AM
>To: soap-dev@xml.apache.org
>Subject: Re: Bean Serializer Question
>
>
>On Wed, 28 Jun 2000 01:29:41 -0400, in soap you wrote:
>
>>Simon Fell writes:
>>> section 1.2 says
>>> Throughout this document, the namespace prefix "xsi" is assumed to be
>>> associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
>>> which is defined in the XML Schemas specification [11]. Similarly, the
>>> namespace prefix "xsd" is assumed to be associated with the URI
>>> "http://www.w3.org/1999/XMLSchema" which is defined in [10].
>>>
>>> whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
>>> that i'm currently testing with, have these been changed ?)
>>
>>Nope.
>>
>>> xsd = http://www.w3.org/1999/XMLSchema/
>>> xsi = http://www.w3.org/1999/XMLSchema/instance/
>>>
>>> I've had a quick look at the schema specs, and the soap spec'd URI's
>>> do appear to be as per the schema specs.
>>
>>Ouch. If we screwed up we'll change it. I'm surprised James Snell's
>>interop testing didn't point this out .. James?
>>
>>Sanjiva.
>
>did we come to any conclusions here ?, i notice that the MS .net SOAP
>serializer uses
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/1999/XMLSchema"
>
>as per the SOAP 1.1 spec.
>
>Cheers
>Simon
Re: Bean Serializer Question
Posted by Simon Fell <si...@zaks.demon.co.uk>.
also the XSD namespace shouldn't have a trailing /
Cheers
Simon
On Tue, 25 Jul 2000 11:59:08 -0500, in soap you wrote:
>
>Hmm..
>
>Considering that, from what I can tell, both the W3C Schema doc AND the
>Soap 1.1 doc both specify XMLSchema-instance, we probably should too.. :-)
>
>Here is the diff, which I believe is all we need, to Constants.java
>
>Index: Constants.java
>===================================================================
>RCS file: /home/cvspublic/xml-soap/java/src/org/apache/soap/Constants.java,v
>retrieving revision 1.3
>diff -u -r1.3 Constants.java
>--- Constants.java 2000/06/01 16:56:46 1.3
>+++ Constants.java 2000/07/25 16:56:17
>@@ -83,7 +83,7 @@
> public static String NS_URI_SOAP_ENC =
> "http://schemas.xmlsoap.org/soap/encoding/";
> public static String NS_URI_SCHEMA_XSI =
>- "http://www.w3.org/1999/XMLSchema/instance/";
>+ "http://www.w3.org/1999/XMLSchema-instance";
> public static String NS_URI_SCHEMA_XSD =
> "http://www.w3.org/1999/XMLSchema/";
> public static String NS_URI_IBM_SOAP =
>
>
>
>
>-----Original Message-----
>From: Simon Fell [mailto:soap@zaks.demon.co.uk]
>Sent: Tuesday, July 25, 2000 12:14 AM
>To: soap-dev@xml.apache.org
>Subject: Re: Bean Serializer Question
>
>
>On Wed, 28 Jun 2000 01:29:41 -0400, in soap you wrote:
>
>>Simon Fell writes:
>>> section 1.2 says
>>> Throughout this document, the namespace prefix "xsi" is assumed to be
>>> associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
>>> which is defined in the XML Schemas specification [11]. Similarly, the
>>> namespace prefix "xsd" is assumed to be associated with the URI
>>> "http://www.w3.org/1999/XMLSchema" which is defined in [10].
>>>
>>> whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
>>> that i'm currently testing with, have these been changed ?)
>>
>>Nope.
>>
>>> xsd = http://www.w3.org/1999/XMLSchema/
>>> xsi = http://www.w3.org/1999/XMLSchema/instance/
>>>
>>> I've had a quick look at the schema specs, and the soap spec'd URI's
>>> do appear to be as per the schema specs.
>>
>>Ouch. If we screwed up we'll change it. I'm surprised James Snell's
>>interop testing didn't point this out .. James?
>>
>>Sanjiva.
>
>did we come to any conclusions here ?, i notice that the MS .net SOAP
>serializer uses
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/1999/XMLSchema"
>
>as per the SOAP 1.1 spec.
>
>Cheers
>Simon
Re: Bean Serializer Question
Posted by Simon Fell <si...@zaks.demon.co.uk>.
also the XSD namespace shouldn't have a trailing /
Cheers
Simon
On Tue, 25 Jul 2000 11:59:08 -0500, in soap you wrote:
>
>Hmm..
>
>Considering that, from what I can tell, both the W3C Schema doc AND the
>Soap 1.1 doc both specify XMLSchema-instance, we probably should too.. :-)
>
>Here is the diff, which I believe is all we need, to Constants.java
>
>Index: Constants.java
>===================================================================
>RCS file: /home/cvspublic/xml-soap/java/src/org/apache/soap/Constants.java,v
>retrieving revision 1.3
>diff -u -r1.3 Constants.java
>--- Constants.java 2000/06/01 16:56:46 1.3
>+++ Constants.java 2000/07/25 16:56:17
>@@ -83,7 +83,7 @@
> public static String NS_URI_SOAP_ENC =
> "http://schemas.xmlsoap.org/soap/encoding/";
> public static String NS_URI_SCHEMA_XSI =
>- "http://www.w3.org/1999/XMLSchema/instance/";
>+ "http://www.w3.org/1999/XMLSchema-instance";
> public static String NS_URI_SCHEMA_XSD =
> "http://www.w3.org/1999/XMLSchema/";
> public static String NS_URI_IBM_SOAP =
>
>
>
>
>-----Original Message-----
>From: Simon Fell [mailto:soap@zaks.demon.co.uk]
>Sent: Tuesday, July 25, 2000 12:14 AM
>To: soap-dev@xml.apache.org
>Subject: Re: Bean Serializer Question
>
>
>On Wed, 28 Jun 2000 01:29:41 -0400, in soap you wrote:
>
>>Simon Fell writes:
>>> section 1.2 says
>>> Throughout this document, the namespace prefix "xsi" is assumed to be
>>> associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
>>> which is defined in the XML Schemas specification [11]. Similarly, the
>>> namespace prefix "xsd" is assumed to be associated with the URI
>>> "http://www.w3.org/1999/XMLSchema" which is defined in [10].
>>>
>>> whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
>>> that i'm currently testing with, have these been changed ?)
>>
>>Nope.
>>
>>> xsd = http://www.w3.org/1999/XMLSchema/
>>> xsi = http://www.w3.org/1999/XMLSchema/instance/
>>>
>>> I've had a quick look at the schema specs, and the soap spec'd URI's
>>> do appear to be as per the schema specs.
>>
>>Ouch. If we screwed up we'll change it. I'm surprised James Snell's
>>interop testing didn't point this out .. James?
>>
>>Sanjiva.
>
>did we come to any conclusions here ?, i notice that the MS .net SOAP
>serializer uses
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/1999/XMLSchema"
>
>as per the SOAP 1.1 spec.
>
>Cheers
>Simon
Re: Bean Serializer Question
Posted by Steven McDowall <sj...@aptest.com>.
Hmm..
Considering that, from what I can tell, both the W3C Schema doc AND the
Soap 1.1 doc both specify XMLSchema-instance, we probably should too.. :-)
Here is the diff, which I believe is all we need, to Constants.java
Index: Constants.java
===================================================================
RCS file: /home/cvspublic/xml-soap/java/src/org/apache/soap/Constants.java,v
retrieving revision 1.3
diff -u -r1.3 Constants.java
--- Constants.java 2000/06/01 16:56:46 1.3
+++ Constants.java 2000/07/25 16:56:17
@@ -83,7 +83,7 @@
public static String NS_URI_SOAP_ENC =
"http://schemas.xmlsoap.org/soap/encoding/";
public static String NS_URI_SCHEMA_XSI =
- "http://www.w3.org/1999/XMLSchema/instance/";
+ "http://www.w3.org/1999/XMLSchema-instance";
public static String NS_URI_SCHEMA_XSD =
"http://www.w3.org/1999/XMLSchema/";
public static String NS_URI_IBM_SOAP =
-----Original Message-----
From: Simon Fell [mailto:soap@zaks.demon.co.uk]
Sent: Tuesday, July 25, 2000 12:14 AM
To: soap-dev@xml.apache.org
Subject: Re: Bean Serializer Question
On Wed, 28 Jun 2000 01:29:41 -0400, in soap you wrote:
>Simon Fell writes:
>> section 1.2 says
>> Throughout this document, the namespace prefix "xsi" is assumed to be
>> associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
>> which is defined in the XML Schemas specification [11]. Similarly, the
>> namespace prefix "xsd" is assumed to be associated with the URI
>> "http://www.w3.org/1999/XMLSchema" which is defined in [10].
>>
>> whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
>> that i'm currently testing with, have these been changed ?)
>
>Nope.
>
>> xsd = http://www.w3.org/1999/XMLSchema/
>> xsi = http://www.w3.org/1999/XMLSchema/instance/
>>
>> I've had a quick look at the schema specs, and the soap spec'd URI's
>> do appear to be as per the schema specs.
>
>Ouch. If we screwed up we'll change it. I'm surprised James Snell's
>interop testing didn't point this out .. James?
>
>Sanjiva.
did we come to any conclusions here ?, i notice that the MS .net SOAP
serializer uses
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
as per the SOAP 1.1 spec.
Cheers
Simon
Re: Bean Serializer Question
Posted by Steven McDowall <sj...@aptest.com>.
Hmm..
Considering that, from what I can tell, both the W3C Schema doc AND the
Soap 1.1 doc both specify XMLSchema-instance, we probably should too.. :-)
Here is the diff, which I believe is all we need, to Constants.java
Index: Constants.java
===================================================================
RCS file: /home/cvspublic/xml-soap/java/src/org/apache/soap/Constants.java,v
retrieving revision 1.3
diff -u -r1.3 Constants.java
--- Constants.java 2000/06/01 16:56:46 1.3
+++ Constants.java 2000/07/25 16:56:17
@@ -83,7 +83,7 @@
public static String NS_URI_SOAP_ENC =
"http://schemas.xmlsoap.org/soap/encoding/";
public static String NS_URI_SCHEMA_XSI =
- "http://www.w3.org/1999/XMLSchema/instance/";
+ "http://www.w3.org/1999/XMLSchema-instance";
public static String NS_URI_SCHEMA_XSD =
"http://www.w3.org/1999/XMLSchema/";
public static String NS_URI_IBM_SOAP =
-----Original Message-----
From: Simon Fell [mailto:soap@zaks.demon.co.uk]
Sent: Tuesday, July 25, 2000 12:14 AM
To: soap-dev@xml.apache.org
Subject: Re: Bean Serializer Question
On Wed, 28 Jun 2000 01:29:41 -0400, in soap you wrote:
>Simon Fell writes:
>> section 1.2 says
>> Throughout this document, the namespace prefix "xsi" is assumed to be
>> associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
>> which is defined in the XML Schemas specification [11]. Similarly, the
>> namespace prefix "xsd" is assumed to be associated with the URI
>> "http://www.w3.org/1999/XMLSchema" which is defined in [10].
>>
>> whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
>> that i'm currently testing with, have these been changed ?)
>
>Nope.
>
>> xsd = http://www.w3.org/1999/XMLSchema/
>> xsi = http://www.w3.org/1999/XMLSchema/instance/
>>
>> I've had a quick look at the schema specs, and the soap spec'd URI's
>> do appear to be as per the schema specs.
>
>Ouch. If we screwed up we'll change it. I'm surprised James Snell's
>interop testing didn't point this out .. James?
>
>Sanjiva.
did we come to any conclusions here ?, i notice that the MS .net SOAP
serializer uses
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
as per the SOAP 1.1 spec.
Cheers
Simon
Re: Bean Serializer Question
Posted by Simon Fell <so...@zaks.demon.co.uk>.
On Wed, 28 Jun 2000 01:29:41 -0400, in soap you wrote:
>Simon Fell writes:
>> section 1.2 says
>> Throughout this document, the namespace prefix "xsi" is assumed to be
>> associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
>> which is defined in the XML Schemas specification [11]. Similarly, the
>> namespace prefix "xsd" is assumed to be associated with the URI
>> "http://www.w3.org/1999/XMLSchema" which is defined in [10].
>>
>> whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
>> that i'm currently testing with, have these been changed ?)
>
>Nope.
>
>> xsd = http://www.w3.org/1999/XMLSchema/
>> xsi = http://www.w3.org/1999/XMLSchema/instance/
>>
>> I've had a quick look at the schema specs, and the soap spec'd URI's
>> do appear to be as per the schema specs.
>
>Ouch. If we screwed up we'll change it. I'm surprised James Snell's
>interop testing didn't point this out .. James?
>
>Sanjiva.
did we come to any conclusions here ?, i notice that the MS .net SOAP
serializer uses
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
as per the SOAP 1.1 spec.
Cheers
Simon
Re: Bean Serializer Question
Posted by Simon Fell <so...@zaks.demon.co.uk>.
On Wed, 28 Jun 2000 01:29:41 -0400, in soap you wrote:
>Simon Fell writes:
>> section 1.2 says
>> Throughout this document, the namespace prefix "xsi" is assumed to be
>> associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
>> which is defined in the XML Schemas specification [11]. Similarly, the
>> namespace prefix "xsd" is assumed to be associated with the URI
>> "http://www.w3.org/1999/XMLSchema" which is defined in [10].
>>
>> whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
>> that i'm currently testing with, have these been changed ?)
>
>Nope.
>
>> xsd = http://www.w3.org/1999/XMLSchema/
>> xsi = http://www.w3.org/1999/XMLSchema/instance/
>>
>> I've had a quick look at the schema specs, and the soap spec'd URI's
>> do appear to be as per the schema specs.
>
>Ouch. If we screwed up we'll change it. I'm surprised James Snell's
>interop testing didn't point this out .. James?
>
>Sanjiva.
did we come to any conclusions here ?, i notice that the MS .net SOAP
serializer uses
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
as per the SOAP 1.1 spec.
Cheers
Simon
Re: Bean Serializer Question
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Simon Fell writes:
> section 1.2 says
> Throughout this document, the namespace prefix "xsi" is assumed to be
> associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
> which is defined in the XML Schemas specification [11]. Similarly, the
> namespace prefix "xsd" is assumed to be associated with the URI
> "http://www.w3.org/1999/XMLSchema" which is defined in [10].
>
> whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
> that i'm currently testing with, have these been changed ?)
Nope.
> xsd = http://www.w3.org/1999/XMLSchema/
> xsi = http://www.w3.org/1999/XMLSchema/instance/
>
> I've had a quick look at the schema specs, and the soap spec'd URI's
> do appear to be as per the schema specs.
Ouch. If we screwed up we'll change it. I'm surprised James Snell's
interop testing didn't point this out .. James?
Sanjiva.
Re: Bean Serializer Question
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Simon Fell writes:
> section 1.2 says
> Throughout this document, the namespace prefix "xsi" is assumed to be
> associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
> which is defined in the XML Schemas specification [11]. Similarly, the
> namespace prefix "xsd" is assumed to be associated with the URI
> "http://www.w3.org/1999/XMLSchema" which is defined in [10].
>
> whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
> that i'm currently testing with, have these been changed ?)
Nope.
> xsd = http://www.w3.org/1999/XMLSchema/
> xsi = http://www.w3.org/1999/XMLSchema/instance/
>
> I've had a quick look at the schema specs, and the soap spec'd URI's
> do appear to be as per the schema specs.
Ouch. If we screwed up we'll change it. I'm surprised James Snell's
interop testing didn't point this out .. James?
Sanjiva.
Re: Bean Serializer Question
Posted by Simon Fell <so...@zaks.demon.co.uk>.
On Wed, 28 Jun 2000 00:41:25 -0400, in soap you wrote:
[snip thoughts on beans & URI's]
>class should be used to map the schema type to and what code should
>be used to do it. Does this make sense? If not please ask again ..
makes sense to me, i have the basics of this working, i can take the
GetAddress demo from apache-soap and call it against my server and it
works fines, although my mappings are currently static per type. As i
don't currently have any config data at all, i need to think about how
provide a more flexible structure.
>> BTW, are there any views on the xsd & xsi namespace issues ? (the
>> URI's don't match the SOAP spec)
>
>Could you please explain what you mean? AFAIK we use exactly the URIs
>that are given in the SOAP spec and the Schema specs. I seem to recall
>that the soap spec was incorrect about one of the schema URIs and that
>we use the URI in the schema spec for that case. I forget the details
>now ..
>
>Sanjiva.
section 1.2 says
Throughout this document, the namespace prefix "xsi" is assumed to be
associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
which is defined in the XML Schemas specification [11]. Similarly, the
namespace prefix "xsd" is assumed to be associated with the URI
"http://www.w3.org/1999/XMLSchema" which is defined in [10].
whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
that i'm currently testing with, have these been changed ?)
xsd = http://www.w3.org/1999/XMLSchema/
xsi = http://www.w3.org/1999/XMLSchema/instance/
I've had a quick look at the schema specs, and the soap spec'd URI's
do appear to be as per the schema specs.
Cheers
Simon
Re: Bean Serializer Question
Posted by Simon Fell <so...@zaks.demon.co.uk>.
On Wed, 28 Jun 2000 00:41:25 -0400, in soap you wrote:
[snip thoughts on beans & URI's]
>class should be used to map the schema type to and what code should
>be used to do it. Does this make sense? If not please ask again ..
makes sense to me, i have the basics of this working, i can take the
GetAddress demo from apache-soap and call it against my server and it
works fines, although my mappings are currently static per type. As i
don't currently have any config data at all, i need to think about how
provide a more flexible structure.
>> BTW, are there any views on the xsd & xsi namespace issues ? (the
>> URI's don't match the SOAP spec)
>
>Could you please explain what you mean? AFAIK we use exactly the URIs
>that are given in the SOAP spec and the Schema specs. I seem to recall
>that the soap spec was incorrect about one of the schema URIs and that
>we use the URI in the schema spec for that case. I forget the details
>now ..
>
>Sanjiva.
section 1.2 says
Throughout this document, the namespace prefix "xsi" is assumed to be
associated with the URI "http://www.w3.org/1999/XMLSchema-instance"
which is defined in the XML Schemas specification [11]. Similarly, the
namespace prefix "xsd" is assumed to be associated with the URI
"http://www.w3.org/1999/XMLSchema" which is defined in [10].
whilst the apache soap URI's are (well to be precise, the IBM-SOAP 1.2
that i'm currently testing with, have these been changed ?)
xsd = http://www.w3.org/1999/XMLSchema/
xsi = http://www.w3.org/1999/XMLSchema/instance/
I've had a quick look at the schema specs, and the soap spec'd URI's
do appear to be as per the schema specs.
Cheers
Simon
Re: Bean Serializer Question
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Simon Fell writes:
> I'm working on the support for structs in 4S4C, and ideally, i'd like
> it to inter-op with the bean serializer in apache-soap, here's the
> relevant part of the return message for the GetAddress demo.
>
> <ns1:getAddressFromNameResponse xmlns:ns1="urn:AddressFetcher"
> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> <return xmlns:ns2="urn:ibm-soap-address-demo" xsi:type="ns2:address">
> <phoneNumber xsi:type="ns2:phone">
> ...
>
> I can see in the client code where is provides the mapping from
> namespace URI's to Beans, is there any required format to the URI's,
> i'm currently generating namespace URI's like
> uuid:6B9EC0AC-C0C2-4FF9-894A-24CB77CDDAAD will this cause a problem ?
> (other than headaches from staring at GUID's for too long !)
Nope, none at all from the code perspective.
The mapping from namespace URI to bean is actually a mapping from
the qualified name that's the element's schema type (ns2:address
in the above example) to a Java class. The Apache SOAP code uses a
registry which maintains these mappings, but it not fix a specific
binding to the schema type. That is, on one end I can bind the schema
type to a certain class and to a different class on the other side.
Similar, the other side could map it to a COM object and it wouldn't
matter one bit. All that matters is that the code be told which Java
class should be used to map the schema type to and what code should
be used to do it. Does this make sense? If not please ask again ..
> BTW, are there any views on the xsd & xsi namespace issues ? (the
> URI's don't match the SOAP spec)
Could you please explain what you mean? AFAIK we use exactly the URIs
that are given in the SOAP spec and the Schema specs. I seem to recall
that the soap spec was incorrect about one of the schema URIs and that
we use the URI in the schema spec for that case. I forget the details
now ..
Sanjiva.
Re: Bean Serializer Question
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Simon Fell writes:
> I'm working on the support for structs in 4S4C, and ideally, i'd like
> it to inter-op with the bean serializer in apache-soap, here's the
> relevant part of the return message for the GetAddress demo.
>
> <ns1:getAddressFromNameResponse xmlns:ns1="urn:AddressFetcher"
> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> <return xmlns:ns2="urn:ibm-soap-address-demo" xsi:type="ns2:address">
> <phoneNumber xsi:type="ns2:phone">
> ...
>
> I can see in the client code where is provides the mapping from
> namespace URI's to Beans, is there any required format to the URI's,
> i'm currently generating namespace URI's like
> uuid:6B9EC0AC-C0C2-4FF9-894A-24CB77CDDAAD will this cause a problem ?
> (other than headaches from staring at GUID's for too long !)
Nope, none at all from the code perspective.
The mapping from namespace URI to bean is actually a mapping from
the qualified name that's the element's schema type (ns2:address
in the above example) to a Java class. The Apache SOAP code uses a
registry which maintains these mappings, but it not fix a specific
binding to the schema type. That is, on one end I can bind the schema
type to a certain class and to a different class on the other side.
Similar, the other side could map it to a COM object and it wouldn't
matter one bit. All that matters is that the code be told which Java
class should be used to map the schema type to and what code should
be used to do it. Does this make sense? If not please ask again ..
> BTW, are there any views on the xsd & xsi namespace issues ? (the
> URI's don't match the SOAP spec)
Could you please explain what you mean? AFAIK we use exactly the URIs
that are given in the SOAP spec and the Schema specs. I seem to recall
that the soap spec was incorrect about one of the schema URIs and that
we use the URI in the schema spec for that case. I forget the details
now ..
Sanjiva.
Re: Bean Serializer Question
Posted by Blaine Brysh <bb...@v-wave.com>.
Using a GUID seems too COMish. Can't you instead map a URI like
"urn:ibm-soap-address-demo" to a GUID internally. For example, if a COM
server could read a file like the DeploymentDescriptor.xml file that the
Apache-SOAP server uses, then you could map the URI to a concrete COM object
and a serializer/deserializer for that COM object.
As far as I can tell about xsd and xsi, these are W3C specs, which SOAP
builds on top of. Although I may be wrong as I'm new to SOAP.
Blaine
----- Original Message -----
From: "Simon Fell" <so...@zaks.demon.co.uk>
To: <so...@xml.apache.org>
Sent: Monday, June 26, 2000 11:21 PM
Subject: Bean Serializer Question
I'm working on the support for structs in 4S4C, and ideally, i'd like
it to inter-op with the bean serializer in apache-soap, here's the
relevant part of the return message for the GetAddress demo.
<ns1:getAddressFromNameResponse xmlns:ns1="urn:AddressFetcher"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<return xmlns:ns2="urn:ibm-soap-address-demo" xsi:type="ns2:address">
<phoneNumber xsi:type="ns2:phone">
...
I can see in the client code where is provides the mapping from
namespace URI's to Beans, is there any required format to the URI's,
i'm currently generating namespace URI's like
uuid:6B9EC0AC-C0C2-4FF9-894A-24CB77CDDAAD will this cause a problem ?
(other than headaches from staring at GUID's for too long !)
BTW, are there any views on the xsd & xsi namespace issues ? (the
URI's don't match the SOAP spec)
Thanks
Simon