[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Fwd: [JIRA] Updated: (REGREPTC-111) UpdateObjectsRequest does nothave a mode like SubmitObjectrsRequest]
Dear colleagues, Please discuss this issue on this thread (rather than adding comments to JIRA). Thanks. Nikola please ping sometime so we can sync on spec work this week. Thanks. -- Regards, Farrukh Web: http://www.wellfleetsoftware.com
--- Begin Message ---
- From: WxForge JIRA <jirauser@mailhub.wx.ll.mit.edu>
- To: farrukh@wellfleetsoftware.com
- Date: Mon, 21 Sep 2009 17:14:51 -0400 (EDT)
[ http://wxforge.wx.ll.mit.edu:8080/jira/browse/REGREPTC-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farrukh Najmi updated REGREPTC-111: ----------------------------------- Summary: UpdateObjectsRequest does not have a mode like SubmitObjectrsRequest (was: UpdateObjectsRequest does not have a mode like SubmitObjectrsRequestProposed solution) Description: This means that there is no way to control versioning now that versioning is controlled in SubmitObjectsRequest via mode="CreateOrVersion" per resolution of: http://wxforge.wx.ll.mit.edu:8080/jira/browse/REGREPTC-97 Proposed solution: -Add global type <simpleType name="mode"> <restriction base="NCName"> <enumeration value="CreateOrReplace"/> <enumeration value="CreateOrVersion"/> <enumeration value="CreateOnly"/> </restriction> </simpleType> -Ref the global type in Submit/UpdateObjectsRequest <element name="SubmitObjectsRequest"> <annotation> <documentation xml:lang="en">This SubmitObjects protocol allows a client to submit RegistryObjects to the server. It also allows a client to completely replace existing RegistryObjects in the server.</documentation> </annotation> <complexType> <complexContent> <extension base="rs:RegistryRequestType"> <sequence> <element name="RegistryObjectList" type="rim:RegistryObjectListType" minOccurs="0" maxOccurs="1"/> <element name="ObjectRefList" type="rim:ObjectRefListType" minOccurs="0" maxOccurs="1" /> </sequence> <attribute name="mode" type="tns:mode" use="optional" default="CreateOrReplace"/> </extension> </complexContent> </complexType> </element> <element name="UpdateObjectsRequest"> <annotation> <documentation xml:lang="en">This UpdateObjectsRequest allows a client to updates elements and attributes within RegistryObjects already existing in the server.</documentation> </annotation> <complexType> <complexContent> <extension base="rs:RegistryRequestType"> <sequence> <!-- Query and ObjectRefList select objects to update --> <element name="Query" type="rim:QueryType" minOccurs="0" maxOccurs="1" /> <element name="ObjectRefList" type="rim:ObjectRefListType" minOccurs="0" maxOccurs="1" /> <!-- Specifies how to update selected objects --> <element name="UpdateAction" type="tns:UpdateActionType" minOccurs="1" maxOccurs="unbounded"/> </sequence> <attribute name="mode" type="tns:mode" use="optional" default="CreateOrReplace"/> </extension> </complexContent> </complexType> </element> Issue: There is a mode attribute in UpdateActionType. Is there too many mode attributes and is this confusing? was: This means that there is no way to control versioning now that versioning is controlled in SubmitObjectsRequest via mode="CreateOrVersion" per resolution of: http://wxforge.wx.ll.mit.edu:8080/jira/browse/REGREPTC-97 > UpdateObjectsRequest does not have a mode like SubmitObjectrsRequest > -------------------------------------------------------------------- > > Key: REGREPTC-111 > URL: http://wxforge.wx.ll.mit.edu:8080/jira/browse/REGREPTC-111 > Project: ebXML RegRep TC > Issue Type: Improvement > Reporter: Farrukh Najmi > Assignee: Farrukh Najmi > > This means that there is no way to control versioning now that versioning is controlled in SubmitObjectsRequest via mode="CreateOrVersion" per resolution of: > http://wxforge.wx.ll.mit.edu:8080/jira/browse/REGREPTC-97 > Proposed solution: > -Add global type > <simpleType name="mode"> > <restriction base="NCName"> > <enumeration value="CreateOrReplace"/> > <enumeration value="CreateOrVersion"/> > <enumeration value="CreateOnly"/> > </restriction> > </simpleType> > -Ref the global type in Submit/UpdateObjectsRequest > <element name="SubmitObjectsRequest"> > <annotation> > <documentation xml:lang="en">This SubmitObjects protocol allows a client to submit RegistryObjects to the server. It also allows a client to completely replace existing RegistryObjects in the server.</documentation> > </annotation> > <complexType> > <complexContent> > <extension base="rs:RegistryRequestType"> > <sequence> > <element name="RegistryObjectList" type="rim:RegistryObjectListType" minOccurs="0" maxOccurs="1"/> > <element name="ObjectRefList" type="rim:ObjectRefListType" minOccurs="0" maxOccurs="1" /> > </sequence> > <attribute name="mode" type="tns:mode" use="optional" default="CreateOrReplace"/> > </extension> > </complexContent> > </complexType> > </element> > <element name="UpdateObjectsRequest"> > <annotation> > <documentation xml:lang="en">This UpdateObjectsRequest allows a client to updates elements and attributes within RegistryObjects already existing in the server.</documentation> > </annotation> > <complexType> > <complexContent> > <extension base="rs:RegistryRequestType"> > <sequence> > <!-- Query and ObjectRefList select objects to update --> > <element name="Query" type="rim:QueryType" minOccurs="0" maxOccurs="1" /> > <element name="ObjectRefList" type="rim:ObjectRefListType" minOccurs="0" maxOccurs="1" /> > > <!-- Specifies how to update selected objects --> > <element name="UpdateAction" type="tns:UpdateActionType" minOccurs="1" maxOccurs="unbounded"/> > </sequence> > <attribute name="mode" type="tns:mode" use="optional" default="CreateOrReplace"/> > </extension> > </complexContent> > </complexType> > </element> > Issue: There is a mode attribute in UpdateActionType. Is there too many mode attributes and is this confusing? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://wxforge.wx.ll.mit.edu:8080/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira--- End Message ---
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]