OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsrp] Spec / schema discrepancy


unfortunatly, right.

One could argue that the change would not affect producers, since if they
*did* always set the value, nothing changes for them.
For Consumers implementing publicNav params, this is the only way to reset
publicNav params on a pbia(), he() response, otherwise from the xsd point
of view the feature would not be usable.
Thus this would imply to me that
a) there is no consumer impl at this point is able to reset public params
b) consumers do the right thing already but do no xsd validation

As a result I would argue that we should be able to change that minor issue
without a new process step.

I've checked our impl and the latter is the case.
Our stack doesn't perform a schema validation and the generated JAX-RPC
model allows to set a null value to indicate a deletion.
Therefor the messages on the wire conform to the intended xsd ;-)

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept. 2289, WebSphere Portal Server Development 1
WSRP Team Lead
WSRP Architecture & Standardization
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888

IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294


|------------>
| From:      |
|------------>
  >------------------------------------------------------------------------------------------------------------------------------------------------|
  |Kevin Frender <kfrender@bea.com>                                                                                                                |
  >------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
  >------------------------------------------------------------------------------------------------------------------------------------------------|
  |wsrp@lists.oasis-open.org                                                                                                                       |
  >------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
  >------------------------------------------------------------------------------------------------------------------------------------------------|
  |12/05/2007 10:18 PM                                                                                                                             |
  >------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject:   |
|------------>
  >------------------------------------------------------------------------------------------------------------------------------------------------|
  |[wsrp] Spec / schema discrepancy                                                                                                                |
  >------------------------------------------------------------------------------------------------------------------------------------------------|





I think I have noticed a discrepancy between the
wsrp-2.0-types-pr-04.xsd and the wsrp-2.0-spec-pr-04 regarding the
publicValues in a NavigationalContext.
In the spec section 5.1.23, 5th bullet point it is stated that (within a
NavigationalContext) "The semantics of returning a publicValue item
without a value are to clear any stored value for that item."  In both
the spec and schema NavigationalContext's publicValues field is of type
NamedString; in the spec section 5.1.11 defining NamedString, the value
is marked as optional, which conforms to the statement from section
5.1.23.  However, the schema definition for NamedString is:

 <complexType name="NamedString">
   <sequence>
     <element name="value" type="xsd:string"/>
   </sequence>
   <attribute name="name" type="xsd:string" use="required"/>
 </complexType>

-- the value is not optional.  Therefore, it is not possible to return a
publicValue item without a value as stated in section 5.1.23.  Note that
the empty string value is not the same as the null value-- we must be
able to support empty string values distinct from null values.
NamedString is also used as the mimeAttributes type in an UploadContext,
and it is valid to have empty strings as a value for mime attributes.

As I see it, the schema needs to be changed to set minOccurs="0" on the
NamedString value element.

 Kevin

Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual or
entity named in this message. If you are not the intended recipient, and
have received this message in error, please immediately return this by
email and then delete it.

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]