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

[Aslak Knutsen (JIRA)]

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

Aslak Knutsen commented on SHRINKWRAP-404:
------------------------------------------

In theory we could have had something like "T Asset<T>.getSource()" but it wouldn't really help, you would still need to do the type checking to figure out T and if T is something you can work with.

We could standardise on Type getSource, even tho not enforced by the Asset interface.

{code}
File FileAsset.getSource()
String ClassLoaderAsset.getSource()
Class<?> ClassAsset.getSource()
{code}
                
> 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