You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Tim Williams <wi...@gmail.com> on 2005/04/13 22:58:21 UTC
workflow on slide
I eventually want a Forrest site that is contained in Slide that has a
workflow engine built on top. It seems that plugging Forrest and
Slide wouldn't be that difficult but I also want it to follow some
sort of workflow which neither has built in. I don't want to go with
a Lenya-like system because the authors will use a more robust
authoring tool like Epic. This thread is the only reference I could
find of anyone talking about a Workflow engine on top of Slide. Have
I overlooked something or is this just something that's generally not
needed or expected that a CMS would have to build on top of the
repository?
http://mail-archives.eu.apache.org/mod_mbox/jakarta-slide-dev/200209.mbox/threads.html
Thanks for any help...
--tim
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Getting access to Request or Session ?
Posted by Jean-Philippe Encausse <Je...@Jalios.com>.
Is there a way to get access to HttpRequest or HttpSession from method
BasicWebdavStore.begin(Service service, Principal principal, Object
connection, LoggerFacade logger, Hashtable parameters) ?
I need to retrieve Security Information from Request , Session ... ?
I don't want to use Principal or I don't know how to override Principal.
Why does the BasicWebdavStore API give a Logger and a Principal it is
very restrictive ?
Regards,
Jp
--
*Jean-Philippe Encausse* - R&D Jalios SA
Jp@encausse.net - http://www.encausse.com - http://www.jalias.com
ICQ: 109796741 - AOL: NextOne6666 - MSN: Nextone6666@hotmail.com
Mob: +33 6 80 75 71 09 - Office: +33 1 39 23 92 83 - Home: +33 1 39 18 90 15
*Do it Once, Use it Twice ~ Do it Twice, Make It Once*
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.7 - Release Date: 12/04/2005
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: workflow on slide
Posted by delbd <de...@oma.be>.
>
> Unfortunately I don't have any good links to existing simple
> workflow engines, I would be as interested as you in any hints!
>
Just for information, we achieved here to integrate slide with the workflow
engine osworkflow (http://www.opensymphony.com/osworkflow), we hope in the
near future to have slide startup workflows and workflows to register for
events in slide, for now the workflow engine is able get it's users/roles
from slide, it store it's instances as slide collections and is able to
attach documents to a running workflow. This all went not without writing
some intermediate components and fighting against the api design of
osworkflow and sometime strange errors from slide api ;)
And today we still have lost of tinhgs to do on the side of osworkflow, so if
you look for an easy to use solution, easy to glue with slide, not your
choice :)
> >>At my day-job company we have a CMS using Slide as repository impl
> >>and Cocoon as presentation engine. This particular CMS uses Cocoon
> >>Flow-script for the controller logic and the workflow processing
> >>is mostly implemented in Cocoon Flow (with some sanity checks
> >>in the Java Repository integration code on top of Slide).
> >
> > Can I ask what CMS you use on top of Slide at work?
>
> Sure; it is a custom open source integration project initially done
> for a Swedish government body. The recepient has not yet decided if
> they want to donate the integration bits back as open source.
>
Make me think of our current work here to have an document archiving system
respecting lots of governement retention rules on top of slide :)
> (Sorry, I know that's not what you wanted to hear.) ;-)
Project will pobably not be open sourced here too :)
>
> Regards,
> Martin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
--
David Delbecq
Royal Meteorological Institute of Belgium
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: workflow on slide
Posted by Martin Kalén <mk...@apache.org>.
Tim Williams wrote:
>>Workflow means a lot of different things to different people,
>>could you specify a bit more what you mean?
>
> I'm thinking something fairly simple. I'm clearly no expert in either
> CMS or WFE's so my terminology coule be a bit off but something like:
>
> o) A document has multiple "states" -- new, in-edit, in-review, published
> o) A simple "routing" logic associated with child nodes of the "site"
> element of site.xml in Forrrest.
> o) Obviously some sort of permissions associated with the routing
> logic above (e.g., person X has the ability to create new content and
> Person Y can "publish" that content.
That's similar to what the Cocoon Flowscript implemented solution I
mentioned do, but this is unfortunately not freestanding enough to
package as a separate workflow handling so I can't help you with code
(and I guess you are not using Flowscript as controller logic anyway).
But just to get you started: it's not much code reuqired to implement
something like this on your own on top of Slide.
Slide kernel gives you all the access control you need and since
repository nodes in Slide can have arbitrary properties, you can easily
define your own property for workflow state, preferrably outside of the
DAV: namespace.
You also mentioned a notification scheme, which would of course also
have to be implemented by something else than Slide.
> I've got a rough idea of what's needed but flexible enough to use
> what's out there (if anything).
Unfortunately I don't have any good links to existing simple
workflow engines, I would be as interested as you in any hints!
>>At my day-job company we have a CMS using Slide as repository impl
>>and Cocoon as presentation engine. This particular CMS uses Cocoon
>>Flow-script for the controller logic and the workflow processing
>>is mostly implemented in Cocoon Flow (with some sanity checks
>>in the Java Repository integration code on top of Slide).
>
> Can I ask what CMS you use on top of Slide at work?
Sure; it is a custom open source integration project initially done
for a Swedish government body. The recepient has not yet decided if
they want to donate the integration bits back as open source.
(Sorry, I know that's not what you wanted to hear.) ;-)
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: workflow on slide
Posted by Tim Williams <wi...@gmail.com>.
On 4/14/05, Martin Kalén <mk...@apache.org> wrote:
> Tim Williams wrote:
> > I eventually want a Forrest site that is contained in Slide that has a
> > workflow engine built on top. It seems that plugging Forrest and
> > Slide wouldn't be that difficult but I also want it to follow some
> > sort of workflow which neither has built in.
>
> Workflow means a lot of different things to different people,
> could you specify a bit more what you mean?
I'm thinking something fairly simple. I'm clearly no expert in either
CMS or WFE's so my terminology coule be a bit off but something like:
o) A document has multiple "states" -- new, in-edit, in-review, published
o) A simple "routing" logic associated with child nodes of the "site"
element of site.xml in Forrrest.
o) Obviously some sort of permissions associated with the routing
logic above (e.g., person X has the ability to create new content and
Person Y can "publish" that content.
I guess all and all, I like the workflow inside Lenya but need
something that's independent of the web interface -- so that I can use
a real authoring tool like Epic or Spy. I'm not sure how the
notification would happen -- maybe email or a web-based queue.
I've got a rough idea of what's needed but flexible enough to use
what's out there (if anything).
>
> > Have
> > I overlooked something or is this just something that's generally not
> > needed or expected that a CMS would have to build on top of the
> > repository?
>
> At my day-job company we have a CMS using Slide as repository impl
> and Cocoon as presentation engine. This particular CMS uses Cocoon
> Flow-script for the controller logic and the workflow processing
> is mostly implemented in Cocoon Flow (with some sanity checks
> in the Java Repository integration code on top of Slide).
> ...
> There are many XML-standards for process descriptions and
> advanced engines to handle them. A quick google led to:
> http://web.openwfe.org/display/openwfe/Home
I'll take a look at that, thanks. Can I ask what CMS you use on top
of Slide at work?
Thanks,
--tim
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: workflow on slide
Posted by Martin Kalén <mk...@apache.org>.
Tim Williams wrote:
> I eventually want a Forrest site that is contained in Slide that has a
> workflow engine built on top. It seems that plugging Forrest and
> Slide wouldn't be that difficult but I also want it to follow some
> sort of workflow which neither has built in.
Workflow means a lot of different things to different people,
could you specify a bit more what you mean?
> Have
> I overlooked something or is this just something that's generally not
> needed or expected that a CMS would have to build on top of the
> repository?
At my day-job company we have a CMS using Slide as repository impl
and Cocoon as presentation engine. This particular CMS uses Cocoon
Flow-script for the controller logic and the workflow processing
is mostly implemented in Cocoon Flow (with some sanity checks
in the Java Repository integration code on top of Slide).
Workflow state tracking is done by a specific property on each
Slide node (with predetermined constant values for each state).
For more advanced workflow processing, eg with some sort of
description language and processing engine, I think you sould
try to find and existing implementation from the bussiness
process workflow side of things (rather than CMS/publishing).
There are many XML-standards for process descriptions and
advanced engines to handle them. A quick google led to:
http://web.openwfe.org/display/openwfe/Home
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org