WFS Range Checking
------------------
Key: GEOS-3128
URL: http://jira.codehaus.org/browse/GEOS-3128
Project: GeoServer
Issue Type: Bug
Components: WFS
Affects Versions: 1.7.0
Environment: RHEL5
Reporter: Rettanah Hean
Assignee: Andrea Aime
This originally may have been an improvement issue. But I believe it is now a bug.
The history of the problem can be read here. http://www.nabble.com/GeoServer-WFS-range-checking--td22164066.html#a22164066
---
This is my latest discovery.
In the WFS module, in the GetFeature class, I have added debug to determine why I am not getting range checking exceptions.
I saw the specific cases in the code where range checking will occur. I've traced it through many of the if statements. But it seems to never get to the "visit" part in the code.
According to java docs, the accept method calls the visit method.
I put a print out before and after the accept call.
LOGGER.severe("BEFORE - accept(fvisitor, null)");
query.getFilter().accept(fvisitor, null);
LOGGER.severe("AFTER - accept(fvisitor, null)");
And I added a print out in the visit method and also a System.exit to ensure if I got to that point, I would know.
public Object visit(BBOX filter, Object data) {
LOGGER.severe("In VISIT METHOD - Now Exiting");
System.exit(0);
I get the printouts before and after the accept call, but no printouts from the visit method, nor the System.exit being performed.
As a simple test I tried to invoke the visit method manually with this snippet.
BBOX temp = null;
fvisitor.visit(temp,null);
After doing so I see the LOGGER.severe("In VISIT METHOD - Now Exiting"); printout, and then the System.exit is performed.
With this I do not believe range checking will ever occur in the code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira