Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-users@xml.apache.org
To: cocoon-users@xml.apache.org
From: Andreas Hartmann <andreas@apache.org>
Subject: Re: using pipeline matched parameters in XSP
Date: Thu, 05 Jun 2003 22:26:20 +0200
Lines: 27
Message-ID: <bbo8sj$rnr$1@main.gmane.org>
References: <002201c32bcb$9ed524b0$b1e3119c@pablos>
 <bbntv8$qpl$1@main.gmane.org> <3EDF9C40.7060404@outerthought.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030529
In-Reply-To: <3EDF9C40.7060404@outerthought.org>
Sender: news <news@main.gmane.org>

Steven Noels wrote:

> On 5/06/2003 19:20 Andreas Hartmann wrote:
> 
>> I don't know if the util logicsheet works for this
>> kind of parameters, you could try it:
>>
>> <xsp-util:get-sitemap-parameter name="1" />
>>
>> But I wouldn't recommend this solution, even if it works.
> 
> Why that? Just curious - since I added that tag.

Of course the get-sitemap-parameter tag itself is very useful.
But when using the wildcard number as parameter key, the XSP
depends on the match pattern - I could imagine that is hard
to debug for someone who changes the pattern without being
familiar with the XSP.

OK, maybe it's just my personal perference that I usually want
to see from outside which parameters are used by a component.

Sorry if you felt offended - it was not against your tag but
against its misuse :)

Andreas


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