You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/04/28 23:39:31 UTC
[jira] Updated: (TAP5-223) Allow properties files (on classpath or
in the context) to be used as SymbolProviders
[ https://issues.apache.org/jira/browse/TAP5-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-223:
--------------------------------------
Priority: Minor (was: Major)
Assignee: Howard M. Lewis Ship
Summary: Allow properties files (on classpath or in the context) to be used as SymbolProviders (was: add PropertiesFileSymbolProvider)
I'm glad these are going into the internal package because I have some issues with them, primarily with the ContextResourceSymbolProvider ... that is, the order of operations for starting up a Tapestry web application means (to me) that it is highly likely that you will not have a Context available when it is necessary to contribute to the SymbolSource. Perhaps I'm missing something. I'm much more comfortable with the ResourceSymbolProvider.
> Allow properties files (on classpath or in the context) to be used as SymbolProviders
> -------------------------------------------------------------------------------------
>
> 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
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Attachments: PropertiesFileSymbolProvider.patch.txt, 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.