Yes, the primary key did the trick! Changing <OCQL>getId()</OCQL> into <OCQL>id()</OCQL> did not help, unfortunately.
Since I am retrieving the data from a PostGIS VIEW I now need to find a way to provide my chained data together with a primary key somehow. Not sure yet, how to do this. As far as I know, PostGIS doesn't support primary keys for views... Barbara v...@csiro wrote: > > The warning belows looks very familar, try setting a primary key or > > instead of idExpression -> getID maybe try idExpression -> id > > 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. > -- View this message in context: http://old.nabble.com/Error-duplicate-mappingName-in-2.0.2-%28but-works-fine-in-2.0.1%29-tp29570368p29612165.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
