[JXPATH-151] null handling is inconsistent

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.3

Environment

windows oracle jvm 1.6_25

• Assignee: Unassigned
• Reporter: Johannes Stelzer
• Created: 07/Jun/11 10:08
• Updated: 08/Jun/11 18:20
• Resolved: 08/Jun/11 18:20

Description

Comparing a vaule to null using unequals (!=) yields false!

        Map<String, Integer> m = new HashMap<String, Integer>();
        m.put("a", 1);
        m.put("b", null);
        m.put("c", 1);
        JXPathContext c = JXPathContext.newContext(m);
        System.out.println(c.getValue("a != b") + " should be true");
        System.out.println(c.getValue("a != c") + " should be false");
        System.out.println(c.getValue("a = b") + " should be false");
        System.out.println(c.getValue("a = c") + " should be true");
        System.out.println(c.getValue("not(a = b)") + " should be true");
        System.out.println(c.getValue("not(a = c)") + " should be false");

Output using 1.3:
false should be true
false should be false
false should be false
true should be true
true should be true
false should be false

In 1.2 it works correctly!