GeoTools

DataStore parser doesnīt allow column with name "name"

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.1.RC0
  • Fix Version/s: 2.7.6
  • Component/s: xml
  • Labels:
    None

Description

My application throws an exception when I use a DataStore connected to a PostGIS
table with a column named "name". I am using Geoserver.
There is a bug that make it impossible to use a table with a column
named "name".

The problem happens only when Geoserver query answers have a column named "name".
Debugging the xml parser code, I have found in
org.geotools.xml.handlers.ComplexElementHandler that the class attribute "type"
contains the name of all table columns and some other objects.
But there are **TWO** instances with a name "name", when the table has such
a column. The second occurrence is related to the desired column, but the
first occurrence is something else. Maybe every type has automatically this
object with name "name", even when there is no column named "name".

The two occurrences of "name" should be treated differently.
I have fixed this bug by searching "type" backwards, from the end to the beginning, in
org.geotools.xml.handlers.xsi.ComplexTypeHandler.DefaultSequence.findChildElement.
But I donīt think it is an elegant solution - I even donīt know it is a solution
for all similar cases

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jody Garnett added a comment -
Apparently still unfixed - please use Fix Version to mark actual fixes.
Show
Jody Garnett added a comment - Apparently still unfixed - please use Fix Version to mark actual fixes.
Hide
Permalink
Michal Maniecki added a comment -
I was wondering if there is going to be a fix to this bug. The problem is more serious than just the "name" column.

There are 2 errors in the validation xml code, in org.geotools.xml.handlers.ComplexElementHandler.valid(Element, int)

- Schemas are case sensitive, and here elements are compared with equalsIgnoreCase( ). For GeoTools <gml:name> is the same as <gml:NAME> and that is not correct.

- Namespaces are not checked. One of the "name" elements is from a gml schema <gml:name>, the other one comes from my table <my_namespace:name>. For GeoTools they are the same.
Show
Michal Maniecki added a comment - I was wondering if there is going to be a fix to this bug. The problem is more serious than just the "name" column. There are 2 errors in the validation xml code, in org.geotools.xml.handlers.ComplexElementHandler.valid(Element, int) - Schemas are case sensitive, and here elements are compared with equalsIgnoreCase( ). For GeoTools <gml:name> is the same as <gml:NAME> and that is not correct. - Namespaces are not checked. One of the "name" elements is from a gml schema <gml:name>, the other one comes from my table <my_namespace:name>. For GeoTools they are the same.

People

  • Assignee:
    Unassigned
    Reporter:
    Vladimir Oliveira Di Iorio
Vote (1)
Watch (0)

Dates

  • Created:
    Updated: