[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp] TC Call Feb 25 2010
I don’t have an issue to an array of properties (event
with the same name) but an issue with the value of a property being an array of
arbitrary values rather than a single value as with events.
It’s a bit weird to have a property value that should only be a single
“int” and have to treat it as an array of int. How do you
provide a schema that it should only be a single value when WSRP schema says
you can have an array of values? For events on other hand, if I have an
array, I have to explicitly provide an array schema type that results in a root
element that encloses the array items. The other point had to do with convenience default payload and
property values - “namedStringArray” and “stringValue”.
Once you’ve coded to <any>, these conveniences just get in the way.
And here’s another point: having specifically named elements
within EventPayload and Property made some sense when the <any> had to be
from “##other” namespace. However, if we move towards making
<any> being in the “##any” namespace, these specifically
named elements are definitely not so relevant. Neither of these issues cannot be worked around and yes it could
be considered cleanup. For me though, property value above seems more wrong. Nader From: Nathan Lipke
[mailto:nathan.lipke@oracle.com] Attendance:
Agenda:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]