Arthur,
I'd like to confirm my understanding based on the Spec and the previous
discussion in this thread. Please comment on any errors:
1. As per Part 1 Section 3.1, the Description component's {type
definitions} property should contain the datatypes defined by the schema
for XML Schema along with the types defined in any user-defined schemas.
The schema for XML Schema has 90 type definitions, but as per Part 1 Table
2-1 the minimum requirement is for the 19 primitive datatypes and 25
derived datatypes to be included in {type definitions}.
2. The 41 element declarations in the schema for XML Schema are not
required in the WSDL 2.0 component model so they should not appear in the
{element declarations} property of the Description component. Only
user-defined element declarations will appear in {element declarations}.
3. The Interchange Format Tests cater for XML Schema datatypes when
checking for expected TypeDefinitions (currently, the 'expected' types do
not include these XML Schema data types so I assume the Tests just ignore
any TypeDefinitions with the XML Schema namespace when counting the
'actual' number).
thanks,
John Kaputin
Arthur Ryman
<[EMAIL PROTECTED]
> To
[email protected]
02/11/2006 15:43 cc
[email protected]
Subject
Please respond to Re: Does Woden still need to import
[EMAIL PROTECTED] XML Schema schema?
he.org
John,
We don't need to import it but we do need to add the built-it types to the
component model. This is a fixed list which can be hard-coded in Woden.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
John Kaputin
<[EMAIL PROTECTED]>
To
[email protected]
11/01/2006 11:00 PM cc
Subject
Please respond to Does Woden still need to import
[email protected] XML Schema schema?
Lawrence or Arthur,
Do we still need to import the schema for XML Schema into Woden to get the
basic schema types into the model?
I think this was done to satisfy the Part 1 spec Section 3.1 at [1] which
says:
"The built-in XML Schema datatypes are built-in to the WSDL 2.0 component
model and are contained in the {type definitions} property of the
Description component. "
The other related history I can find is JIRA WODEN-1 and a mailing list
thread at [2].
Although the XML Schema schema is imported by Woden, its schema components
don't appear to be used anywhere and they are not expected by the component
interchange format when it checks for {element declarations} and {type
definitions} in the Description component. Until now they have not appeared
in the component model anyway due to a bug in the equals(Object) method of
XmlSchema which is used indirectly by Woden's ComponentModelBuilder when it
populates the {element declarations} and {type definitions} properties. I
have a possible fix for XmlSchema (to fix Chameleon-4G for WODEN-13) but
this means that all schema components inlined or imported within types
element will now appear in {element declarations} and {type definitions},
including those for the XML Schema schema.
I can work around this in ComponentModelBuilder to exclude the XML Schema
schema components from {element declarations} and {type definitions} so as
not to break the component interchange tests, but in that case maybe I
should just remove the Woden code that imports the XML Schema schema
instead?
I have run AllWodenTests with this code commented out and it does not break
anything (except for some resolver tests whose asserts assume that XML
Schema schema is present - easily changed).
[1]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-type=text/html;%20charset=utf-8#xsd-types
[2] http://lists.w3.org/Archives/Public/www-ws-desc/2006Jan/0038.html
John Kaputin
---------------------------------------------------------------------
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]
