Hi!
I tried to find the exact error-spot by trial & error (adding mappings one
by one). I found the following:
After having commented out the feature-chaining, there were still 2 errors
concerning name-spaces. Looks like GeoServer 2.0.1 was more forgiving? I
made the following changes to "protected_sites_1.xml" :
. . .
<Namespace>
<prefix>gn</prefix>
<uri>urn:x-inspire:specification:gmlas:GeographicalNames:3.0</uri>
</Namespace>
. . .
<!-- siteName -->
. . .
<ClientProperty>
<name>ps:nilReason</name>
<value>'unknown'</value>
</ClientProperty>
. . .
<!-- siteName:GeographicalName -->
. . .
<ClientProperty>
<name>gn</name>
<value>'urn:x-inspire:specification:gmlas:GeographicalNames:3.0'</value>
</ClientProperty>
Here is the new version of the mapping-file:
http://old.nabble.com/file/p29602675/protected_sites_1.xml
protected_sites_1.xml
After these changes, everything works fine WITHOUT feature-chaining. As soon
as I uncomment the feature-chaining, this time there is a new error-message
(IndexOutOfBoundsException). Here is part of the log:
WARN [data.complex] - This shouldn't have happened.There should be at least
1 features with id='species_in_ps.fid-4573364d_12ad1d0800a_-8000'.
WARN [data.complex] - No features found in next().This wouldn't have
happenned if hasNext() was called beforehand.
ERROR [geoserver.ows] -
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
....
"species_in_ps" is a view in a PostGIS-DB.
And here is an attachment of this part of the log containing the full
stack-trace:
http://old.nabble.com/file/p29602675/IndexOutOfBoundsException_2.0.2.log
IndexOutOfBoundsException_2.0.2.log
I then tried chaining a simple feature (generated with the GeoServer
Admin-GUI) instead of the non-feature-type ("speciesIncluded") - the result
was the same.
Not sure whether this is still a problem of duplicates? Could it be
something else? Maybe some hidden errors in my mapping-file(s) that
GeoServer 2.0.1 did not detect? Or were there changes concerning the
mapping-files from 2.0.1 --> 2.0.2 I'm not aware of?
Thank's in advance...
Barbara
Ben Caradoc-Davies-2 wrote:
>
> On 30/08/10 16:13, babsip wrote:
>> As I said before, everything worked fine with GeoServer 2.0.1, so what
>> changed in 2.0.2?
>
> I added a test to protect against the silent data corruption that
> results from having a multiply-defined feature type and app-schema
> feature chaining picking the first one it finds.
>
--
View this message in context:
http://old.nabble.com/Error-duplicate-mappingName-in-2.0.2-%28but-works-fine-in-2.0.1%29-tp29570368p29602675.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
