[
https://issues.apache.org/jira/browse/CLK-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711998#action_12711998
]
Adrian A. commented on CLK-405:
-------------------------------
> I think we need a MenuFactory to support alternative caching strategies.
Whatever solution solves the actual problem (together with CLK-407 to make the
component usable) would be OK.
Right now, most uses simply make their own Menu by hacking this class: in fact,
in all Click based web applications, I've never seen the "official" click Menu
used, but always a hack (except of course click-examples :) )
> Menu improvements - allow setting the cache strategy.
> -----------------------------------------------------
>
> Key: CLK-405
> URL: https://issues.apache.org/jira/browse/CLK-405
> Project: Click
> Issue Type: Improvement
> Components: extras
> Reporter: Demetrios Kyriakis
>
> Please improve the Menu Control, by allowing the user to set the chache
> stragety.
> Right now the cache strategy seems to be "application" (or JVM instance) only.
> This is very limiting, making the existing Menu Control useless for most user
> applications, thus forcing the users
> to make their own menu controls (or the hack the original one).
> Please allow setting the cache strategy also to "session", and "request" (or
> "page" if the page is stateful).
> (even if the default remains to "application" - the ensure the compatibility
> with existing applications).
> Thank you,
> Demetrios.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
