[jira] Commented: (CLK-405) Menu improvements - allow setting the cache strategy.

["Malcolm Edgar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLK-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711971#action_12711971 ] 

Malcolm Edgar commented on CLK-405:
-----------------------------------

I think we need a MenuFactory to support alternative caching strategies.

  // Application wide scope 
  public static Menu getRootMenu() 

  // Application wide scope 
  public static Menu getRootMenu(AccessController accessController) 

  // Application wide scope 
  public static Menu getRootMenu(String xmlPath) 

  // Application wide scope 
  public static Menu getRootMenu(AccessController accessController, String xmlPath) 

  // Session scoped 
  public static Menu getRootMenu(HttpSession session)

  // Session scoped 
  public static Menu getRootMenu(HttpSession session, AccessController accessController)

  // Session scoped 
  public static Menu getRootMenu(HttpSession session, String xmlPath)

  // Session scoped 
  public static Menu getRootMenu(HttpSession session, AccessController accessController, String xmlPath)

 We could refactor the existing static Menu factory methods to use the MenuFactory class static metthods.

> 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.