Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341862 - [xpath2] improvements to computation of typed value of xs:boolean nodes
Summary: [xpath2] improvements to computation of typed value of xs:boolean nodes
Status: RESOLVED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.xpath (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jesper Moller CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-05 01:21 EDT by Mukul Gandhi CLA
Modified: 2011-04-05 02:15 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mukul Gandhi CLA 2011-04-05 01:21:04 EDT 
Build Identifier: I20090313-0100

It seems that PsychoPath engine has following bug:

For such a node,

<X>1</X> (element 'X' is of type xs:boolean)

or <X att="1" />   (attribute 'att' is of type xs:boolean)

The following XPath expressions,

X = true()

OR

X/@att = true()

do not return right results. The current PsychoPath implementation returns false for these comparisons (there seems to be a bug in computing typed values of xs:boolean nodes, when the boolean lexical form "1" is present in an instance document).

I'll shortly be committing a fix for this, along with a test case.

Reproducible: Always
Comment 1 Mukul Gandhi CLA 2011-04-05 02:12:59 EDT 
i've committed the changes for this bug to HEAD and service branch, along with a commit for test case.

i'm marking this bug report as resolved.
Comment 2 Mukul Gandhi CLA 2011-04-05 02:15:17 EDT 
@Jesper: would you please integrate this change into the PsychoPath engine build.