#710: XSL Transformations done by XML Config Parser should have some information
available in template parameters
--------------------+-------------------------------------------------------
Reporter: david | Owner: david
Type: defect | Status: new
Priority: high | Milestone: 1.0
Component: config | Version:
Severity: major | Resolution:
Keywords: | Has_patch: 0
--------------------+-------------------------------------------------------
Old description:
> The name of the config file, for example, or the current environment and
> context names (see #708). Could also walk over all the {{{environment}}}
> and {{{context}}} attributes, evaluate the preg expressions, and set true
> and false flags on the nodes which an XSLT can then use (the WSDL XSL,
> for instance, transforms everything, not just the stuff from the
> respective {{{soap}}} context, due to lack of this information)
New description:
The name of the config file, for example, or the current environment and
context names (see #709). Could also walk over all the {{{environment}}}
and {{{context}}} attributes, evaluate the preg expressions, and set true
and false flags on the nodes which an XSLT can then use (the WSDL XSL, for
instance, transforms everything, not just the stuff from the respective
{{{soap}}} context, due to lack of this information)
--
Ticket URL: <http://trac.agavi.org/ticket/710#comment:1>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
