Escape literal attributes or allow AVTs?

[GoogleCodeExporter]

  Hi,

  The content of the x:param element in a call to a template or a
function explicitely escapes the { and } characters in attribute
values.  But why?  Why not declaring those literal elements as
being able to use AVT?

  I have a concrete example for that use.  I test a function that
takes an element in parameter, which contains a URI.  Those URIs
are all relative to a context on a server.  So I disable the
escaping in mode="test:create-xslt-generator" and used the
following test suite:

    <x:param name="base-uri" select="
        'http://www.expath.org/modules/http-client/test/request'"/>

    <t:scenario label="method-001">
       <t:call function="http:send-request">
          <t:param>
             <http:request href="{ $base-uri }/method-001"
                           method="options"/>
          </t:param>
    ...
    <!-- all subsequent test uses $base-uri -->

  I can provide a patch if this is more clear.

  What do you think?

  Regards,

-- 
Florent Georges
http://www.fgeorges.org/

Original issue reported on code.google.com by fgeorges on 6 Jan 2010 at 11:51

[GoogleCodeExporter]

Original comment by fgeorges on 25 Jan 2010 at 3:57

[GoogleCodeExporter]

Original comment by fgeorges on 25 Jan 2010 at 3:58

• Changed state: Accepted

[GoogleCodeExporter]

Fixed in r59.

Original comment by fgeorges on 26 Jan 2010 at 3:11

• Changed state: Fixed