Sorry - I should have made that clearer - if the status is "Active" and
not "Tentative Resolve" or "Resolved", then the "Resolution" is just something
proposed by the issuer, or maybe by somebody else.
-----Original Message-----
From: Andre Kramer
[mailto:]
Sent: Wed, December 18, 2002
11:43
To: 'Gil Tayar';
Subject: RE: [wsrp-wsia] [I#202] The
field schema in Modeldescription has no WSDL encoding
The
"Resolution:"s in my new issues, of course, should all be a "Proposal:"
for discussion.
regards,
Andre
-----Original Message-----
From: Gil Tayar
[mailto:]
Sent: 18 December 2002
09:05
To:
Subject:
[wsrp-wsia] [I#202] The field schema in Modeldescription has no WSDL
encoding
Issue: 202
Status: Active
Topic:
interface
Class: Minor_Technical
Raised by: Andre Kramer
Title: The
field schema in Modeldescription has no WSDL encoding
Date Added:
18-Dec-2002
Document Section:
v0.85/7.1.9
Description:
The Schema type in ModelDescrition has no
good representation in WSDL and no value as an ANY.
Resolution:
"Use a
url to point to a schemafilename.xsd file containing a XML schema
document.
<attribute name=""shemaURL"" type=""xsd:string""
use=""required""/> [In practice, can't use schemaLocation and anyURL is
broken in JAXRPC.] The JSR168 should then publish a schema at a well known
URL for any
extensions it requires, above string arrays and named strings
(string name value pair collections) and stringValue properties, including
container elements in <extensions/> (that are a JSR168 type and point
at the JSR168 xsd using the schemaURL attribute) for the string types in the
WSRP wsdl, so that they can be carried in WSRP Extensions elements in a more
well-typed manner."
