[erlang-patches] [PATCH] Teach xmerl_xpath to resolve context namespaces in more cases

Daniel White <>
Tue Oct 22 23:46:21 CEST 2013


Anthony,

I thought I might have a chance to look at items mentioned above, but
there are many other issues competing for my attention, and this
doesn't scratch any of my itches.  Will keep it in mind if I'm passing
this way again, however.


Fredrik,

Has the applicable team been able to look at this?  We're hoping it is
minimal enough to see it in an R16 release.  As it stands, we need to
have unnecessarily complicated hacks in our codebase in order to work
around this problem.


Cheers,


On Fri, Sep 13, 2013 at 8:49 PM, Anthony Ramine <> wrote:
> Btw 3 years ago when I implemented the namespace axis in xmerl_xpath I had to fix a few things beforehand, but I left a todo in that commit:
>
>         https://github.com/nox/otp/commit/770d6d9aaf4ebad18b1247911c5c3c23d688364a
>
> You may be interested in actually completing it.
>
> Regards,
>
> Le 13 sept. 2013 à 12:47, Anthony Ramine a écrit :
>
>> Well, good news, that's one less bug to fix :)
>>
>> Le 13 sept. 2013 à 12:45, Daniel White a écrit :
>>
>>> D'oh, that was a mistake when transcribing it from my console.  The
>>> example above should have read:
>>>
>>> <root xmlns:ns1="http://www.example.com/ns">
>>> <ns1:child ns1:attr="example" />
>>> </root>
>>>
>>> On Fri, Sep 13, 2013 at 7:57 PM, Anthony Ramine <> wrote:
>>>> Isn't that case wrong too?
>>>>
>>>> The <child/> element isn't in the http://www.example.com/ns namespace, right?
>>>>
>>>> Le 12 sept. 2013 à 18:52, Daniel White a écrit :
>>>>
>>>>>> [#xmlElement{}] = xmerl_xpath:string("/root/t:child", Doc,  [{namespace, [{"t", "http://www.example.com/ns"}]}]).
>>
>



-- 
Daniel White


More information about the erlang-patches mailing list