[cddlm] proposed change to deploy API state info

[Stuart Schaefer]

Steve,

The stateInfo string comes from an early revision of the Component
Model.  The CM now uses WSDM.  You should follow the example in the CM
to reflect the use of WSDM.

Stuart

-----Original Message-----
From: Steve Loughran [mailto:steve_loughran at hpl.hp.com] 
Sent: Friday, May 13, 2005 1:32 PM
To: CDDLM
Subject: [cddlm] proposed change to deploy API state info

looking at the deployment API, it has three components: state enum, 
stateInfo (a string) and extended state

             <xsd:element name="state" type="cmp:lifecycleStateType"/>
             <xsd:element name="stateInfo" type="xsd:string"/>
             <xsd:element name="extendedState" 
type="cmp:unboundedXMLAnyNamespace"
               minOccurs="0"/>

We dont really need that stateInfo string do we? the cmp: state 
identifies every state; if you want to map that enum to a string in the 
language/locale of preference, you are free to do so. And the extended 
state can be anything you like.

I propose, therefore, dropping that element, leaving a sequence of

             <xsd:element name="state" type="cmp:lifecycleStateType"/>
             <xsd:element name="extendedState" 
type="cmp:unboundedXMLAnyNamespace"
               minOccurs="0"/>

Comments?