activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-2536) XPath selectors return false if xalan is not on the classpath
Date Sun, 03 Nov 2013 08:24:17 GMT

     [ https://issues.apache.org/jira/browse/AMQ-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved AMQ-2536.
------------------------------

    Resolution: Fixed

We are now using pre compiled expressions which is faster. That avoids using the cached xpath
api.

> XPath selectors return false if xalan is not on the classpath
> -------------------------------------------------------------
>
>                 Key: AMQ-2536
>                 URL: https://issues.apache.org/jira/browse/AMQ-2536
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Selector
>    Affects Versions: 5.3.0
>            Reporter: Roman Kalukiewicz
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 5.10.0
>
>
> When xalan.jar is not on the classpath, then {{org.apache.activemq.filter.XalanXPathEvaluator}}
in {{evaluate()}} method tries to load {{org.apache.xpath.CachedXPathAPI}}, throws {{NoClassDefFoundError}},
that is catched as {{Throwable}} and {{false}} is returned instead of an error.
> No clue is given to the client, that it lacks a jar on the classpath and the impression
is, that XPath selectors doesn't work and return false whatever the message is.
> I believe if we catch {{Exception}} instead of {{Throwable}}, then the problem would
be fixed.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message