[
https://issues.apache.org/jira/browse/TAP5-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577589#comment-13577589
]
Borut Bolcina commented on TAP5-1930:
-------------------------------------
Yes, that would be of great benefit. One could inject SymbolSource into service
and then dynamically build "things" in that service based on defined symbols in
the properties file for example.
This way you do not have to touch the source code, compile and deploy, but only
modify configuration file (property file), or if symbols are coming from
database - change some records, and the application would be dynamically
configured.
> Feature request: SymbolSource.getSymbolNames()
> ----------------------------------------------
>
> Key: TAP5-1930
> URL: https://issues.apache.org/jira/browse/TAP5-1930
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.3.3, 5.4
> Reporter: Lance
> Priority: Minor
>
> I'm currently integrating DWR with Tapestry and I'd like to pass all of the
> "dwr.*" symbols from tapestry to DWR. At the moment, I need to hard code the
> possible symbol names and try/catch RuntimeException around
> SymbolSource.valueForSymbol(symbolName) for each possible symbol.
> It would be great if the following method could be added to SymbolSource
> public Collection<String> getSymbolNames()
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
