[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-404) Expose underlying Asset source in the individual API's

[Andrew Rubinger (JIRA)]

    [ https://issues.jboss.org/browse/SHRINKWRAP-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689317#comment-12689317 ] 

Andrew Rubinger commented on SHRINKWRAP-404:
--------------------------------------------

Assuming that we don't intend on exposing this in Asset, but rather directly in some Asset impls as indicated, this looks OK to me.  The user would have to do type checking and cast to the appropriate Asset subtype to get at the info.
                
> Expose underlying Asset source in the individual API's
> ------------------------------------------------------
>
>                 Key: SHRINKWRAP-404
>                 URL: https://issues.jboss.org/browse/SHRINKWRAP-404
>             Project: ShrinkWrap
>          Issue Type: Feature Request
>            Reporter: Aslak Knutsen
>
> In some cases it is interesting to get the 'real source' of an Asset beyond the InputStream. Where on disk is the FileAsset read from?
> Both for Tooling integration and e.g. the JRebel Arquillian extension it is needed to know where a source came from to do the linking.
> File FileAsset.getFile
> String ClassLoaderAsset.getResource
> Class<?> ClassAsset.getClass
> etc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira