Last week I've upgraded to GeoServer 2.5.2 from 2.3.4 and now the same
GetFeatureInfo request in my web site returns different results.
I am using "vendorParams" to filter layers and their attributes because I
dont want to show all fields of a table in a popup when they made a query.
Code:
With GeoServer 2.3.4 if I run a WMS getFeatureInfo request using code above
it works like it should - it shows only desired attributes which are
mentioned in "vendorParams" and only from 2 layers i have stated in
"layers".
But after upgrade to 2.5.2 it looks like that you cannot put attributes from
more than 1 layer because it returns
*"Internal error occurred PropertyDescriptor is null - did you request a
property that does not exist?"*
This would be a bug (well a regressions since the functionality does not work as before). Please report it to Jira
On the bright side GetFeatureInfo now respects your style settings, so you should get fewer false positives (where users click on something that is not actually displayed on the map they are looking at).
You may want to try an turning on the “old” implementation of GetFeatureInfo - just to see if it works better for your use case? See the docs for the command line option …
Last week I’ve upgraded to GeoServer 2.5.2 from 2.3.4 and now the same
GetFeatureInfo request in my web site returns different results.
I am using “vendorParams” to filter layers and their attributes because I
dont want to show all fields of a table in a popup when they made a query.
Code:
With GeoServer 2.3.4 if I run a WMS getFeatureInfo request using code above
it works like it should - it shows only desired attributes which are
mentioned in “vendorParams” and only from 2 layers i have stated in
“layers”.
But after upgrade to 2.5.2 it looks like that you cannot put attributes from
more than 1 layer because it returns
“Internal error occurred PropertyDescriptor is null - did you request a
property that does not exist?”