[BVAL-17] PathImpl keeps a null-named first node on unindexed property paths

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.1-incubating
• Fix Version/s: 0.1-incubating
• Component/s: jsr303
• Assignee: Roman Stumm
• Reporter: Carlos Vara
• Created: 06/Apr/10 02:10
• Updated: 06/Apr/12 22:29
• Resolved: 06/Apr/10 11:36

Description

PathImpl keeps a null-named first node on unindexed property paths, so the TCK tests detect the paths as invalid (the toString() produces the same output, but your PathImpl has an extra uneeded node there).