Return-Path: 
 <forrest-dev-return-6404-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 36955 invoked by uid 500); 25 Jul 2003 06:51:00 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 36944 invoked from network); 25 Jul 2003 06:51:00 -0000
Received: from dobit2.ugent.be (HELO dobit2.rug.ac.be) (157.193.42.8)
  by daedalus.apache.org with SMTP; 25 Jul 2003 06:51:00 -0000
Received: from allserv.UGent.be (allserv.ugent.be [157.193.40.42])
	by dobit2.rug.ac.be (8.12.8/8.12.8) with ESMTP id h6P6ovFY009262
	for <forrest-dev@xml.apache.org>; Fri, 25 Jul 2003 08:50:57 +0200 (MEST)
Received: from otsrv1.iic.rug.ac.be (otsrv1.iic.ugent.be [157.193.121.51])
	by allserv.UGent.be (8.12.8/8.12.8) with ESMTP id h6P6ovxR002817
	for <forrest-dev@xml.apache.org>; Fri, 25 Jul 2003 08:50:57 +0200 (MEST)
Received: from outerthought.org (host113 [192.168.123.113])
	by otsrv1.iic.rug.ac.be (8.11.6/8.11.6) with ESMTP id h6P6oux08594
	for <forrest-dev@xml.apache.org>; Fri, 25 Jul 2003 08:50:57 +0200
Message-ID: <3F20D34F.3040707@outerthought.org>
Date: Fri, 25 Jul 2003 08:50:55 +0200
From: Marc Portier <mpo@outerthought.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en, nl-be
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: New CLI, twice as fast :)
References: <20030720120743.GD3528@expresso.localdomain>
 <1058961326.3f1e77ae98062@secure.solidusdesign.com>
 <20030723122004.6087A73578@smtp.us2.messagingengine.com>
 <1058963033.3f1e7e59847e2@secure.solidusdesign.com>
 <20030723131546.0FBEA6ACE6@smtp.us2.messagingengine.com>
 <1058968367.3f1e932fd02d2@secure.solidusdesign.com>
 <20030724054155.E6141719FA@smtp.us2.messagingengine.com>
 <3F1FAE9E.5050501@che-che.com>
 <20030724131116.230EA74F0B@smtp.us2.messagingengine.com>
In-Reply-To: <20030724131116.230EA74F0B@smtp.us2.messagingengine.com>
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

Upayavira wrote:
> Cheche,
> 
> 
>>I thought that CLI was just to allow static version of websites.
> 
> 
> Not just to, it _IS_ to ;-)
> 
> 
>>Why do we want to overlap the funcionality that ant gives us?
> 
> 
> Because the CLI isn't always deployed in an Ant context. It can be used
> from the command line, or the CocoonBean can be integrated into your own
> Java applications.
> 
> Having said that, I think I should think more about the implications of
> using it in Ant - I've only been using Ant for a month or so (other than
> building Cocoon), and have been very impressed with its power.
> 

at the danger of completely missing the ball here...
(sine coming in late)

wouldn't it make the most sense to have a cocoon-cli ant task 
directly? (rather then hooking up through the java task?)

writing such custom ant task (and combined datatypes) should not 
be that difficult and I'ld like to assist. (I also think the 
cocoon bean could largely benefit)

am a bit short on time though and my main threshold here and now 
is understanding the full interface of the cocoon bean as is now

mainly how can it be instantiated/started and how does it get 
access to its xconf? (must be a file, or could it just be an 
InputStream?)



some rough ideas on the task

<cocoon-cli xconf-src=".." />

<cocoon-cli>
   <xconf>
     ... inline so we could go for ant-parameter-substitution
   </xconf>
</cocoon-cli>


in fact this last remark makes me think about quick hack using
<echo file="temp-location-to.xconf"><![CDATA[
<?xml version="1.0"?>
... whatever should be in the xconf ...
... wrapped around ant-parameters coming from the properties ...
]]></echo>


to generate the xconf based on ant-parameter-substitution and 
then still let it be followed by the classic <java> task


what do others think?

> Regards, Upayavira
> 

-marc=
-- 
Marc Portier                            http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at              http://radio.weblogs.com/0116284/
mpo@outerthought.org                              mpo@apache.org