[
https://issues.apache.org/jira/browse/TAPESTRY-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572083#action_12572083
]
Kalin Krustev commented on TAPESTRY-1924:
-----------------------------------------
Yes, throwing an exception also seems good and removing toURL from
org.apache.tapestry.ioc.Resource is also going to make interface simpler. But
when I looked the source it seemed simpler to keep toURL. Howard, it's your
decision if it will be kept, my issue was for supporting resources coming from
stream.
> Allow for templates coming from stream
> --------------------------------------
>
> Key: TAPESTRY-1924
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1924
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core, tapestry-ioc
> Affects Versions: 5.0.6
> Reporter: Kalin Krustev
>
> In the current version Tapestry parses templates coming from java.net.URL. If
> the template is not in the filesystem (for example coming from database), it
> is more easier to implement this if Tapestry can parse the template coming
> from stream.
> My suggestion is to extend the org.apache.tapestry.ioc.Resource interface
> with one more method:
> InputStream toStream();
> which will be called insted of calling toURL().openStream() when parsing the
> template.
> If this interface is extended in this way, Tapestry should expect
> org.apache.tapestry.ioc.Resource.toURL() to return null even when the
> resource exists(but does not have an URL).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
