[overlord-issues] [JBoss JIRA] (SRAMP-182) Make artifact type detection less generic (atom layer)

Eric Wittmann (JIRA) jira-events at lists.jboss.org
Thu Oct 3 07:26:03 EDT 2013


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

Eric Wittmann updated SRAMP-182:
--------------------------------

    Fix Version/s: 0.4.0 - API Management
                       (was: 0.3.1 - jBPM - bugfix 1)

    
> Make artifact type detection less generic (atom layer)
> ------------------------------------------------------
>
>                 Key: SRAMP-182
>                 URL: https://issues.jboss.org/browse/SRAMP-182
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Atom Binding, Core
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>            Priority: Minor
>             Fix For: 0.4.0 - API Management
>
>
> Currently the artifact type detection methods are very generic and do not consider the context.  There are two basic scenarios where an artifact type must be detected from an Atom Entry:
> 1) atom summary entries
> 2) full atom entries
> In the former case we need to figure out the type based on meta-data in the Entry, such as the URL, or from the 'x-s-ramp:2010:type' Category (for example)
> In the latter case, we should look at the wrapped artifact itself (there will be an <artifact> custom element in the Atom Entry with a single child - that single child is the full artifact meta-data, and the element name will indicate the type).
> Currently we just try both under all circumstances.  I want to change from "getArtifactTypeFromEntry" to two methods:
> getArtifactTypeFromSummaryEntry
> getArtifactTypeFromFullEntry
> Callers must know what they have (summary or full).  This should be known in all cases.

--
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


More information about the overlord-issues mailing list