KV-paired CRS gets truncated during equality test

[Piero Campalani]

For example, querying:

http://localhost:8080/def/equal?1=http://localhost:8080/def/crs?authority=EPSG&code=4326&version=0&2=http://localhost:8080/def/crs/EPSG/0/4326

will parse http://localhost:8080/def/crs?authority=EPSG instead of http://localhost:8080/def/crs?authority=EPSG&code=4326&version=0 as first CRS, so that exception is then thrown.

[Piero Campalani]

The problem resides in secore.util.StringUtil.addParam() method, which splits the KV-paired URL and adds the first two elements, which should be the key and the value actually, but in this case they key is the number (1) and the value is the whole KV-paired URL.

[Piero Campalani]

The same happens upon compounding.

http://localhost:8080/def/crs-compound?1=http://localhost:8080/def/crs?authority=EPSG&code=4326&version=0&2=http://localhost:8080/def/crs/EPSG/0/32633

[Piero Campalani]

Fixed in:

Author: Piero Campalani <cmppri@unife.it>
Date:   Fri Nov 9 15:23:19 2012 +0100

    Fix SECORE URLs parsing in case of compound/equal operations and KV-paired URLs (ticket #236).