Hi, "my cms dies" means that after the trigger tried to ask the extension, all the request to the CMS returns nothing, and I don't have any entry in the request log file.
Alaric 2009/12/28 Jasha Joachimsthal <[email protected]> > If you're using the server-side Javascript for replication or an old > version of the repository (< 1.2.15) the CMS responds very slow when > replication fails. It waits for a response code from the repository > before it reloads the workflow. Please check the repository logs for > replication failures. > > Jasha > > 2009/12/23 Dennis Dam <[email protected]>: > > the replicate trigger is a component in your Hippo Repository , based on > the > > replication feature (see [1])? > > > > What do you mean with "my cms dies" ? :) Do you have specific errors from > > logfiles? > > > > [1] > > > http://wiki.onehippo.com/display/CMS/6.+Hippo+Repository+Configure+Replication > > > > On Tue, Dec 22, 2009 at 9:15 AM, Hippo WCMTech <[email protected] > >wrote: > > > >> Hi Hippos, > >> > >> I've developed an import system based on the replicate trigger... when a > >> specific file comes in the repository, this file is splited and several > >> documents are created in the repository. > >> > > > > > > > > > >> My problem is that my client doesn't want to use the explorer view and > wish > >> to see documents directly in the todo list, which doesn't work if there > is > >> no workflowId. > >> > >> So I've tried: > >> 1) The trigger calls an extension of the cms who create the workflow > (like > >> the explorer) and send back the Id: the extension works very well from > the > >> browser... but my cms dies when the trigger use it. I think that this > >> relates to the fact that the document isn't in the repository yet. > >> 2) An extractor calling the same extension as above: works good in local > >> but > >> has bad perf when deployed on the development server. > >> > >> So... here is my question: is there a way to do it ? Is there someone > who > >> already tried to something like this ? > >> > >> Thanks in advance, > >> > >> Alaric > >> ******************************************** > >> Hippocms-dev: Hippo CMS development public mailinglist > >> > >> Searchable archives can be found at: > >> MarkMail: http://hippocms-dev.markmail.org > >> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > >> > >> > > > > > > -- > > 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: > > MarkMail: http://hippocms-dev.markmail.org > > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > > > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
