Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 89488 invoked by uid 500); 8 Oct 2002 10:01:05 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 89473 invoked from network); 8 Oct 2002 10:01:03 -0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Proposal]: Advanced Value Substitution X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Tue, 8 Oct 2002 12:02:55 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Proposal]: Advanced Value Substitution Thread-Index: AcJupYvqIGNvARZZRbuw9G6wbo0B/gAC+cow From: "Amir Rosen" To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] > Sent: Tuesday, October 08, 2002 10:36 AM > To: Cocoon-Dev > Subject: [Proposal]: Advanced Value Substitution >=20 >=20 > Hi, >=20 > here is a simple proposal for an easier value substitution algorithm > in the sitemap. >=20 > Currently, if you nest actions and matchers you have to aware of > the paths to get your information: > > > > > > > This can get very complicated. When I first got contact with value > substitution more than two years ago, I thought I could write: > > And what happens if in the next version of AnythingAction it does use = '1' as a key ? how about: or some other simillar syntax that doesn't collide with input-modules.=20 Amir=20 >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org