felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-3733) Clarify icon location
Date Sun, 28 Oct 2012 14:39:12 GMT

     [ https://issues.apache.org/jira/browse/FELIX-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Felix Meschberger resolved FELIX-3733.

    Resolution: Fixed

Probably we should not catch the exception (we cannot properly interpret it anyway). In addition,
the icon has been defined and one candidate has been found. But that candidate is not available.
So I reading the JavaDoc I would think, it is ok to throw an exception while opening the InputStream
to the candidate found.
> Clarify icon location
> ---------------------
>                 Key: FELIX-3733
>                 URL: https://issues.apache.org/jira/browse/FELIX-3733
>             Project: Felix
>          Issue Type: Task
>          Components: Metatype Service, Specification compliance
>    Affects Versions: metatype-1.0.4
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For:  metatype-1.0.6
> The Metatype Service specification states for the location value of the icon element
(Table 105.1 in section 105.7.1):
>      The resource is a URL. The base URL is assumed to be the XML file
>      with the definition. I.e. if the XML is a resource in the JAR file, then this
>      URL can reference another resource in that JAR file using a relative URL.
> Our current implementation takes this definition and uses the XML resource URL as the
base URL to create the Icon URL.
> For example: If the icon resource path is "icon/sample.png" and the XML resource URL
is "file://bundle-5/OSGI-INF/metatype/sample.xml" then the icon resource URL would be assumed
to be "file://bundle-5/OSGI-INF/icon/sample.png".
> In contrast the current OSGi CT work-in-progress expects the URL to be relative to the
defining bundle.
> It must be clarified which reading is correct.

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

View raw message