tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Moved: (TAP5-838) Tapestry should provide a list of known Symbols and providers
Date Thu, 03 Sep 2009 18:03:57 GMT

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

Howard M. Lewis Ship moved TAPESTRY-2742 to TAP5-838:
-----------------------------------------------------

           Issue Type: Bug  (was: New Feature)
    Affects Version/s:     (was: unspecified)
                  Key: TAP5-838  (was: TAPESTRY-2742)
              Project: Tapestry 5  (was: Tapestry)

> 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: Bug
>            Reporter: Peter Stavrinides
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message