Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <41F29958.9010805@apache.org>
Date: Sat, 22 Jan 2005 19:20:08 +0100
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: WishFull thinking JX and SessionContext Authentication
References: <csrfka$lku$1@sea.gmane.org> <41F14560.9080100@apache.org>
 <41F17A62.4060600@mobilebox.pl> <41F237E3.9050708@apache.org>
 <41F2428C.9090804@mobilebox.pl>
In-Reply-To: <41F2428C.9090804@mobilebox.pl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Leszek Gawron wrote:
> don't we have a pluggable object model ? :))
> 
> function doIt() {
>   var objectModel = {};
> 
>   objectModel.pluggedIn1 = entityFromDatabase();
>   objectModel.pluggedIn2 = request.getParameter( "skin" );
> 
>   cocoon.sendPage( "view/myview.jx", objectModel );
> }
> 
> Other data that is not directly available from flow (like authentication 
> context can be accessed with input modules that are already available).
> 
And this is exactly my problem :)
With this approach you have to get all the data for each 
cocoon.sendPage() and store it somewhere. If you use a lot of flow this 
creates a maintenance nightmare. Of course you could provide your own 
sendPage() function that does all the work, but it's not a nice way of 
doing it.

So why not defining plugins for the object model somewhere and as soon 
as you use them in your template they are queried to provide information.

Carsten