You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Ulrich Stärk (JIRA)" <ji...@apache.org> on 2009/04/20 14:08:47 UTC

[jira] Updated: (TAP5-223) add PropertiesFileSymbolProvider

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

Ulrich Stärk updated TAP5-223:
------------------------------

    Attachment: ResourceSymbolProvider.java

Howard, would something like this qualify for such a factory method? The only thing I see that will be problematic is that the individual Resource implementations are internal so the user shouldn't contribute them directly. We'd need another service that maps from a list of strings like "cp:org/example/foo", "context:foo/bar" and so on to the respective Resource implementations.

Uli

> add PropertiesFileSymbolProvider
> --------------------------------
>
>                 Key: TAP5-223
>                 URL: https://issues.apache.org/jira/browse/TAP5-223
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-ioc
>    Affects Versions: 5.0.15
>            Reporter: Neeme Praks
>         Attachments: PropertiesFileSymbolProvider.patch.txt, ResourceSymbolProvider.java, TAP5-223.txt
>
>
> add a possibility to resolve symbols from properties file (PropertiesFileSymbolProvider).
> For reference, see:
> http://thread.gmane.org/gmane.comp.java.tapestry.user/65656

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.