Return-Path: 
 <cocoon-dev-return-30787-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 57408 invoked by uid 500); 29 Aug 2002 06:33:37 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 57397 invoked from network); 29 Aug 2002 06:33:36 -0000
Message-ID: <3D6DC00F.8090109@apache.org>
Date: Thu, 29 Aug 2002 08:32:47 +0200
From: Nicola Ken Barozzi <nicolaken@apache.org>
Reply-To: nicolaken@apache.org
Organization: Apache Software Foundation
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.0) Gecko/20020530
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: Cocoon - web environment coupling ?
References: <5.1.0.14.0.20020726145252.02d91368@10.10.1.1>
 <3D6BB33A.8020105@wyona.org> <3D6BD4DB.6050508@telio.be>
 <3D6C68FC.8020405@apache.org> <3D6C7908.7050401@telio.be>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


Pierre-Alexandre Losson wrote:
>> But since to set up Cocoon correctly you have to perform some steps 
>> that are not so easy to remember, very recently we have been thinking 
>> of creating a CocoonBean.java that would make the embedded usage in 
>> Cocoon easier.
>>
>> Basially what you need is this Bean; you can do it quite easily from 
>> Main.java, and it would be well accepted as a contribution to Cocoon 
>> :-D <hint hint - nudge nudge> ;-)
> 
> 
> I'll gladly investigate and implement this than. It'll clearly take me 
> less time than reimplementing what Cocoon already does very well ;)

Cool! :-D

>> If you have /any/ question regarding this, feel free to ask :-)
>>
> 
> My first question is the following : Cocoon has been built with the web 
> in mind i suppose (historically anyway), an in that aspect is built 
> around a 1 entry ---> 1 output paradigm.
> 
> Do you think it would be easy, or stated differently, what could be the 
> problematics of using Cocoon in a  n input ---> n output system (xml 
> pipeline architecture where a pipeline is not a 1->1)
> I suppose one can always transform a n->n transformation to multiple 1 
> to 1 of course but I just wanted to get your opinion on this.

There are no real problems about this, just that it hasn't been thought 
worthwhile IIRC.

Some committers have been against this (still IIRC), because it can 
possibly create confusion and unmannageability in a web publishing and 
webapp system.

But when you start using it as an embedded system, it becomes quite 
clear that it needs what XSLT gives, which means also n outputs.

So currently we have transformers that are able to write to the 
filesystem, so that you can have n outputs by inserting a Transformer 
for every n-1 output you need.

Now, the main point is: what is your use-case?
To understand the requirements it's always best to see real-life
examples and the exact points where you want the "fork" to begin.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


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