Opened 10 years ago

Last modified 8 years ago

#124 new Issue

DOM4J XPath Issue

Reported by: Garth Braithwaite Owned by:
Priority: -Low Milestone: Unassigned
Component: View-App Version: Parking Lot
Severity: Major Effort Keywords: source code


Ran into a weird XPath problem with Dom4j doing the QM missing values work. For some reason a certain boundary or size was hit where either SAXON's or Jaxen's XPath would not find/hit an existing element. If converted to DOM then xpath worked as it should. Did lots of reading and didn't see any errors along this line.

Dom4j appears to be stalled or even a dead project. The last commit was over a year ago and it was an early alpha version. XOM appears to be the new ruler. DOM still remains king but it has other issues like making sure the XML is well formed and valid.

In any case it does leave a warm fuzzy about DOM4j and we probably need to refactor the XML code into a service with an interface so that this code can be localized and pluggable.

Change History (7)

comment:1 Changed 10 years ago by Garth Braithwaite

Owner: changed from Garth to Java Developer

comment:2 Changed 10 years ago by Garth Braithwaite

Milestone: Unassigned
Owner: changed from Java Developer to Unknown
Severity: Major
Version: 2.0Unknown

comment:3 Changed 9 years ago by Eleanor Howell

Keywords: source code added

comment:4 Changed 9 years ago by Garth Braithwaite

Milestone: Unassigned2.2 - Feature Set Definition

comment:5 Changed 9 years ago by Lois Haggard

Milestone: 2.2 - Feature Set DefinitionUnassigned

comment:6 Changed 9 years ago by Lois Haggard

Version: UnknownParking Lot

comment:7 Changed 8 years ago by Garth Braithwaite

Reared it's ugly head again. This time in the chart data from query module xpath. Did a search and it appears that this has been seen by others. Example:

This case we did have hyphens in the text so this might have applied:

Note: See TracTickets for help on using tickets.