On Tue, Mar 1, 2022 at 3:37 AM Nick Wellnhofer wrote:
> On 28/02/2022 22:07, George Joseph wrote:
> > Actually "//*[name()='dm:device']" works as well so maybe that's what
> I'll do.
>
> This seems like the best work-around.
>
Yeah makes sense. I'll need to do some performance testing
On 28/02/2022 22:07, George Joseph wrote:
Actually "//*[name()='dm:device']" works as well so maybe that's what I'll do.
This seems like the best work-around.
Is there any reason why path parameters with namespaces haven't been
supported?
Would a pull request to add the
On Mon, Feb 28, 2022 at 2:01 PM George Joseph wrote:
>
>
> On Mon, Feb 28, 2022 at 1:04 PM Nick Wellnhofer
> wrote:
>
>> On 28/02/2022 20:54, George Joseph via xslt wrote:
>> > I think it works because xsltProcessUserParamInternal only sets
>> > xpctxt->namespaces = NULL but it doesn't clear
On Mon, Feb 28, 2022 at 1:04 PM Nick Wellnhofer wrote:
> On 28/02/2022 20:54, George Joseph via xslt wrote:
> > I think it works because xsltProcessUserParamInternal only sets
> > xpctxt->namespaces = NULL but it doesn't clear xpctxt->nsHash which is
> where
> > xmlXPathRegisterNs puts the
On 28/02/2022 20:54, George Joseph via xslt wrote:
I think it works because xsltProcessUserParamInternal only sets
xpctxt->namespaces = NULL but it doesn't clear xpctxt->nsHash which is where
xmlXPathRegisterNs puts the namespaces to be registered.
Right, the XPath engine uses both
On Mon, Feb 28, 2022 at 11:42 AM Nick Wellnhofer
wrote:
> On 28/02/2022 18:50, George Joseph via xslt wrote:
> > I've been having a heck of a time trying to pass a parameter
> > to xsltApplyStylesheet
> > that has namespaces in the xpath expression.
>
> This use case is simply not supported.
>
On 28/02/2022 18:50, George Joseph via xslt wrote:
I've been having a heck of a time trying to pass a parameter
to xsltApplyStylesheet
that has namespaces in the xpath expression.
This use case is simply not supported.
Finally I did find a workaround by calling xsltNewTransformContext() then
