Comments on: Hippo cms workflow with events

By: jettro

jettro — Sat, 28 Mar 2009 22:53:39 +0000

Thanks Frank, I like the idea

By: Frank van Lankvelt

Frank van Lankvelt — Sat, 28 Mar 2009 22:22:20 +0000

Hi Jettro, cool stuff!
It might be nice to know how to make this dynamic, i.e. such that one can add and remove listeners at runtime.
You could do this by creating a separate type (cust:workfloweventfolder?) for the folder that contains the cust:workflowevent nodes. In the daemon code, register a jcr listener for this node (by type, so that there can be multiple folders) and (un)register a workflow event listener when node added/removed events are received.
Administrators might appreciate such functionality…

By: jettro

jettro — Tue, 17 Mar 2009 08:15:28 +0000

He Freddie, good to be in your territory now . If I understand you correctly I can say: Yes. JackRabbit does have the concept of document types. If you check the first code block with the CND file, this is a type definition for the nodes in the repository. With these types you can specify what a certain item looks like. You can use inheritance within types as well as aggregation relations.

Meta-data is handled using normal properties except for a few basic properties like Node name, creation date, etc.

Is that an answer to your question?

By: Freddie

Freddie — Mon, 16 Mar 2009 23:10:45 +0000

Hi Jettro,

I have a question. Is JackRabbit truly a Repository or is it just a sexy name for an Archive?

According to the literature a Reposítory contains the definitions of the What in your own words CLASS DEFINITIONS and not Instances. To me Content is an Instance of a certain type and described by NOT what everyone think is META-DATA but should be called Attributes. META-DATA describes the structure, rules, entities (ontologie). Content instances are stored in an Archive (for short or long term).

Curious to hear from you