[
https://issues.apache.org/jira/browse/TAPESTRY-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555719#action_12555719
]
Howard M. Lewis Ship commented on TAPESTRY-1839:
------------------------------------------------
I'm not certain this is a great idea; SymbolSources look a lot like message
catalogs but have some differences: a symbol value may contain symbols that
are recursively expanded (which might be nice for message catalogs, but is a
new concept). Also, a message key that is unresolved is a warning, a symbol
that can't be resolved is an error (yes, I could catch that exception, but it
would be ugly). Just food for thought.
> Include SymbolSource when looking up component messages
> -------------------------------------------------------
>
> Key: TAPESTRY-1839
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1839
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.6
> Reporter: Dan Adams
>
> If symbols were provided in the component messages then we could do things
> such as setting component defaults that could be overridden by the
> application. I would like to see SymbolSource included when looking up
> messages or make the component message sources configurable or both.
--
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]
