Re: [sca-c-cpp] ISSUE 92: Multi-valued Property retrieval in C

[Bryan Aupperle <aupperle@us.ibm.com>]

A proposal based on last week's discussion

Highlights:
Each SCAProperty<T>() call has
an additional num_values in/out parameter indicating maximum allowable
values/configured values.
There is a new reason code indicating
more configured values need to be retrieved.
When retrieving multi-valued string,
character array or byte array property values, the size parameter is also
an array.



Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

From:	Bryan Aupperle/Raleigh/IBM@IBMUS
To:	sca-c-cpp@lists.oasis-open.org
Date:	08/11/2009 03:21 PM
Subject:	Re: [sca-c-cpp] ISSUE 92: Multi-valued Property retrieval in C

---

Here is a proposal based on the approach outlined below.  

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

From:	Bryan Aupperle/Raleigh/IBM@IBMUS
To:	sca-c-cpp@lists.oasis-open.org
Date:	07/31/2009 11:14 AM
Subject:	[sca-c-cpp] ISSUE 92: Multi-valued Property retrieval in C

---

As I was looking at this some more I had an inspiration.  Each of
the SCAProperty<T> functions has a value parameter that is a pointer
to the appropriate type.  Multi-valued properties are held in arrays
(we are not explicit about this yet, but the definition of @Property annotation
strongly suggest so).  The type of the property in the componentType
file would specify the maximum number of values for the property via a
maxOccurs facet.  So for a multi-valued property, the value parameter
would be the address of the array, and SCAProperty<T> would populate
the elements of the array with the configured values (the stride of the
array is based on <T> and the maxLength facet in the case of strings
or .size of struct resulting from the default mapping in the case of complexTypes
so the programmer needs to exercise care if type conversion during property
value retrieval).  This needs to be explained in section 2.3

The only interesting scenario that needs further API clarification is if
there are fewer configured values than there are array elements (the componetType
could prevent this by setting minOccurs = maxOccurs).  To handle this,
I propose that when SCAProperty<T> completes with a compCode of SCACC_OK
that the returned value of reason is the number of values set.

If this approach seems reasonable, I will prepare a full proposal for our
next call. 

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com 
[attachment "sca-ccni-1.1-spec-cd03-rev3+Issue92.doc" deleted
by Bryan Aupperle/Raleigh/IBM] ---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

sca-ccni-1.1-spec-cd03-rev3+ISSUE 92_2.doc