Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361058 - QName._expanded and compare problem
Summary: QName._expanded and compare problem
Status: RESOLVED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.xpath (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jesper Moller CLA
QA Contact: Jesper Moller CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-15 10:31 EDT by Lukasz Wycisk CLA
Modified: 2011-12-14 17:52 EST (History)
0 users

See Also:


Attachments
patch (2.47 KB, text/plain)
2011-10-15 10:31 EDT, Lukasz Wycisk CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukasz Wycisk CLA 2011-10-15 10:31:36 EDT
Created attachment 205258 [details]
patch

3. QName._expanded which is boolean value saying if namespace was set (also null if default). When qname is created by function with empty first argument:

http://www.w3.org/TR/xquery-operators/#func-QName

then ._expanded is ‘true’(we think it’s correct)

but to compare it with qname from element will always return ‘false’ since Element.node_name() sets ._expanded to ‘false’ in case of null namespace (w3c.org representation of no-namespace situation is null).

Removing if statement in constructor (QName:45) seems to solve the problem and do not affected other tests. However we are not sure about correct ._expanded parameter state. What is Your opinion?
Comment 1 Jesper Moller CLA 2011-10-30 20:04:56 EDT
Patch looks good ... Reviewing and testing against HEAD and maintenance branches!
Comment 2 Jesper Moller CLA 2011-12-14 17:52:59 EST
Committed against HEAD and 3_3 maint.