[overlord-issues] [JBoss JIRA] (SRAMP-204) Identical UUIDs are possible for s-ramp artifacts

[Eric Wittmann (JIRA)]

     [ https://issues.jboss.org/browse/SRAMP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SRAMP-204 started by Eric Wittmann.

> Identical UUIDs are possible for s-ramp artifacts
> -------------------------------------------------
>
>                 Key: SRAMP-204
>                 URL: https://issues.jboss.org/browse/SRAMP-204
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core, Persistence
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> Currently if an artifact with the same UUID is added to the s-ramp repository, it will fail *only* if the artifact is also the same *type*.  In other words, this is currently *not* a conflict:
> POST /s-ramp/core/Document/12345
> POST /s-ramp/core/XmlDocument/12345
> This is because we use the type and model in the JCR path.  So the two artifacts above result in different, non-conflicting paths.
> GET'ing the artifacts will work just fine:
> GET /s-ramp/core/Document/12345
> GET /s-ramp/core/XmlDocument/12345
> Alas, query will result in two artifacts for this query:
> /s-ramp[@uuid = '12345']
> I suggest we remove the model and type information from the JCR path.  Perhaps put artifacts here:
> /s-ramp/artifacts/<btreepath>
> And put ontologies here:
> /s-ramp/ontologies/<uuid>
> And put stored queries here:
> /s-ramp/queries/<uuid>
> Etc...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira