[Dspace-tech] Do I need to remove the Cocoon cache files every time I make a change that affects the XMLUI?

2011-06-16 Thread Galewsky, Dan
Recently I was changing the browse indices for my Dspace 1.7.2 installation in my dspace.cfg -- for example : webui.browse.index.1 = datecreated:metadata:dc.date.created:date The problem I ran into was that even after restarting Tomcat and my browser - my changes did not show up in the

Re: [Dspace-tech] Do I need to remove the Cocoon cache files every time I make a change that affects the XMLUI?

2011-06-16 Thread Pottinger, Hardy J.
Hi, Dan, it was good to meet you at OR11. I don't know the official answer to this, but I do know my voodoo answer is, yes, I make it a habit to clear the Cocoon cache if I ever change anything in the XMLUI. I do it often enough that I'd like to develop a button for the XMLUI admin control panel

Re: [Dspace-tech] Do I need to remove the Cocoon cache files every time I make a change that affects the XMLUI?

2011-06-16 Thread Tim Donohue
Hi Dan Hardy, There is supposedly a way to trigger Cocoon to 'clear' its cache via the ClearCacheAction built into Cocoon. See: http://comments.gmane.org/gmane.text.xml.cocoon.user/61537 I just tried this out locally in my XMLUI, and it *seems* to work (at least with a few extremely simple

Re: [Dspace-tech] Do I need to remove the Cocoon cache files every time I make a change that affects the XMLUI?

2011-06-16 Thread Tim Donohue
Neglected to mention in my previous email: Once you apply the previously sent patch, you should be able to clear the Cocoon cache by visiting: http://localhost:8080/xmlui/clearcache Again, it will return a bunch of XML (which is Cocoon Status Info). But, in that XML will be an section like:

Re: [Dspace-tech] Do I need to remove the Cocoon cache files every time I make a change that affects the XMLUI?

2011-06-16 Thread Tim Donohue
Hardy Dan, Ok, after a bit more playing around, here's a slightly updated version of the patch that shows it seems to be working (see attached). This updated version adds an additional option: http://localhost:8080/xmlui/statusinfo - will now show the Cocoon Status XML doc (as a base