cannot recalculate Oracle layer coordinates bounds from the layer web admin interface when a custom SQL start session request is seton the datastore.
The custom SQL start session request is the following :
') from dual
This request works pretty well in any other situation with geoserver.(this is a great improvement for efficient data filtering according to user profile)
Problem occurs with both versions 2.2.5 and 2.2.4
Workaround : discard the custom SQL start session request, validate, recompute the layer geo bounds, validate, set the SQL start session request again, validate, OK