Thank you for the response.
Launching an http request from the trigger in order to activate a Cocoon
pipeline will allow me to do what I wanted.
My mistake was to think I could use all this in Cocoon with some kind of=
action that would have waited for a notification just like in a socket=20
On 8/29/05, Wolfgang Meier <wolfgangmm@...> wrote:=20
> > I am using Cocoon, and I wish to use the triggers features from eXist t=
> > 'launch' pipelines in cocoon.
> > Typically, I am trying to 'launch' pipes in Cocoon depending on trigger=
> > eXist.
> > For instance:
> > If the doc 'test' is modified in eXist, an action (eXistTriggerAction=
> > example) would be notified allowing the processing of the pipe to=20
> > in Cocoon
> I'm not quite sure what you're trying to achieve. Why should the
> Cocoon pipe be notified?
> Basically, a trigger can do anything, but it only has access to
> eXist's internal api, not the Cocoon environment. What you could do is
> to launch some http request from the trigger which activates a Cocoon
> > The second point is that I am using the RPC protocol for my application=
> > order to depend less on eXist APIs). Are thre some RPC APIs available t=
> > triggers ?
> No, the trigger is executed on the server, so the class implementing
> the trigger needs to be in the classpath of the server. You can define
> a trigger by storing the special document collections.dbx into
+33 (0) 675 190 455