[bcarothers]

That explorer sounds sweet!  How do I get the source of that thing? :-)

I like the idea of having the presentation metadata/template be stored in the repository - after all, aren't templates just content too? 

Were you thinking of something like /jcr:system/dna:views/<format>/<node type> where <format> is some kind of string to discriminate between JCR templates vs. other templates like JSP templates and <node type> is the name of the mixin type? 

One thing to consider in this scheme is that you would have to have the same templates for all workspaces, since the jcr:system graph is generally shared across all workspaces in the repository.  This is probably the desired behavior anyway.

[kukeltje]

Everything is content, a processdefinition is as well. So I'm not sure where to start/end...

Since my initial idea was to use it for storing binary content (pdf, xls etc) and xml, I only need forms to display the xml. jBPM can store it's own forms and since these are related to tasks as wel as to the type of content (which in turn is related to the task again), I still store those in the processdefinition. (maybe a 'modeshape connector to the processdefinition is an idea)

So you are way ahead of me with your question on how to store those, share them (or not) etc..

jcr-explorer is more or less the management ui (management as in task/process, not grey suites)

Cheers,

Ronald

Oh, access to the richfaces jcr-explorer source is trough its svn repo. The richfaces jBPM console is unfortunately not open yet (but a screencast can be found on my blog)