You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ulrich Stärk (JIRA)" <ji...@apache.org> on 2011/02/17 15:16:24 UTC

[jira] Updated: (TAP5-838) Tapestry should provide a list of known Symbols and providers

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

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

    Issue Type: Improvement  (was: Bug)

> Tapestry should provide a list of known Symbols and providers
> -------------------------------------------------------------
>
>                 Key: TAP5-838
>                 URL: https://issues.apache.org/jira/browse/TAP5-838
>             Project: Tapestry 5
>          Issue Type: Improvement
>            Reporter: Peter Stavrinides
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> SymbolSourceImpl Contains two key elements: a list of providers; and a map of Symbols. When using SymbolSource, the assumption Tapestry makes is that the name of a Symbol is always known in order to do a Symbol lookup. 
> Why shouldn't these elements in SymbolSourceImpl be exposed since they are immutable?
> private final List<SymbolProvider> providers;
> private final Map<String, String> cache = CollectionFactory.newConcurrentMap();
> Its a disadvantage not having access to a list symbol names, and not being able to query for where the Symbols resides, the lack of these two features limits the usefulness of Symbols in Tapestry.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira