cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Homeijer <M.Homei...@devote.nl>
Subject RE: Cocoon and Jetspeed portal
Date Tue, 15 Jan 2002 14:30:31 GMT
Hi,

Would you care to explain which concepts you introduced in your cocoon setup
to achieve this?
Wouldn't it be possible to use jetspeed or turbine instead of building and
maintaining your own code?

TIA,
Michael


-----Original Message-----
From: Lewis, Andrew J [mailto:Andrew.Lewis@jbosc.ksc.nasa.gov]
Sent: dinsdag 15 januari 2002 15:08
To: 'cocoon-dev@xml.apache.org'
Subject: RE: Cocoon and Jetspeed portal


I have a similar project - I'm stealing a few things from Jetspeed, and
building on Cocoon. I have really spent a lot of time with Jetspeed, and
while the concepts are great and thre is some cool stuff there, I think
Coccon is a better framework for a portal.



> ----------
> From: 	Michael Homeijer[SMTP:M.Homeijer@devote.nl]
> Reply To: 	cocoon-dev@xml.apache.org
> Sent: 	Tuesday, January 15, 2002 4:29 AM
> To: 	cocoon-dev@xml.apache.org
> Subject: 	Cocoon and Jetspeed portal
> 
> Hi,
> 
> For a portal prototype I am trying to describe how it should be built
using
> Cocoon. I have read about jetspeed and I tried to implement a portal page
in
> Cocoon. If i could use the portlet mechanism from jetspeed, this would
> really simplify building a portal with Cocoon.
> 
> I can see two ways of achieving this:
> - Access cocoon from jetspeed. This would mean producing portlet contents
> from Cocoon. This would be possible by parsing serialized output, but this
> way you would probably lose a lot of benefits portlets in jetspeed have.
> Another way would be to call the Cocoon environment (something like the
> CLI?) and outputting the SAX events in jetspeed. I haven't seen a clean
way
> to output the sax events in jetspeed, but haven't look at it detailed yet.
> 
> - Build portal actions, portal layout stylesheet, portlet logic sheets and
> portlet configuration layout in Cocoon. This would be a lot more work and
> the overlap with jetspeed would probably be very big. I cannot see if
> jetspeed is "componentized" enough to use these components in Cocoon.
> 
> Can anyone comment on this or give me some hints on the approach.
> 
> TIA,
> 
> Michael Homeijer
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message