Joshua Lucas wrote:
>
> I needed to have the use of Cocoon in a Turbine application that I'm working
> on so I moved over the code found in Jetspeed. There wasn't any big
> problems in moving the code over but I know have some architecture
> questions...
>
> * If Cocoon support is supposed to be a screen, where will the xml come from
> which will be given to Cocoon?
> The way that I did it was to *chain* screens together, using a 'xml_screen'
> parameter and the ScreenLoader and make it be the second screen's job to
> create the xml.
>
> * Should the xml created automatically have all of the necessary Cocoon
> information (like stylesheet) or should there be a way that a stylesheet can
> be given via parameters?
> I didn't do this in my code but I think it should be a possibility. That's
> the way it is in Jetspeed.
>
> I can send the code if it is wanted.
All the code you need is in the CocoonPortlet. And IMO it should be an
Avalon Block so that we can share the code across Jetspeed and Turbine
without having two code bases. Where the final code goes (Jetspeed vs
Turbine) is up in the air but maybe in the Avalon distribution.
You only really need to give it two things a source XML document and an
XSL document. It should do the work after that.
Kevin
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Open Source Java!"
"For evil to win is for good men to do nothing."
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
