You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by "Stewart, Gary" <Ga...@luht.scot.nhs.uk> on 2005/11/09 16:41:17 UTC
Processing variables in the sitemap
Hi there,
A bit of a strange question here. I have a chunk in my sitemap that does something like:
<map:call resource="xforms-processing">
<map:parameter name="form-name" value="edit-form/{../id}" />
</map:call>
and then in the resource it basically calls cocoon:/{form-name} along with some other processing. The problem appears to be that {../id} is handed to the call which doesn't have id as part of it's scope. Is there some way to assess the variable before handing it over as a parameter so basically the resource would see "edit-form/1231".
Thanks,
Gary
*****************************************************************
The information contained in this message may be confidential or
legally privileged and is intended for the addressee only, If you
have received this message in error or there are any problems,
please notify the originator immediately. The unauthorised use,
disclosure, copying or alteration of this message is
strictly forbidden.
*****************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Processing variables in the sitemap
Posted by Sylvain Wallez <sy...@apache.org>.
Stewart, Gary wrote:
> Hi there,
>
> A bit of a strange question here. I have a chunk in my sitemap that does something like:
>
> <map:call resource="xforms-processing">
> <map:parameter name="form-name" value="edit-form/{../id}" />
> </map:call>
>
> and then in the resource it basically calls cocoon:/{form-name} along with some other processing. The problem appears to be that {../id} is handed to the call which doesn't have id as part of it's scope. Is there some way to assess the variable before handing it over as a parameter so basically the resource would see "edit-form/1231".
>
Well, it _should_ be resolved before actually calling the resource...
Double-checked the code...
Sylvain
--
Sylvain Wallez Anyware Technologies
http://people.apache.org/~sylvain http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org