W3C home > Mailing lists > Public > xproc-dev@w3.org > September 2011

Re: XML Calabash V0.9.34 released

From: Florent Georges <fgeorges@fgeorges.org>
Date: Sun, 4 Sep 2011 17:51:27 +0200
Message-ID: <CADyR_r3-H88BD9ZuVrRCBPPeb3+sSUVWSwoQYFX0dP4z28OycQ@mail.gmail.com>
To: Norman Walsh <ndw@nwalsh.com>
Cc: XProc Dev <xproc-dev@w3.org>
On 2 September 2011 21:39, Norman Walsh wrote:

  Hi,

> I introduced a couple of ugly bugs in 0.9.33. I think 0.9.34
> fixes those errors

  Congrats!

>     * Added Florent Georges' "configurers" patch. You can now
>       configure many aspects of the processor without modifying
>       the original sources.

  Thanks for that, and for your help during this!

>     * Made sure extension attributes are processed on all
>       elements; added hook for an XStep to get access to the
>       underlying Step for access to extension attributes on
>       descendants.

  Thanks.  That solves the problem for XSteps.  But most of the
steps are not XSteps, they are XProcSteps.  And in Calabash those
are even all extending DefaultStep.  So they _have_ an
XAtomicStep (which is an XStep), but they are not an XStep
themselves.

  I guess a simple and convenient solution is to add a method
like the following to DefaultStep, in order for extension code
manipulating steps to access the underlying XStep and thus the
extension attribtues:

    public XAtomicStep getUnderlyingStep() {
        return step;
    }

or preferably a more dedicated one like:

    public String getExtensionAttribute(QName name) {
        return step == null
            ? null
            : step.getExtensionAttribute(name);
    }

 Regards,

-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/
Received on Sunday, 4 September 2011 15:52:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 4 September 2011 15:52:24 GMT