Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: Tue, 1 Apr 2003 14:42:40 +0200 (CEST)
From: Stephan Michels <stephan@apache.org>
To: cocoon-dev@xml.apache.org
Subject: Re: CLI ideas (long)
In-Reply-To: <3E88A107.10784.6DF4D03@localhost>
Message-ID: <Pine.LNX.4.44.0304011437050.10161-100000@vern.chem.tu-berlin.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 31 Mar 2003, Upayavira wrote:

> A destination can be configured with a uri which identifies a
> ModfiableSource via its protocol. So instead of specifying a
> Destination, you specify a uri, and a sourceResolver identifies the
> ModifiableSource.
>
> Then all that remains is how to work out the actual uri of a
> particular output file, based upon the destination uri and the
> source uri.
>
> This can be done by specifying the source uri as a base
> and a path. The base is used to request a page, but is not appended
> to the output uri. When the source path should be inserted into the
> destination URI, the insertion point can be marked with a *, e.g.
>
> Ftp://ftp.host.com/htdocs/*
> zip://path/*@foo.zip
>
> If no * is present, and the destination URI ends with a /, the
> source path is appended to the output uri. If it does not end with a
> /, the output URI only is used, and the source path is discarded.
>
> The source uri is identified by combining the base & the path
> (separated by a file separator).

Do you know the Ant mapper
(http://ant.apache.org/manual/CoreTypes/mapper.html)?
Perhaps a similar facility can be used.

Stephan.