cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <acoli...@nc.rr.com>
Subject Re: Donating Portal and Authentication Components to the Cocoon project
Date Mon, 21 Jan 2002 13:49:03 GMT
On Mon, 2002-01-21 at 06:08, Matthew Langham wrote:
> As some of you already know, our company has built a complete middleware
> solution around Cocoon. This product, named "sunShine", is successfully
> being used to build a variety of different solutions for various customers
> here in Germany. sunShine applications range from Web portals to XML based
> workflow systems.
> 
> We think Cocoon is an ideal solution for building XML applications and are
> proud to be a part of this great community. In the past we have donated
> smaller components, Carsten's development efforts and other bits and pieces
> to the Cocoon project. We are also doing our best to increase visibility for
> Cocoon by writing articles for magazines and speaking at conferences about
> Cocoon.
> 
> Although the current primary use of Cocoon is as a Web publishing framework

I think the devil of this is in the details of what Cocoon 2
expands/allows as the meaning of "web publishing".

> we see great potential for integrated components that provide such things as
> authentication and portal capabilities. To honor this we are willing to
> return parts of sunShine back to the Cocoon project. These parts will
> include Cocoon components for authentication, session management and
> building portals. All of these components adhere to the Cocoon architecture
> and are "tried and trusted".
> 
> Here is a brief description:
> 
> The authorization components allow the integration of given data-sources
> (e.g. databases that may already contain user information) and provide a
> means of protecting pipelines so that only authorized users can access the
> defined resources.
> 
> The portal engine is totally SAX-based and is integrated into the sitemap.
> Portals can be described in an XML format. Content can be defined for the
> portal using regular Cocoon pipelines. Based on the authorization
> components, a portal generator "gets" the portal description for a user and
> streams the complete portal content into the pipeline. A following
> stylesheet transformation transforms this into HTML.
> 
> 
> We have discussed this move with several people from the Cocoon community
> and have received tremendous feedback. Therefore Carsten is currently
> working to bring the components in line with an upcoming Cocoon release and
> we will be donating them (along with documentation, samples etc.) in the
> near future. Probably around the middle of February.
> 
> In the meantime please contact us if you would like any further information.
> 
> Best regards
> 
> Matthew Langham / Carsten Ziegeler
> 
> --
> Open Source Group               sunShine - Lighting up e:Business
> =================================================================
> Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> Tel:+49-5251-1581-30  mlangham@s-und-n.de - http://www.s-und-n.de
> =================================================================
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 
-- 
www.superlinksoftware.com
www.sourceforge.net/projects/poi - port of Excel format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
			- fix java generics!


The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


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


Mime
View raw message