|
I have the current CVS version of Jetspeed running under
Tomcat 3.1
It took a bit of doing but I learned a lot about the internals
of Turbine and Jetspeed in the process.
I'm working on developing an OpenSource workflow enactment
service that seems like a good fit with Jetspeed. My intention is to make use of
a subclass of CocoonPortlet as a way of managing user interactions.
Some emails in the jetspeed archive make me question whether
this portlet is still supported. Is this the case?
I know that there are problems with the ProducerFromRequest
class. I have tried to cobble together something that works by adding this class
back into my personal copy of Cocoon 1.8 but this leads to other problems,
most notably it looks like the Cocoon Engine doesn't like the null path in the
JetspeedServletRequest that the JetSpeedCocoon service leaves when it includes
the stylesheet as a PI in the generated document.
I've been fiddling around with various tweaks and combinations
of jars, but to no avail. I thought before I go much further I should see the
lay of the land.
Questions:
1. Does CocoonPortlet work in the current CVS and it's just a
matter of me playing around with it to get it to work, or is it known to be
broken.
2. Any advice on how to fix it? I'll gladly post it back
here.
3. Would it make sense for me to try to modify the
CocoonPortlet to make use of the ProducerFromFile class or would this cause
other problems.
I know that there are many issues with Cocoon 1.8 but I want
to get something working as a proof of concept in the hopes that Cocoon 2 will
be available in time for my project to get real.
I'm working on a proposal for this workflow enactment service.
I want to make sure I understand the Jetspeed architecture before I take it much
further.
Assuming I can make this work, I hope to post the proposal
here in the next week or so.
Ben Galewsky
|
