From: Paul T. <pt...@gm...> - 2007-01-10 21:04:24
|
Hello, while using v.1.9 (and actually, i believe it's a bug in prior versions dating back to 1.5) i'm getting the stack trace below. I've attached a simple unit test that emulates this behaviour. Within my unit test, if you substitute "FAILING_CODE" with "PASSING_CODE" on line 23, the error doesn't occur. As near as i can tell, it's got something to do w/ the "bean" element that is directly beneath a bean element that contains the "&" symbol, as is the case w/ the "AIR" bean" if the attachment doesn't make it, i can simply inline the class, let me know thoughts? --- stack trace --- [junit] Testcase: testCompStringNodeSet(com.ximpleware.BinaryExprTest): Caused an ERROR [junit] Undefined behavior [junit] java.lang.RuntimeException: Undefined behavior [junit] at com.ximpleware.BinaryExpr.compStringNodeSet(BinaryExpr.java:364) [junit] at com.ximpleware.BinaryExpr.computeEQNE(BinaryExpr.java:234) [junit] at com.ximpleware.BinaryExpr.evalBoolean(BinaryExpr.java:113) [junit] at com.ximpleware.BinaryExpr.evalBoolean(BinaryExpr.java:111) [junit] at com.ximpleware.xpath.Predicate.eval(Predicate.java:41) [junit] at com.ximpleware.xpath.Step.evalPredicates(Step.java:118) [junit] at com.ximpleware.xpath.Step.eval(Step.java:108) [junit] at com.ximpleware.LocationPathExpr.process_child(LocationPathExpr.java:291) [junit] at com.ximpleware.LocationPathExpr.evalNodeSet(LocationPathExpr.java:1556) [junit] at com.ximpleware.UnionExpr.evalNodeSet(UnionExpr.java:111) [junit] at com.ximpleware.AutoPilot.evalXPath(AutoPilot.java:549) [junit] at com.ximpleware.BinaryExprTest.testCompStringNodeSet(BinaryExprTest.java:28) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) |