[
https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969220#action_12969220
]
Chris A. Mattmann commented on OODT-69:
---------------------------------------
Hey Brian:
bq. but element id depends on the repository manager implemented . . . in the
xml version it is typically urn:<ns>:<element_name>, however if a data source
one where implemented, element id most likely would be an integer
This is not *strictly* true. In fact, you can mix and match (we have in the
past, even on OCO) where we used a DataSourceCatalog, but an XML repo layer, in
which case the element ID would not be an integer, it was *still* a URN. Also
the scheme you propose for elements that's usually used is just *one of many
possible* schemes that could be used to avoid collision.
bq. thus a user querying the filemgr would then have to be aware of which
repository manager was being used; using element name / product type to
determine element id hides this from the user.
Not necessarily. We could also come up with smart names for ProductTypes that
avoided this collision, or even expose a query criteria method using element
IDs (the way it *used* to work before you changed it :) ). That way
o.a.oodt.cas.filemgr.structs.QueryCriteria would actually be a mapping of
element ID to value.
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
>
> - ProductTypes may have Elements with same name but different meaning . . .
> thus using the ValidationLayer to get an element by name without taking the
> ProductType into consideration can cause the wrong Element ID to be sent to
> the underlying Catalog
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
