Hi Bryan,
I agree with the first point, but I think on the second, we
still need the <T> to override the type of the value. Eg,
dataObject.set(3); creates a property of type Int,
but
dataObject.set(String.class, 3); creates a
property of type String.
Ron
Von: Bryan Aupperle
[mailto:aupperle@us.ibm.com]
Gesendet: Montag, 27. September 2010 15:23
An: sdo@lists.oasis-open.org
Betreff: [sdo] NEW ISSUE: Problems with COR04010903
There
are some problems with COR04010903:
In the first
bullet mentions DataObject.set<T>() but not DataObject.set() and the
example on line 470 use DataObject.set().
In the first
bullet mentions Sequence.add<T>() which does not exist.
The second
bullet states the Type of the new property is based on T, which is not
sufficient (it does not cover DataObject.set() or Sequence.add()).
Proposal
Change the
first bullet to: The property name is the name passed to the
DataObject.set<T>(), DataObject.set() or Sequence.add() method.
Change the
second bullet to: The property type is derived from or the type of the value or
List of values being set or added.
Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of
Excellence Application Integration Architect
Research Triangle Park, NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com