OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [regrep-comment] How to send back id and versionName?


Perhaps a more efficient alternative is to return an ObjectRefListType instead of a RegistryObjectList. Further, the list of ObjectRefType MUST have same order and count as original RegistryObjects.

Sent from my Cyanogen phone

On Aug 6, 2015 3:42 PM, Farrukh Najmi <farrukh@wellfleetsoftware.com> wrote:

Hi Harald,

I believe you are correct that this is an oversight in the RegRep 4.0 specs. Your proposed solution of returning a RegistryObjectList within the RegistrResponse is a good solution. Please file an issue within RegRep Jira and include your proposed solution. Thank you.

Sent from my Cyanogen phone

On Aug 5, 2015 10:51 AM, "Krause, Harald (Dataport)" <harald.krause@dataport.de> wrote:

Hello RegRep-experts,

 

an issue regarding the submitObjects-request/resonse is ambiguous for me:

 

According to the id/lid-rules for the submitObjects-operation there are two situations where the server must create the id of an RegistryObject:

-          If client at CreateOnly hasn’t specified the id

-          If at CreateOrVersion a new unique id for an instance is required

 

How should the client be informed about the id created by server? Similar issue applies to versionName, cause submitting client should know about too.

 

A solution would  be sending back all RegistryObjects within the RegistryResponse - enriched with new id and versionName. I suppose it’s not an violation of the spec.

Would that be the recommended approach?

 

 

I would be glad to have your explanation.

Kind regards

Harald Krause (Dataport)

 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]