Nick Goupinets wrote:
Hi Matt,
I do not know if it will help, but I think that the profile is cached once for every successful log in. So normally, it should not be necessary to restart tomcat or reload cocoon just to get the latest profile available.
Yes, this is how it should work.
In case the changes to the profile were made while a user is still logged in, they should appear after the user logs out and logs in again. If it's necessary to avoid this "re login" process, you can go directly to the PortalService and invalidate the cached profile (or a part of it) by clearing up the corresponding profile attribute.
For example, in case portal layout needs to be reloaded, this will get it done:
PortalService service = (PortalService) this.manager.lookup(PortalService.ROLE);
service.removeAttribute("Layout:portal");
I have a feeling that trying to update the confguration during a session won't always work. I know that objects created for JSR-168 portlets keep references to the copletinstancedata object. The PageLabel support I added also doesn't allow the layout to be changed during a session, at least it doesn't yet.
Sincerely, Nick.
Matt Innes wrote:
Hi,
I am building an intranet using Cocoon 2.1.5.1 running in Tomcat 5.0.28 on XP. I have structured my project identically to the sample (with coplets, profiles, resources subdirectories). I have noticed that Cocoon caches the profile files (portal.xml) by default i.e. you need to restart Tomcat to pick up any changes to these files. Is there an easy way to switch this off? Thanks, Matt
Matt Innes, UTB Consulting [EMAIL PROTECTED] 07795 300 735
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
