Hello Sebb,
We are kind of bound to Xalan due to one feature:
- In javax api, evaluate does not return something similar to XObject,
ie if we don't know the return type then we cannot work generically like
today, for example:
- XPathAssertion expects either NodeList or Boolean , I don't see
with current javax API how to handle this unless we add more infos in GUI
or make some try/catch codes, maybe you have an idea.
Except for this, we could easily switch to Xpath standard API.
Regards
Philippe
On Fri, Nov 11, 2011 at 5:46 PM, <[email protected]> wrote:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=43294
>
> --- Comment #8 from Sebb <[email protected]> 2011-11-11 16:46:47 UTC ---
> I'd not realised that we used any Xalan-specific classes, but I see now
> that we
> use XPathAPI.
>
> We should perhaps work towards removing that dependency ... seems like it
> is
> not very efficient anyway.
>
> As a work-round, the simplest would be to allow the user to supply a
> properties
> file to provide the additional NS mappings.
>
> If we do go down this route, we should probably provide the additional
> mappings
> for use with all other XPath elements, e.g. the XPath function.
>
> --
> Configure bugmail:
> https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug.
>
--
Cordialement.
Philippe Mouawad.
