[opencms-dev] CmsJspNavBuilder->getSiteNavigation

[Achim Westermann]

Hi Thomas,

I'd also recommend Kai's suggestion. Done in 5 Seconds (excluding the
first request from server strategy).

1. Go to the jsp in VFS that renders the navigation.
2. Right click, choose "properties" and set the cache property to "uri"
(in case it is not a whole site navigation).

The output of the jsp is stored in flexcache with one version per
different URI.

cheers,
Achim

On 02/28/2014 11:44 AM, T.Kluge at t-systems.com wrote:
> Hi there,
> 
> thanks for all the suggestions :-) 
> 
> Indeed there is no need to store the menue for every user. The menue depends on the roles of the user.
> So I first have to check which roles the users has and get a prepared cached menu from a store.
> Unfortunately we have a bunch of user groups and some combinations, but nothing is perfect.
> 
>> trigger an event after each publish process, which requests the page once
> Great idea! It looks like I could use org.opencms.main.I_CmsEventListener.EVENT_PUBLISH_PROJECT for that.
> 
>> OCEE offers cache on DB request
> Ah OK.
> 
> Thanks again,
> Thomas
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Schliemann, Kai
> Gesendet: Freitag, 28. Februar 2014 11:31
> An: The OpenCms mailing list
> Betreff: Re: [opencms-dev] CmsJspNavBuilder->getSiteNavigation
> 
> Hi Thomas,
> a workaround comes to my mind.
> When you are using the cache parameter solution you could trigger an event after each publish process, which requests the page once. So the first call will come from your server and not from one of the users.
> I know it is just a workaround. But maybe it helps.
> 
> Best regards
> Kai
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev
> 
> 
>