Not sure why you would need to do this: if you've hardcoded the value, you
can hardcode it below. If you're not (I assume hardcoding was just
temporary) you should have access to the parameter from where it was set -
ie, using a matcher wildcard, or an action, etc. What was the final
functionality you were looking for?
Geoff
> >
> > I'm new at C2 but it seems to me from looking at
> sitemap.xsl that the
> > following (valid) sitemap snippet would result in some unintended
> code:
> >
> > <map:match patter="client.xml">
> > <map:parameter name="client" value="magnet" />
> >
> > <map:generate src="config/{client}.xml">
> > <map:parameter name="affiliate" value="onclave" />
> > </map:generate>
> > <map:transform src="config/output.xsl">
> > <map:parameter name="title" value="foo" />
> > </map:transform>
> > <map:serialize type="xml" />
> > </map:match>
> >
> > Every map:parameter generates a section of code that begins with:
> >
> > param = new Parameters();
> >
> > which would override outer parameter declarations.
>
> This is intended behavior. Parameter declared in the element (match,
> act, select, etc) is available only to this element, passed in the
> setup() call, and not to nested elements.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
