[EMAIL PROTECTED] wrote:
Hi Ard,
SlideJMSEventListener worked like magic! My cms now picks up the changes
almost instantly. Thank you so much for the help!
Now another question for you: is there an easy way to start the workflow
programmatically, so my new files would show up in the CMS TODO list?
I'm not aware of any easy way. The two things I can think of are: extend
the cms to have a url you can externally call to start the workflow on a
document or extend the cms to create an extra todo list based on a
property you set yourself.
Regards,
Bart
Regards,
Jun
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ard
Schrijvers
Sent: Monday, June 23, 2008 9:14 AM
To: Hippo CMS development public mailinglist
Subject: RE: [HippoCMS-dev] import document files
Hello,
> Hi Ard,
>
> After I do filesync and propertyset, my new files don't show
You do a propertyset in the repository outside of the cms, right? This
should trigger a jms event.
> up in the CMS until I manually "touched" the directory by
> creating a file or delete or file. I've tried repair index -
> the index seems to be alright.
I might because of an effienciency part in the cms, where the cms evicts
items without needing a jms. You might want to try to do the following
and let me know wether it works:
In the cocoon.xconf of the cms, change
nl.hippo.cocoon.caching.CMS_SlideJMSEventListener
Into
nl.hippo.cocoon.caching.SlideJMSEventListener
The CMS_SlideJMSEventListener handles jms events only the document that
changed, where the SlideJMSEventListener does it recursively to the
root. So, the SlideJMSEventListener is less efficient, but for example
in clustered environments, you need to have this one instead of
CMS_SlideJMSEventListener: you can only use CMS_SlideJMSEventListener
when one single cms instance is doing all the changes: that instance
knows how to invalidate its own caches. When it depends on changes from
outside the cms, it needs to recursively invalidate its caches, hence
use SlideJMSEventListener.
Let me know wether this solves your problem,
Regards Ard
> I can't think of anything else that I can do other than the
> lack of an event that triggers the CMS to pick up the new
> files. Is this assumption correct? If not, which direction
> would you suggest me to investigate the problem further?
>
> Thanks a lot!
> Jun
>
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
<a href=ttp://hippocms-dev.markmail.org/">MarkMail</a> and <a
href=ttp://www.nabble.com/Hippo-CMS-f26633.html">Nable</a>.
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
<a href=ttp://hippocms-dev.markmail.org/">MarkMail</a> and <a
href=ttp://www.nabble.com/Hippo-CMS-f26633.html">Nable</a>.
--
Hippo B.V. - Amsterdam
Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466
Hippo USA Inc. - San Francisco
101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646
-----------------------------------------------------------------
http://www.onehippo.com - [EMAIL PROTECTED]
-----------------------------------------------------------------
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
<a href="http://hippocms-dev.markmail.org/";>MarkMail</a> and <a
href="http://www.nabble.com/Hippo-CMS-f26633.html";>Nable</a>.
