Hi all,
Dwins and I again today ran into the indeterministic test problem in
which were both getting failures on trunk in different instances. And it
was again indeed a result of initializing the crs subsystem.
The failures on my part were resulting only in eclipse. I am still
unsure of the root cause but I found a fix by changing the following in
GeoServerAbstractTestSupport:
if
(Boolean.TRUE.equals(Hints.getSystemDefault(Hints.FORCE_LONGITUDE_FIRST_AXIS_ORDER)))
{
Hints.putSystemDefault(Hints.FORCE_AXIS_ORDER_HONORING, "http");
}
The change is to remove the guard around setting the
FORCE_AXIS_ORDER_HONORING hint, and always setting it. The result is
that all tests pass in eclipse.
So my questions are for Andrea (i think):
1. What is the rationale behind checking the default for the
FORCE_LONGITUDE_... hint before setting the FORCE_AXIS_... hint.
2. What are the repercussions of always setting the FORCE_AXIS_... hint?
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
