[Geoserver-users] GeoServer filter parsing truncation

Hi all,

Sorry about the cross-list post but I’m not sure exactly where this problem lies.

(Ignore until you read the sentence below)

598072759 [FINE] org.vfny.geoserver.servlets.AbstractService - ------------XML POST START-----------
<?xml version="1.0" encoding="UTF-8"?>
<GetFeature xmlns=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/wfs"](http://www.opengis.net/wfs) xmlns:gml=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/gml"](http://www.opengis.net/gml) xmlns:ogc=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/ogc"](http://www.opengis.net/ogc) version="1.0.0" service="WFS" outputFormat="GML2"><Query typeName="topp:roadevent_pnt"><ogc:PropertyName>roadeventid</ogc:PropertyName>
<ogc:Filter><ogc:And><ogc:Intersects><ogc:PropertyName>the_geom</ogc:PropertyName>
<gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates decimal="." cs="," ts=" ">2224073.5294117643,5725938.522408964 2224073.5294117643,6077972.522408964 2740784.4985994394,6077972.522408964 2740784.4985994394,5725938.522408964 2224073.5294117643,5725938.522408964</gml:coordinates>
</gml:LinearRing>
</gml:outerBoundaryIs>
</gml:Polygon>
</ogc:Intersects>
<ogc:And><ogc:Not><ogc:PropertyIsGreaterThan><ogc:PropertyName>startdate</ogc:PropertyName>
<ogc:Literal>1.155523188718E12</ogc:Literal>
</ogc:PropertyIsGreaterThan>
</ogc:Not>
<ogc:Not><ogc:And><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</ogc:PropertyName>
<ogc:Literal>Closed</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsLessThan><ogc:PropertyName>enddate</ogc:PropertyName>
<ogc:Literal>1.154227188718E12</ogc:Literal>
</ogc:PropertyIsLessThan>
</ogc:And>
</ogc:Not>
<ogc:Not><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</ogc:PropertyName>
<ogc:Literal>Deleted</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Not>
<ogc:Or><ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Road Hazard</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Road Work</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Area Warning</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Compliment</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Complaint</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>**eventtype**</ogc:PropertyName>
<ogc:Literal>Damage Report</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Or>
</ogc:And>
</ogc:And>
</ogc:Filter>
</Query>
</GetFeature>

------------XML POST END-----------
598072774 [FINE] org.vfny.geoserver.wfs.requests.readers.GetFeatureXmlReader - just parsed: org.xml.sax.InputSource@anonymised.com
598072774 [INFO] org.vfny.geoserver.servlets.AbstractService - handling request:
Request: null
 output format:GML2
 max features:2147483647
 version:
 queries:
  Query []
   feature type: topp:roadevent_pnt
   filter: [[ the_geom intersects POLYGON ((2224073.5294117643 5725938.522408964, 2224073.5294117643 6077972.522408964, 2740784.4985994394 6077972.522408964, 2740784.4985994394 5725938.522408964, 2224073.5294117643 5725938.522408964)) ] AND [NOT [ startdate > 1.155523188718E12 ] AND NOT [[ eventstatus = Closed ] AND [ enddate < 1.154227188718E12 ]] AND NOT [ eventstatus = Deleted ] AND [[ eventtype = Road Hazard ] OR [ eventtype = Road Work ] OR [ eventtype = Area Warning ] OR [ eventtype = Compliment ] OR [ eventtype = Complaint ] OR [ **ttype** = Damage Report ]]]]
   [properties: roadeventid]

This is a WFS request sent to GeoServer 1.3.1 from uDig. Admittedly it is quite a big filter but I can’t really get away from that.

As you can see the last attribute filter in the XML post says “… or eventtype = Damage Report”. However, the parsed GeoTools filter below that says “… OR [ ttype = Damage Report ]”. This only happens when I have this number of attribute filters turned on, if I reduce the number by one everything works correctly.

The amount of truncation appears random as well. Sometimes the filter ends up as “OR [ e = Damage Report ]”.

Has anyone seen this before or know what can be done about it?

Thanks,
Mark

Hi Mark,

In eclipse when you run uDig you can set tracing on and make sure that tracing for the WFS plugin is checked and the request will be printed to the uDig console. That should give an indication of whether the problem is caused by the client or the server.

Jesse

I think it may actually have to do with the limitations of the SAX parser, but I thought we had a workaround for it. Like it'll only chunk a certain number of characters at once.

Gabriel, I feel like you may have had this bug and/or a fix for it? I know someone did. Maybe it didn't get ported over at some point?

Mark Presling wrote:

Hi all,

Sorry about the cross-list post but I'm not sure exactly where this problem lies.

(Ignore until you read the sentence below)

598072759 [FINE] org.vfny.geoserver.servlets.AbstractService - ------------XML POST START-----------
<?xml version="1.0" encoding="UTF-8"?>
<GetFeature xmlns=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot; xmlns:gml=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot; xmlns:ogc=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/ogc&quot; version="1.0.0" service="WFS" outputFormat="GML2"><Query typeName="topp:roadevent_pnt"><ogc:PropertyName>roadeventid</ogc:PropertyName>
<ogc:Filter><ogc:And><ogc:Intersects><ogc:PropertyName>the_geom</ogc:PropertyName>
<gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates decimal="." cs="," ts=" ">2224073.5294117643,5725938.522408964 2224073.5294117643,6077972.522408964 2740784.4985994394,6077972.522408964 2740784.4985994394,5725938.522408964 2224073.5294117643,5725938.522408964</gml:coordinates>
</gml:LinearRing>
</gml:outerBoundaryIs>
</gml:Polygon>
</ogc:Intersects>
<ogc:And><ogc:Not><ogc:PropertyIsGreaterThan><ogc:PropertyName>startdate</ogc:PropertyName>
<ogc:Literal>1.155523188718E12</ogc:Literal>
</ogc:PropertyIsGreaterThan>
</ogc:Not>
<ogc:Not><ogc:And><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</ogc:PropertyName>
<ogc:Literal>Closed</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsLessThan><ogc:PropertyName>enddate</ogc:PropertyName>
<ogc:Literal>1.154227188718E12</ogc:Literal>
</ogc:PropertyIsLessThan>
</ogc:And>
</ogc:Not>
<ogc:Not><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</ogc:PropertyName>
<ogc:Literal>Deleted</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Not>
<ogc:Or><ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Road Hazard</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Road Work</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Area Warning</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Compliment</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Complaint</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>*eventtype*</ogc:PropertyName>
<ogc:Literal>Damage Report</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Or>
</ogc:And>
</ogc:Filter>
</Query>
</GetFeature>

------------XML POST END-----------
598072774 [FINE] org.vfny.geoserver.wfs.requests.readers.GetFeatureXmlReader - just parsed: org.xml.sax.InputSource@anonymised.com
598072774 [INFO] org.vfny.geoserver.servlets.AbstractService - handling request:
Request: null
output format:GML2
max features:2147483647
version:
queries:
  Query
   feature type: topp:roadevent_pnt
   filter: [[ the_geom intersects POLYGON ((2224073.5294117643 5725938.522408964, 2224073.5294117643 6077972.522408964, 2740784.4985994394 6077972.522408964, 2740784.4985994394 5725938.522408964, 2224073.5294117643 5725938.522408964)) ] AND [NOT [ startdate > 1.155523188718E12 ] AND NOT [[ eventstatus = Closed ] AND [ enddate < 1.154227188718E12 ]] AND NOT [ eventstatus = Deleted ] AND [[ eventtype = Road Hazard ] OR [ eventtype = Road Work ] OR [ eventtype = Area Warning ] OR [ eventtype = Compliment ] OR [ eventtype = Complaint ] OR [ *ttype* = Damage Report ]]]]
   [properties: roadeventid]

This is a WFS request sent to GeoServer 1.3.1 from uDig. Admittedly it is quite a big filter but I can't really get away from that.

As you can see the last attribute filter in the XML post says "... or eventtype = Damage Report". However, the parsed GeoTools filter below that says "... OR [ ttype = Damage Report ]". This only happens when I have this number of attribute filters turned on, if I reduce the number by one everything works correctly.

The amount of truncation appears random as well. Sometimes the filter ends up as "OR [ e = Damage Report ]".

Has anyone seen this before or know what can be done about it?

Thanks,
Mark

!DSPAM:1003,44cd6f7d13131971556521!
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/&gt;, and is
believed to be clean.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

!DSPAM:1003,44cd6f7d13131971556521!

------------------------------------------------------------------------

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:1003,44cd6f7d13131971556521!

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org

indeed,
http://jira.codehaus.org/browse/GEOT-821

going to apply the patch to 2.2.x and trunk right now.

Gabriel

On Monday 31 July 2006 17:59, Chris Holmes wrote:

I think it may actually have to do with the limitations of the SAX
parser, but I thought we had a workaround for it. Like it'll only chunk
a certain number of characters at once.

Gabriel, I feel like you may have had this bug and/or a fix for it? I
know someone did. Maybe it didn't get ported over at some point?

Mark Presling wrote:
> Hi all,
>
> Sorry about the cross-list post but I'm not sure exactly where this
> problem lies.
>
> (Ignore until you read the sentence below)
>
> 598072759 [FINE] org.vfny.geoserver.servlets.AbstractService -
> ------------XML POST START----------- <?xml version="1.0"
> encoding="UTF-8"?>
> <GetFeature xmlns=*MailScanner has detected a possible fraud attempt from
> "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot;
> xmlns:gml=*MailScanner has detected a possible fraud attempt from
> "www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot;
> xmlns:ogc=*MailScanner has detected a possible fraud attempt from
> "www.opengis.net" claiming to be* "http://www.opengis.net/ogc&quot;
> version="1.0.0" service="WFS" outputFormat="GML2"><Query
> typeName="topp:roadevent_pnt"><ogc:PropertyName>roadeventid</ogc:Property
>Name>
> <ogc:Filter><ogc:And><ogc:Intersects><ogc:PropertyName>the_geom</ogc:Prop
>ertyName>
> <gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates
> decimal="." cs="," ts=" ">2224073.5294117643,5725938.522408964
> 2224073.5294117643,6077972.522408964 2740784.4985994394,6077972.522408964
> 2740784.4985994394,5725938.522408964
> 2224073.5294117643,5725938.522408964</gml:coordinates> </gml:LinearRing>
> </gml:outerBoundaryIs>
> </gml:Polygon>
> </ogc:Intersects>
> <ogc:And><ogc:Not><ogc:PropertyIsGreaterThan><ogc:PropertyName>startdate<
>/ogc:PropertyName> <ogc:Literal>1.155523188718E12</ogc:Literal>
> </ogc:PropertyIsGreaterThan>
> </ogc:Not>
> <ogc:Not><ogc:And><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</o
>gc:PropertyName> <ogc:Literal>Closed</ogc:Literal>
> </ogc:PropertyIsEqualTo>
> <ogc:PropertyIsLessThan><ogc:PropertyName>enddate</ogc:PropertyName>
> <ogc:Literal>1.154227188718E12</ogc:Literal>
> </ogc:PropertyIsLessThan>
> </ogc:And>
> </ogc:Not>
> <ogc:Not><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</ogc:Proper
>tyName> <ogc:Literal>Deleted</ogc:Literal>
> </ogc:PropertyIsEqualTo>
> </ogc:Not>
> <ogc:Or><ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyN
>ame> <ogc:Literal>Road Hazard</ogc:Literal>
> </ogc:PropertyIsEqualTo>
> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
> <ogc:Literal>Road Work</ogc:Literal>
> </ogc:PropertyIsEqualTo>
> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
> <ogc:Literal>Area Warning</ogc:Literal>
> </ogc:PropertyIsEqualTo>
> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
> <ogc:Literal>Compliment</ogc:Literal>
> </ogc:PropertyIsEqualTo>
> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
> <ogc:Literal>Complaint</ogc:Literal>
> </ogc:PropertyIsEqualTo>
> <ogc:PropertyIsEqualTo><ogc:PropertyName>*eventtype*</ogc:PropertyName>
> <ogc:Literal>Damage Report</ogc:Literal>
> </ogc:PropertyIsEqualTo>
> </ogc:Or>
> </ogc:And>
> </ogc:And>
> </ogc:Filter>
> </Query>
> </GetFeature>
>
>
> ------------XML POST END-----------
> 598072774 [FINE]
> org.vfny.geoserver.wfs.requests.readers.GetFeatureXmlReader - just
> parsed: org.xml.sax.InputSource@anonymised.com 598072774 [INFO]
> org.vfny.geoserver.servlets.AbstractService - handling request: Request:
> null
> output format:GML2
> max features:2147483647
> version:
> queries:
> Query
> feature type: topp:roadevent_pnt
> filter: [[ the_geom intersects POLYGON ((2224073.5294117643
> 5725938.522408964, 2224073.5294117643 6077972.522408964,
> 2740784.4985994394 6077972.522408964, 2740784.4985994394
> 5725938.522408964, 2224073.5294117643 5725938.522408964)) ] AND [NOT [
> startdate > 1.155523188718E12 ] AND NOT [[ eventstatus = Closed ] AND [
> enddate < 1.154227188718E12 ]] AND NOT [ eventstatus = Deleted ] AND [[
> eventtype = Road Hazard ] OR [ eventtype = Road Work ] OR [ eventtype =
> Area Warning ] OR [ eventtype = Compliment ] OR [ eventtype = Complaint ]
> OR [ *ttype* = Damage Report ]]]] [properties: roadeventid]
>
>
> This is a WFS request sent to GeoServer 1.3.1 from uDig. Admittedly it
> is quite a big filter but I can't really get away from that.
>
> As you can see the last attribute filter in the XML post says "... or
> eventtype = Damage Report". However, the parsed GeoTools filter below
> that says "... OR [ ttype = Damage Report ]". This only happens when I
> have this number of attribute filters turned on, if I reduce the number
> by one everything works correctly.
>
> The amount of truncation appears random as well. Sometimes the filter
> ends up as "OR [ e = Damage Report ]".
>
> Has anyone seen this before or know what can be done about it?
>
> Thanks,
> Mark
>
>
> !DSPAM:1003,44cd6f7d13131971556521!
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/&gt;, and is
> believed to be clean.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys -- and earn
> cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> !DSPAM:1003,44cd6f7d13131971556521!
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
> !DSPAM:1003,44cd6f7d13131971556521!

--
Gabriel Roldán (groldan@anonymised.com)
Axios Engineering (http://www.axios.es)
Tel. +34 944 41 63 84
Fax. +34 944 41 64 90

Chris, Mark:

I've applied the patch to 2.2.x and trunk, and added a test case to ensure
the characters(char, int, int) method contract is respected (not loosing
content).

don't know if Mark is building from source, in any case he would need a
gt-main jar to get it working.

Cheers,

Gabriel.

On Monday 31 July 2006 18:56, Gabriel Roldán wrote:

indeed,
http://jira.codehaus.org/browse/GEOT-821

going to apply the patch to 2.2.x and trunk right now.

Gabriel

On Monday 31 July 2006 17:59, Chris Holmes wrote:
> I think it may actually have to do with the limitations of the SAX
> parser, but I thought we had a workaround for it. Like it'll only chunk
> a certain number of characters at once.
>
> Gabriel, I feel like you may have had this bug and/or a fix for it? I
> know someone did. Maybe it didn't get ported over at some point?
>
> Mark Presling wrote:
> > Hi all,
> >
> > Sorry about the cross-list post but I'm not sure exactly where this
> > problem lies.
> >
> > (Ignore until you read the sentence below)
> >
> > 598072759 [FINE] org.vfny.geoserver.servlets.AbstractService -
> > ------------XML POST START----------- <?xml version="1.0"
> > encoding="UTF-8"?>
> > <GetFeature xmlns=*MailScanner has detected a possible fraud attempt
> > from "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot;
> > xmlns:gml=*MailScanner has detected a possible fraud attempt from
> > "www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot;
> > xmlns:ogc=*MailScanner has detected a possible fraud attempt from
> > "www.opengis.net" claiming to be* "http://www.opengis.net/ogc&quot;
> > version="1.0.0" service="WFS" outputFormat="GML2"><Query
> > typeName="topp:roadevent_pnt"><ogc:PropertyName>roadeventid</ogc:Proper
> >ty Name>
> > <ogc:Filter><ogc:And><ogc:Intersects><ogc:PropertyName>the_geom</ogc:Pr
> >op ertyName>
> > <gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates
> > decimal="." cs="," ts=" ">2224073.5294117643,5725938.522408964
> > 2224073.5294117643,6077972.522408964
> > 2740784.4985994394,6077972.522408964
> > 2740784.4985994394,5725938.522408964
> > 2224073.5294117643,5725938.522408964</gml:coordinates>
> > </gml:LinearRing> </gml:outerBoundaryIs>
> > </gml:Polygon>
> > </ogc:Intersects>
> > <ogc:And><ogc:Not><ogc:PropertyIsGreaterThan><ogc:PropertyName>startdat
> >e< /ogc:PropertyName> <ogc:Literal>1.155523188718E12</ogc:Literal>
> > </ogc:PropertyIsGreaterThan>
> > </ogc:Not>
> > <ogc:Not><ogc:And><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus<
> >/o gc:PropertyName> <ogc:Literal>Closed</ogc:Literal>
> > </ogc:PropertyIsEqualTo>
> > <ogc:PropertyIsLessThan><ogc:PropertyName>enddate</ogc:PropertyName>
> > <ogc:Literal>1.154227188718E12</ogc:Literal>
> > </ogc:PropertyIsLessThan>
> > </ogc:And>
> > </ogc:Not>
> > <ogc:Not><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</ogc:Prop
> >er tyName> <ogc:Literal>Deleted</ogc:Literal>
> > </ogc:PropertyIsEqualTo>
> > </ogc:Not>
> > <ogc:Or><ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:Propert
> >yN ame> <ogc:Literal>Road Hazard</ogc:Literal>
> > </ogc:PropertyIsEqualTo>
> > <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
> > <ogc:Literal>Road Work</ogc:Literal>
> > </ogc:PropertyIsEqualTo>
> > <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
> > <ogc:Literal>Area Warning</ogc:Literal>
> > </ogc:PropertyIsEqualTo>
> > <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
> > <ogc:Literal>Compliment</ogc:Literal>
> > </ogc:PropertyIsEqualTo>
> > <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
> > <ogc:Literal>Complaint</ogc:Literal>
> > </ogc:PropertyIsEqualTo>
> > <ogc:PropertyIsEqualTo><ogc:PropertyName>*eventtype*</ogc:PropertyName>
> > <ogc:Literal>Damage Report</ogc:Literal>
> > </ogc:PropertyIsEqualTo>
> > </ogc:Or>
> > </ogc:And>
> > </ogc:And>
> > </ogc:Filter>
> > </Query>
> > </GetFeature>
> >
> >
> > ------------XML POST END-----------
> > 598072774 [FINE]
> > org.vfny.geoserver.wfs.requests.readers.GetFeatureXmlReader - just
> > parsed: org.xml.sax.InputSource@anonymised.com 598072774 [INFO]
> > org.vfny.geoserver.servlets.AbstractService - handling request:
> > Request: null
> > output format:GML2
> > max features:2147483647
> > version:
> > queries:
> > Query
> > feature type: topp:roadevent_pnt
> > filter: [[ the_geom intersects POLYGON ((2224073.5294117643
> > 5725938.522408964, 2224073.5294117643 6077972.522408964,
> > 2740784.4985994394 6077972.522408964, 2740784.4985994394
> > 5725938.522408964, 2224073.5294117643 5725938.522408964)) ] AND [NOT [
> > startdate > 1.155523188718E12 ] AND NOT [[ eventstatus = Closed ] AND [
> > enddate < 1.154227188718E12 ]] AND NOT [ eventstatus = Deleted ] AND [[
> > eventtype = Road Hazard ] OR [ eventtype = Road Work ] OR [ eventtype =
> > Area Warning ] OR [ eventtype = Compliment ] OR [ eventtype = Complaint
> > ] OR [ *ttype* = Damage Report ]]]] [properties: roadeventid]
> >
> >
> > This is a WFS request sent to GeoServer 1.3.1 from uDig. Admittedly it
> > is quite a big filter but I can't really get away from that.
> >
> > As you can see the last attribute filter in the XML post says "... or
> > eventtype = Damage Report". However, the parsed GeoTools filter below
> > that says "... OR [ ttype = Damage Report ]". This only happens when I
> > have this number of attribute filters turned on, if I reduce the number
> > by one everything works correctly.
> >
> > The amount of truncation appears random as well. Sometimes the filter
> > ends up as "OR [ e = Damage Report ]".
> >
> > Has anyone seen this before or know what can be done about it?
> >
> > Thanks,
> > Mark
> >
> >
> > !DSPAM:1003,44cd6f7d13131971556521!
> > --
> > This message has been scanned for viruses and
> > dangerous content by *MailScanner* <http://www.mailscanner.info/&gt;, and
> > is believed to be clean.
> >
> > -----------------------------------------------------------------------
> >-- Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> > your opinions on IT & business topics through brief surveys -- and earn
> > cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD
> >EV
> >
> > !DSPAM:1003,44cd6f7d13131971556521!
> >
> >
> > -----------------------------------------------------------------------
> >-
> >
> > _______________________________________________
> > Geoserver-users mailing list
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
> >
> > !DSPAM:1003,44cd6f7d13131971556521!

--
Gabriel Roldán (groldan@anonymised.com)
Axios Engineering (http://www.axios.es)
Tel. +34 944 41 63 84
Fax. +34 944 41 64 90

Thankyou so much for getting that into 2.2.x! Now I have a question for the GeoServer people specifically...

I am currently using GeoServer 1.3.1. Therefore, I will need to upgrade. Here are my questions about this:
1. Is the upgrade path from 1.3.1 to 1.3.3 likely to cause me any grief on the WFS side? Things to consider may be inconsistent GeoTools libs between version 1.1.M7 of uDig and GeoServer.
2. Can I patch 1.3.3 with the latest 2.2.x jars to get this patch into 1.3.3?
3. Do I need to go to 1.3.3 or can I just patch 1.3.1 somehow?
4. If I can patch GeoServer with the new 2.2.x jars, where can I get them from?

We are trying to get the project to production immediately and this problem is holding us back, so if anyone has any suggestions on how we can achieve this in a safe manner in the shortest amount of time I would really appreciate it!

Thanks,
Mark

Gabriel Roldán wrote:

Chris, Mark:

I've applied the patch to 2.2.x and trunk, and added a test case to ensure
the characters(char, int, int) method contract is respected (not loosing content).

don't know if Mark is building from source, in any case he would need a gt-main jar to get it working.

Cheers,

Gabriel.

On Monday 31 July 2006 18:56, Gabriel Roldán wrote:
  

indeed,
http://jira.codehaus.org/browse/GEOT-821

going to apply the patch to 2.2.x and trunk right now.

Gabriel

On Monday 31 July 2006 17:59, Chris Holmes wrote:
    

I think it may actually have to do with the limitations of the SAX
parser, but I thought we had a workaround for it. Like it'll only chunk
a certain number of characters at once.

Gabriel, I feel like you may have had this bug and/or a fix for it? I
know someone did. Maybe it didn't get ported over at some point?

Mark Presling wrote:
      

Hi all,

Sorry about the cross-list post but I'm not sure exactly where this
problem lies.

(Ignore until you read the sentence below)

598072759 [FINE] org.vfny.geoserver.servlets.AbstractService -
------------XML POST START----------- <?xml version="1.0"
encoding="UTF-8"?>
<GetFeature xmlns=*MailScanner has detected a possible fraud attempt
from "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot;
xmlns:gml=*MailScanner has detected a possible fraud attempt from
"www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot;
xmlns:ogc=*MailScanner has detected a possible fraud attempt from
"www.opengis.net" claiming to be* "http://www.opengis.net/ogc&quot;
version="1.0.0" service="WFS" outputFormat="GML2"><Query
typeName="topp:roadevent_pnt"><ogc:PropertyName>roadeventid</ogc:Proper
ty Name>
<ogc:Filter><ogc:And><ogc:Intersects><ogc:PropertyName>the_geom</ogc:Pr
op ertyName>
<gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates
decimal="." cs="," ts=" ">2224073.5294117643,5725938.522408964
2224073.5294117643,6077972.522408964
2740784.4985994394,6077972.522408964
2740784.4985994394,5725938.522408964
2224073.5294117643,5725938.522408964</gml:coordinates>
</gml:LinearRing> </gml:outerBoundaryIs>
</gml:Polygon>
</ogc:Intersects>
<ogc:And><ogc:Not><ogc:PropertyIsGreaterThan><ogc:PropertyName>startdat
e< /ogc:PropertyName> <ogc:Literal>1.155523188718E12</ogc:Literal>
</ogc:PropertyIsGreaterThan>
</ogc:Not>
<ogc:Not><ogc:And><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus<
/o gc:PropertyName> <ogc:Literal>Closed</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsLessThan><ogc:PropertyName>enddate</ogc:PropertyName>
<ogc:Literal>1.154227188718E12</ogc:Literal>
</ogc:PropertyIsLessThan>
</ogc:And>
</ogc:Not>
<ogc:Not><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</ogc:Prop
er tyName> <ogc:Literal>Deleted</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Not>
<ogc:Or><ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:Propert
yN ame> <ogc:Literal>Road Hazard</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Road Work</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Area Warning</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Compliment</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Complaint</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>*eventtype*</ogc:PropertyName>
<ogc:Literal>Damage Report</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Or>
</ogc:And>
</ogc:Filter>
</Query>
</GetFeature>

------------XML POST END-----------
598072774 [FINE]
org.vfny.geoserver.wfs.requests.readers.GetFeatureXmlReader - just
parsed: org.xml.sax.InputSource@anonymised.com 598072774 [INFO]
org.vfny.geoserver.servlets.AbstractService - handling request:
Request: null
output format:GML2
max features:2147483647
version:
queries:
  Query
   feature type: topp:roadevent_pnt
   filter: [[ the_geom intersects POLYGON ((2224073.5294117643
5725938.522408964, 2224073.5294117643 6077972.522408964,
2740784.4985994394 6077972.522408964, 2740784.4985994394
5725938.522408964, 2224073.5294117643 5725938.522408964)) ] AND [NOT [
startdate > 1.155523188718E12 ] AND NOT [[ eventstatus = Closed ] AND [
enddate < 1.154227188718E12 ]] AND NOT [ eventstatus = Deleted ] AND [[
eventtype = Road Hazard ] OR [ eventtype = Road Work ] OR [ eventtype =
Area Warning ] OR [ eventtype = Compliment ] OR [ eventtype = Complaint
] OR [ *ttype* = Damage Report ]]]] [properties: roadeventid]

This is a WFS request sent to GeoServer 1.3.1 from uDig. Admittedly it
is quite a big filter but I can't really get away from that.

As you can see the last attribute filter in the XML post says "... or
eventtype = Damage Report". However, the parsed GeoTools filter below
that says "... OR [ ttype = Damage Report ]". This only happens when I
have this number of attribute filters turned on, if I reduce the number
by one everything works correctly.

The amount of truncation appears random as well. Sometimes the filter
ends up as "OR [ e = Damage Report ]".

Has anyone seen this before or know what can be done about it?

Thanks,
Mark

!DSPAM:1003,44cd6f7d13131971556521!
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/&gt;, and
is believed to be clean.

-----------------------------------------------------------------------
-- Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys -- and earn
cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD
EV

!DSPAM:1003,44cd6f7d13131971556521!

-----------------------------------------------------------------------
-

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:1003,44cd6f7d13131971556521!
        
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Mark Presling wrote:

Thankyou so much for getting that into 2.2.x! Now I have a question for the GeoServer people specifically...

I am currently using GeoServer 1.3.1. Therefore, I will need to upgrade. Here are my questions about this:
1. Is the upgrade path from 1.3.1 to 1.3.3 likely to cause me any grief on the WFS side? Things to consider may be inconsistent GeoTools libs between version 1.1.M7 of uDig and GeoServer.

Not very likely. The only real changes between 1.3.1 and 1.3.3 were kml improvements.

2. Can I patch 1.3.3 with the latest 2.2.x jars to get this patch into 1.3.3?

Yes, you should just need a new 2.2.x main jar. In geoserver this is called gt2-main.jar

3. Do I need to go to 1.3.3 or can I just patch 1.3.1 somehow?

You should be able to patch 1.3.1

4. If I can patch GeoServer with the new 2.2.x jars, where can I get them from?

I just did a build, you can grab it from: http://jira.codehaus.org/browse/GEOT-821

I only have maven1 working, so if there's any funkiness let me know, and we can get another build.

We are trying to get the project to production immediately and this problem is holding us back, so if anyone has any suggestions on how we can achieve this in a safe manner in the shortest amount of time I would really appreciate it!

Cool, this should hopefully get you going.

best regards,

Chris

Thanks,
Mark

Gabriel Roldán wrote:

Chris, Mark:

I've applied the patch to 2.2.x and trunk, and added a test case to ensure
the characters(char, int, int) method contract is respected (not loosing content).

don't know if Mark is building from source, in any case he would need a gt-main jar to get it working.

Cheers,

Gabriel.

On Monday 31 July 2006 18:56, Gabriel Roldán wrote:

indeed,
http://jira.codehaus.org/browse/GEOT-821

going to apply the patch to 2.2.x and trunk right now.

Gabriel

On Monday 31 July 2006 17:59, Chris Holmes wrote:
   

I think it may actually have to do with the limitations of the SAX
parser, but I thought we had a workaround for it. Like it'll only chunk
a certain number of characters at once.

Gabriel, I feel like you may have had this bug and/or a fix for it? I
know someone did. Maybe it didn't get ported over at some point?

Mark Presling wrote:
     

Hi all,

Sorry about the cross-list post but I'm not sure exactly where this
problem lies.

(Ignore until you read the sentence below)

598072759 [FINE] org.vfny.geoserver.servlets.AbstractService -
------------XML POST START----------- <?xml version="1.0"
encoding="UTF-8"?>
<GetFeature xmlns=*MailScanner has detected a possible fraud attempt
from "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot;
xmlns:gml=*MailScanner has detected a possible fraud attempt from
"www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot;
xmlns:ogc=*MailScanner has detected a possible fraud attempt from
"www.opengis.net" claiming to be* "http://www.opengis.net/ogc&quot;
version="1.0.0" service="WFS" outputFormat="GML2"><Query
typeName="topp:roadevent_pnt"><ogc:PropertyName>roadeventid</ogc:Proper

ty Name>
<ogc:Filter><ogc:And><ogc:Intersects><ogc:PropertyName>the_geom</ogc:Pr

op ertyName>
<gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates
decimal="." cs="," ts=" ">2224073.5294117643,5725938.522408964
2224073.5294117643,6077972.522408964
2740784.4985994394,6077972.522408964
2740784.4985994394,5725938.522408964
2224073.5294117643,5725938.522408964</gml:coordinates>
</gml:LinearRing> </gml:outerBoundaryIs>
</gml:Polygon>
</ogc:Intersects>
<ogc:And><ogc:Not><ogc:PropertyIsGreaterThan><ogc:PropertyName>startdat

e< /ogc:PropertyName> <ogc:Literal>1.155523188718E12</ogc:Literal>
</ogc:PropertyIsGreaterThan>
</ogc:Not>
<ogc:Not><ogc:And><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus<

/o gc:PropertyName> <ogc:Literal>Closed</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsLessThan><ogc:PropertyName>enddate</ogc:PropertyName>
<ogc:Literal>1.154227188718E12</ogc:Literal>
</ogc:PropertyIsLessThan>
</ogc:And>
</ogc:Not>
<ogc:Not><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</ogc:Prop

er tyName> <ogc:Literal>Deleted</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Not>
<ogc:Or><ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:Propert

yN ame> <ogc:Literal>Road Hazard</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Road Work</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Area Warning</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Compliment</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>
<ogc:Literal>Complaint</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>*eventtype*</ogc:PropertyName>

<ogc:Literal>Damage Report</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Or>
</ogc:And>
</ogc:Filter>
</Query>
</GetFeature>

------------XML POST END-----------
598072774 [FINE]
org.vfny.geoserver.wfs.requests.readers.GetFeatureXmlReader - just
parsed: org.xml.sax.InputSource@anonymised.com 598072774 [INFO]
org.vfny.geoserver.servlets.AbstractService - handling request:
Request: null
output format:GML2
max features:2147483647
version:
queries:
  Query
   feature type: topp:roadevent_pnt
   filter: [[ the_geom intersects POLYGON ((2224073.5294117643
5725938.522408964, 2224073.5294117643 6077972.522408964,
2740784.4985994394 6077972.522408964, 2740784.4985994394
5725938.522408964, 2224073.5294117643 5725938.522408964)) ] AND [NOT [
startdate > 1.155523188718E12 ] AND NOT [[ eventstatus = Closed ] AND [
enddate < 1.154227188718E12 ]] AND NOT [ eventstatus = Deleted ] AND [[
eventtype = Road Hazard ] OR [ eventtype = Road Work ] OR [ eventtype =
Area Warning ] OR [ eventtype = Compliment ] OR [ eventtype = Complaint
] OR [ *ttype* = Damage Report ]]]] [properties: roadeventid]

This is a WFS request sent to GeoServer 1.3.1 from uDig. Admittedly it
is quite a big filter but I can't really get away from that.

As you can see the last attribute filter in the XML post says "... or
eventtype = Damage Report". However, the parsed GeoTools filter below
that says "... OR [ ttype = Damage Report ]". This only happens when I
have this number of attribute filters turned on, if I reduce the number
by one everything works correctly.

The amount of truncation appears random as well. Sometimes the filter
ends up as "OR [ e = Damage Report ]".

Has anyone seen this before or know what can be done about it?

Thanks,
Mark

--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/&gt;, and
is believed to be clean.

-----------------------------------------------------------------------

-- Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys -- and earn
cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD

EV

!DSPAM:1003,44cd6f7d13131971556521!

-----------------------------------------------------------------------

-

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:1003,44cd6f7d13131971556521!
        
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

!DSPAM:1003,44ceadb6116861362196140!

------------------------------------------------------------------------

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:1003,44ceadb6116861362196140!

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org

Thanks Chris. It looks as though that has fixed my filter problem.

However, I have a curly one for you…

Now that I have patched GeoServer 1.3.1 with the new gt-main.jar I get different responses from the WFS when I use the following query:

<?xml version="1.0" encoding="UTF-8"?>
<GetFeature xmlns=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/wfs"](http://www.opengis.net/wfs) xmlns:gml=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/gml"](http://www.opengis.net/gml) xmlns:ogc=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/ogc"](http://www.opengis.net/ogc) version="1.0.0" service="WFS" outputFormat="GML2"><Query typeName="topp:nmcregion_poly"><ogc:PropertyName>regionid</ogc:PropertyName>
<ogc:Filter><ogc:Intersects><ogc:PropertyName>the_geom</ogc:PropertyName>
<gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates decimal="." cs="," ts=" ">2454899.90234375,5850231.933593749 2454899.90234375,5855725.097656249 2460393.06640625,5855725.097656249 2460393.06640625,5850231.933593749 2454899.90234375,5850231.933593749</gml:coordinates>
</gml:LinearRing>
</gml:outerBoundaryIs>
</gml:Polygon>
</ogc:Intersects>
</ogc:Filter>
</Query>
</GetFeature>

On the original one I get this response:

<wfs:FeatureCollection xmlns:wfs=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/wfs"](http://www.opengis.net/wfs) xmlns:topp=[**MailScanner has detected a possible fraud attempt from "www.openplans.org" claiming to be** "http://www.openplans.org/topp"](http://www.openplans.org/topp) xmlns:gml=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/gml"](http://www.opengis.net/gml) xmlns:xsi=[**MailScanner has detected a possible fraud attempt from "www.w3.org" claiming to be** "http://www.w3.org/2001/XMLSchema-instance"](http://www.w3.org/2001/XMLSchema-instance) xsi:schemaLocation=[**MailScanner has detected a possible fraud attempt from "www.openplans.org" claiming to be** "http://www.openplans.org/topp https://xxx/geoserver/wfs/DescribeFeatureType?typeName=topp:nmcregion_poly http://www.opengis.net/wfs https://xxx/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd"](http://www.openplans.org/topphttps://xxx/geoserver/wfs/DescribeFeatureType?typeName=topp:nmcregion_polyhttp://www.opengis.net/wfshttps://xxx/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd)>
  <gml:boundedBy>
    <gml:Box srsName=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/gml/srs/epsg.xml#27200"](http://www.opengis.net/gml/srs/epsg.xml#27200)>
      <gml:coordinates decimal="." cs="," ts=" ">2254760,5583607.2 2598181.9,5921952.9</gml:coordinates>
    </gml:Box>
  </gml:boundedBy>
  <gml:featureMember>
    <topp:nmcregion_poly fid="nmcregion_poly.13">
      <topp:regionid>14</topp:regionid>
    </topp:nmcregion_poly>
  </gml:featureMember>
</wfs:FeatureCollection>

Note that it has only returned the regionid attribute as requested in the Query. Now, the patched GeoServer returns:

<wfs:FeatureCollection xmlns:wfs=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/wfs"](http://www.opengis.net/wfs) xmlns:topp=[**MailScanner has detected a possible fraud attempt from "www.openplans.org" claiming to be** "http://www.openplans.org/topp"](http://www.openplans.org/topp) xmlns:gml=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/gml"](http://www.opengis.net/gml) xmlns:xsi=[**MailScanner has detected a possible fraud attempt from "www.w3.org" claiming to be** "http://www.w3.org/2001/XMLSchema-instance"](http://www.w3.org/2001/XMLSchema-instance) xsi:schemaLocation=[**MailScanner has detected a possible fraud attempt from "www.openplans.org" claiming to be** "http://www.openplans.org/topp http://192.168.201.9:8080/geoserver/wfs/DescribeFeatureType?typeName=topp:nmcregion_poly http://www.opengis.net/wfs http://192.168.201.9:8080/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd"](http://www.openplans.org/topphttp://192.168.201.9:8080/geoserver/wfs/DescribeFeatureType?typeName=topp:nmcregion_polyhttp://www.opengis.net/wfshttp://192.168.201.9:8080/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd)>
  <gml:boundedBy>
    <gml:Box srsName=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/gml/srs/epsg.xml#27200"](http://www.opengis.net/gml/srs/epsg.xml#27200)>
      <gml:coordinates decimal="." cs="," ts=" ">2254760.0000013,5583607.19995544 2598181.89999988,5921952.89999064</gml:coordinates>
    </gml:Box>
  </gml:boundedBy>
  <gml:featureMember>
    <topp:nmcregion_poly fid="nmcregion_poly.13">
      <topp:regionid>14</topp:regionid>
      <topp:regionname>Canterbury</topp:regionname>
      <topp:the_geom>
        <gml:MultiPolygon srsName=[**MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be** "http://www.opengis.net/gml/srs/epsg.xml#27200"](http://www.opengis.net/gml/srs/epsg.xml#27200)>
          <gml:polygonMember>
            <gml:Polygon>
              <gml:extrude>1</gml:extrude>
              <gml:altitudeMode>relativeToGround</gml:altitudeMode>
              <gml:outerBoundaryIs>
                <gml:LinearRing>
		........snip......

So does that mean that the head of GeoTools 2.2.x is no longer meeting the contract to only return the requested attributes or what? It may be something to check out for the next release of GeoServer.

It looks as though I am going to need to apply the patch for the filters to the revision that 1.3.1 was built on. Is anyone able to point me in the right direction on how to do this please? Will I have to set up a Maven build environment for GeoTools? I have never actually used Maven so that could be interesting. I would also need to know the tag/revision that 1.3.1 was built against.

Thanks,
Mark

Chris Holmes wrote:

Ugh. Very not fun.

Looking in to it, it actually looks like the bug fix for filters introduced the new bug.

Gabriel, any ideas for a quick fix/why it's working this way?

(I just completely confirmed it was the problem, did the latest build _with_ the fix, and got Mark's behavior, and did the latest build with the only change being that I merged in the old way of doing things, and it worked fine).

If Gabriel doesn't have an idea I'll dig in to it today. I imagine it's something with the characters not getting up to the property parsing in GeoServer.

best regards,

Chris

Mark Presling wrote:

Thanks Chris. It looks as though that has fixed my filter problem.

However, I have a curly one for you...

Now that I have patched GeoServer 1.3.1 with the new gt-main.jar I get different responses from the WFS when I use the following query:

<?xml version="1.0" encoding="UTF-8"?>
<GetFeature xmlns=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot; xmlns:gml=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot; xmlns:ogc=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/ogc&quot; version="1.0.0" service="WFS" outputFormat="GML2"><Query typeName="topp:nmcregion_poly"><ogc:PropertyName>regionid</ogc:PropertyName>
<ogc:Filter><ogc:Intersects><ogc:PropertyName>the_geom</ogc:PropertyName>
<gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates decimal="." cs="," ts=" ">2454899.90234375,5850231.933593749 2454899.90234375,5855725.097656249 2460393.06640625,5855725.097656249 2460393.06640625,5850231.933593749 2454899.90234375,5850231.933593749</gml:coordinates>
</gml:LinearRing>
</gml:outerBoundaryIs>
</gml:Polygon>
</ogc:Intersects>
</ogc:Filter>
</Query>
</GetFeature>

On the original one I get this response:

<wfs:FeatureCollection xmlns:wfs=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot; xmlns:topp=*MailScanner has detected a possible fraud attempt from "www.openplans.org" claiming to be* "http://www.openplans.org/topp&quot; xmlns:gml=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot; xmlns:xsi=*MailScanner has detected a possible fraud attempt from "www.w3.org" claiming to be* "http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation=*MailScanner has detected a possible fraud attempt from "www.openplans.org" claiming to be* "http://www.openplans.org/topp https://xxx/geoserver/wfs/DescribeFeatureType?typeName=topp:nmcregion_poly http://www.opengis.net/wfs https://xxx/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd&quot;&gt;
  <gml:boundedBy>
    <gml:Box srsName=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/gml/srs/epsg.xml#27200&quot;&gt;
      <gml:coordinates decimal="." cs="," ts=" ">2254760,5583607.2 2598181.9,5921952.9</gml:coordinates>
    </gml:Box>
  </gml:boundedBy>
  <gml:featureMember>
    <topp:nmcregion_poly fid="nmcregion_poly.13">
      <topp:regionid>14</topp:regionid>
    </topp:nmcregion_poly>
  </gml:featureMember>
</wfs:FeatureCollection>

Note that it has only returned the regionid attribute as requested in the Query. Now, the patched GeoServer returns:

<wfs:FeatureCollection xmlns:wfs=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot; xmlns:topp=*MailScanner has detected a possible fraud attempt from "www.openplans.org" claiming to be* "http://www.openplans.org/topp&quot; xmlns:gml=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot; xmlns:xsi=*MailScanner has detected a possible fraud attempt from "www.w3.org" claiming to be* "http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation=*MailScanner has detected a possible fraud attempt from "www.openplans.org" claiming to be* "http://www.openplans.org/topp http://192.168.201.9:8080/geoserver/wfs/DescribeFeatureType?typeName=topp:nmcregion_poly http://www.opengis.net/wfs http://192.168.201.9:8080/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd&quot;&gt;
  <gml:boundedBy>
    <gml:Box srsName=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/gml/srs/epsg.xml#27200&quot;&gt;
      <gml:coordinates decimal="." cs="," ts=" ">2254760.0000013,5583607.19995544 2598181.89999988,5921952.89999064</gml:coordinates>
    </gml:Box>
  </gml:boundedBy>
  <gml:featureMember>
    <topp:nmcregion_poly fid="nmcregion_poly.13">
      <topp:regionid>14</topp:regionid>
      <topp:regionname>Canterbury</topp:regionname>
      <topp:the_geom>
        <gml:MultiPolygon srsName=*MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/gml/srs/epsg.xml#27200&quot;&gt;
          <gml:polygonMember>
            <gml:Polygon>
              <gml:extrude>1</gml:extrude>
              <gml:altitudeMode>relativeToGround</gml:altitudeMode>
              <gml:outerBoundaryIs>
                <gml:LinearRing>
    ........snip......

So does that mean that the head of GeoTools 2.2.x is no longer meeting the contract to only return the requested attributes or what? It may be something to check out for the next release of GeoServer.

It looks as though I am going to need to apply the patch for the filters to the revision that 1.3.1 was built on. Is anyone able to point me in the right direction on how to do this please? Will I have to set up a Maven build environment for GeoTools? I have never actually used Maven so that could be interesting. I would also need to know the tag/revision that 1.3.1 was built against.

Thanks,
Mark

Chris Holmes wrote:

Mark Presling wrote:

Thankyou so much for getting that into 2.2.x! Now I have a question for the GeoServer people specifically...

I am currently using GeoServer 1.3.1. Therefore, I will need to upgrade. Here are my questions about this:
1. Is the upgrade path from 1.3.1 to 1.3.3 likely to cause me any grief on the WFS side? Things to consider may be inconsistent GeoTools libs between version 1.1.M7 of uDig and GeoServer.

Not very likely. The only real changes between 1.3.1 and 1.3.3 were kml improvements.

2. Can I patch 1.3.3 with the latest 2.2.x jars to get this patch into 1.3.3?

Yes, you should just need a new 2.2.x main jar. In geoserver this is called gt2-main.jar

3. Do I need to go to 1.3.3 or can I just patch 1.3.1 somehow?

You should be able to patch 1.3.1

4. If I can patch GeoServer with the new 2.2.x jars, where can I get them from?

I just did a build, you can grab it from: http://jira.codehaus.org/browse/GEOT-821

I only have maven1 working, so if there's any funkiness let me know, and we can get another build.

We are trying to get the project to production immediately and this problem is holding us back, so if anyone has any suggestions on how we can achieve this in a safe manner in the shortest amount of time I would really appreciate it!

Cool, this should hopefully get you going.

best regards,

Chris

Thanks,
Mark

Gabriel Roldán wrote:

Chris, Mark:

I've applied the patch to 2.2.x and trunk, and added a test case to ensure
the characters(char, int, int) method contract is respected (not loosing content).

don't know if Mark is building from source, in any case he would need a gt-main jar to get it working.

Cheers,

Gabriel.

On Monday 31 July 2006 18:56, Gabriel Roldán wrote:

indeed,
http://jira.codehaus.org/browse/GEOT-821

going to apply the patch to 2.2.x and trunk right now.

Gabriel

On Monday 31 July 2006 17:59, Chris Holmes wrote:
  

I think it may actually have to do with the limitations of the SAX
parser, but I thought we had a workaround for it. Like it'll only chunk
a certain number of characters at once.

Gabriel, I feel like you may have had this bug and/or a fix for it? I
know someone did. Maybe it didn't get ported over at some point?

Mark Presling wrote:
    

Hi all,

Sorry about the cross-list post but I'm not sure exactly where this
problem lies.

(Ignore until you read the sentence below)

598072759 [FINE] org.vfny.geoserver.servlets.AbstractService -
------------XML POST START----------- <?xml version="1.0"
encoding="UTF-8"?>
<GetFeature xmlns=*MailScanner has detected a possible fraud attempt
from "www.opengis.net" claiming to be* *MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot;
xmlns:gml=*MailScanner has detected a possible fraud attempt from
"www.opengis.net" claiming to be* *MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot;
xmlns:ogc=*MailScanner has detected a possible fraud attempt from
"www.opengis.net" claiming to be* *MailScanner has detected a possible fraud attempt from "www.opengis.net" claiming to be* "http://www.opengis.net/ogc&quot;
version="1.0.0" service="WFS" outputFormat="GML2"><Query
typeName="topp:roadevent_pnt"><ogc:PropertyName>roadeventid</ogc:Proper

ty Name>
<ogc:Filter><ogc:And><ogc:Intersects><ogc:PropertyName>the_geom</ogc:Pr

op ertyName>
<gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates
decimal="." cs="," ts=" ">2224073.5294117643,5725938.522408964
2224073.5294117643,6077972.522408964
2740784.4985994394,6077972.522408964
2740784.4985994394,5725938.522408964
2224073.5294117643,5725938.522408964</gml:coordinates>
</gml:LinearRing> </gml:outerBoundaryIs>
</gml:Polygon>
</ogc:Intersects>
<ogc:And><ogc:Not><ogc:PropertyIsGreaterThan><ogc:PropertyName>startdat

e< /ogc:PropertyName> <ogc:Literal>1.155523188718E12</ogc:Literal>
</ogc:PropertyIsGreaterThan>
</ogc:Not>
<ogc:Not><ogc:And><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus<

/o gc:PropertyName> <ogc:Literal>Closed</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsLessThan><ogc:PropertyName>enddate</ogc:PropertyName>
<ogc:Literal>1.154227188718E12</ogc:Literal>
</ogc:PropertyIsLessThan>
</ogc:And>
</ogc:Not>
<ogc:Not><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</ogc:Prop

er tyName> <ogc:Literal>Deleted</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Not>
<ogc:Or><ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:Propert

yN ame> <ogc:Literal>Road Hazard</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>

<ogc:Literal>Road Work</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>

<ogc:Literal>Area Warning</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>

<ogc:Literal>Compliment</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyName>

<ogc:Literal>Complaint</ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo><ogc:PropertyName>*eventtype*</ogc:PropertyName>

<ogc:Literal>Damage Report</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Or>
</ogc:And>
</ogc:Filter>
</Query>
</GetFeature>

------------XML POST END-----------
598072774 [FINE]
org.vfny.geoserver.wfs.requests.readers.GetFeatureXmlReader - just
parsed: org.xml.sax.InputSource@anonymised.com 598072774 [INFO]
org.vfny.geoserver.servlets.AbstractService - handling request:
Request: null
output format:GML2
max features:2147483647
version:
queries:
  Query
   feature type: topp:roadevent_pnt
   filter: [[ the_geom intersects POLYGON ((2224073.5294117643
5725938.522408964, 2224073.5294117643 6077972.522408964,
2740784.4985994394 6077972.522408964, 2740784.4985994394
5725938.522408964, 2224073.5294117643 5725938.522408964)) ] AND [NOT [
startdate > 1.155523188718E12 ] AND NOT [[ eventstatus = Closed ] AND [
enddate < 1.154227188718E12 ]] AND NOT [ eventstatus = Deleted ] AND [[
eventtype = Road Hazard ] OR [ eventtype = Road Work ] OR [ eventtype =
Area Warning ] OR [ eventtype = Compliment ] OR [ eventtype = Complaint
] OR [ *ttype* = Damage Report ]]]] [properties: roadeventid]

This is a WFS request sent to GeoServer 1.3.1 from uDig. Admittedly it
is quite a big filter but I can't really get away from that.

As you can see the last attribute filter in the XML post says "... or
eventtype = Damage Report". However, the parsed GeoTools filter below
that says "... OR [ ttype = Damage Report ]". This only happens when I
have this number of attribute filters turned on, if I reduce the number
by one everything works correctly.

The amount of truncation appears random as well. Sometimes the filter
ends up as "OR [ e = Damage Report ]".

Has anyone seen this before or know what can be done about it?

Thanks,
Mark

--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/&gt;, and
is believed to be clean.

-----------------------------------------------------------------------

-- Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys -- and earn
cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD

EV

-----------------------------------------------------------------------

-

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:1003,44cd6f7d13131971556521!
        
-------------------------------------------------------------------------

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

!DSPAM:1003,44ceadb6116861362196140!

------------------------------------------------------------------------

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:1003,44ceadb6116861362196140!

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
------------------------------------------------------------------------

_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
  

!DSPAM:1003,44d01312239116309890654!
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/&gt;, and is
believed to be clean.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

!DSPAM:1003,44d01312239116309890654!

------------------------------------------------------------------------

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:1003,44d01312239116309890654!

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org

I agree with Chris, the problem is on the SAX parser that produce strange result when parsing WFS requests. For example I have logged
the following (that can be useful for fixing the problem):
the log have the following pattern:

The WFS query used for reproduce the result, has a property named: BURIED_DEP. Note how. in the following
snipped log, the property name is truncated in: “BURIED_D” AND “EP”, becuase when the SAX parser
read the chunk, it read only 4096 characters, and do not see over that limit … :frowning: … and more, if you try to add
a new property, or remove a property, if you are lucky, you will have the right results only because the property’ names
are not across chunks of data.

CUSTOM LOG FOLLOWS: (format:: :: )

Query:addPropertyName: naoc:Pipeline_SpecialSections propertyName DESIGN_COD
FeatureHandler:characters: start=4008 length= 10 s = DESIGN_FAC
Query:addPropertyName: naoc:Pipeline_SpecialSections propertyName DESIGN_FAC
FeatureHandler:characters: start=4053 length= 10 s = HYDROSTATI
Query:addPropertyName: naoc:Pipeline_SpecialSections propertyName HYDROSTATI
FeatureHandler:characters: start=4098 length= 8 s = BURIED_D
Query:addPropertyName: naoc:Pipeline_SpecialSections propertyName BURIED_D
FeatureHandler:characters: start=0 length= 2 s = EP
Query:addPropertyName: naoc:Pipeline_SpecialSections propertyName EP
FeatureHandler:characters: start=37 length= 10 s = SUITABILIT
Query:addPropertyName: naoc:Pipeline_SpecialSections propertyName SUITABILIT
FeatureHandler:characters: start=82 length= 6 s = RATING
Query:addPropertyName: naoc:Pipeline_SpecialSections propertyName RATING
FeatureHandler:characters: start=123 length= 7 s = COATING
Query:addPropertyName: naoc:Pipeline_SpecialSections propertyName COATING
FeatureHandler:characters: start=165 length= 10 s = CONCRETE_C
Query:addPropertyName: naoc:Pipeline_SpecialSections propertyName CONCRETE_C

Some help on fixing it ??

10x in advance.
Giacomo

Chris Holmes ha scritto:

hmmm...
first sorry for catching up so late, I've lose the thread and just saw the
message today.

Unfortunately I have _no idea_ of what could be happening. I though the
problem was well isolated and the test case I've added would be enough for
catching, at least, the problem in cuestion.
Obviously was wrong, going to dig into it right now, hope to come back with an
answer asap.

Gabriel

On Wednesday 02 August 2006 17:25, Chris Holmes wrote:

Ugh. Very not fun.

Looking in to it, it actually looks like the bug fix for filters
introduced the new bug.

Gabriel, any ideas for a quick fix/why it's working this way?

(I just completely confirmed it was the problem, did the latest build
_with_ the fix, and got Mark's behavior, and did the latest build with
the only change being that I merged in the old way of doing things, and
it worked fine).

If Gabriel doesn't have an idea I'll dig in to it today. I imagine it's
something with the characters not getting up to the property parsing in
GeoServer.

best regards,

Chris

Mark Presling wrote:
> Thanks Chris. It looks as though that has fixed my filter problem.
>
> However, I have a curly one for you...
>
> Now that I have patched GeoServer 1.3.1 with the new gt-main.jar I get
> different responses from the WFS when I use the following query:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <GetFeature xmlns=*MailScanner has detected a possible fraud attempt from
> "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot;
> xmlns:gml=*MailScanner has detected a possible fraud attempt from
> "www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot;
> xmlns:ogc=*MailScanner has detected a possible fraud attempt from
> "www.opengis.net" claiming to be* "http://www.opengis.net/ogc&quot;
> version="1.0.0" service="WFS" outputFormat="GML2"><Query
> typeName="topp:nmcregion_poly"><ogc:PropertyName>regionid</ogc:PropertyNa
>me>
> <ogc:Filter><ogc:Intersects><ogc:PropertyName>the_geom</ogc:PropertyName>
> <gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates
> decimal="." cs="," ts=" ">2454899.90234375,5850231.933593749
> 2454899.90234375,5855725.097656249 2460393.06640625,5855725.097656249
> 2460393.06640625,5850231.933593749
> 2454899.90234375,5850231.933593749</gml:coordinates> </gml:LinearRing>
> </gml:outerBoundaryIs>
> </gml:Polygon>
> </ogc:Intersects>
> </ogc:Filter>
> </Query>
> </GetFeature>
>
> On the original one I get this response:
>
> <wfs:FeatureCollection xmlns:wfs=*MailScanner has detected a possible
> fraud attempt from "www.opengis.net" claiming to be*
> "http://www.opengis.net/wfs&quot; xmlns:topp=*MailScanner has detected a
> possible fraud attempt from "www.openplans.org" claiming to be*
> "http://www.openplans.org/topp&quot; xmlns:gml=*MailScanner has detected a
> possible fraud attempt from "www.opengis.net" claiming to be*
> "http://www.opengis.net/gml&quot; xmlns:xsi=*MailScanner has detected a
> possible fraud attempt from "www.w3.org" claiming to be*
> "http://www.w3.org/2001/XMLSchema-instance&quot;
> xsi:schemaLocation=*MailScanner has detected a possible fraud attempt
> from "www.openplans.org" claiming to be* "http://www.openplans.org/topp
> https://xxx/geoserver/wfs/DescribeFeatureType?typeName=topp:nmcregion_pol
>y http://www.opengis.net/wfs
> https://xxx/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd&quot;&gt; <gml:boundedBy>
> <gml:Box srsName=*MailScanner has detected a possible fraud attempt
> from "www.opengis.net" claiming to be*
> "http://www.opengis.net/gml/srs/epsg.xml#27200&quot;&gt; <gml:coordinates
> decimal="." cs="," ts=" ">2254760,5583607.2
> 2598181.9,5921952.9</gml:coordinates> </gml:Box>
> </gml:boundedBy>
> <gml:featureMember>
> <topp:nmcregion_poly fid="nmcregion_poly.13">
> <topp:regionid>14</topp:regionid>
> </topp:nmcregion_poly>
> </gml:featureMember>
> </wfs:FeatureCollection>
>
> Note that it has only returned the regionid attribute as requested in
> the Query. Now, the patched GeoServer returns:
>
> <wfs:FeatureCollection xmlns:wfs=*MailScanner has detected a possible
> fraud attempt from "www.opengis.net" claiming to be*
> "http://www.opengis.net/wfs&quot; xmlns:topp=*MailScanner has detected a
> possible fraud attempt from "www.openplans.org" claiming to be*
> "http://www.openplans.org/topp&quot; xmlns:gml=*MailScanner has detected a
> possible fraud attempt from "www.opengis.net" claiming to be*
> "http://www.opengis.net/gml&quot; xmlns:xsi=*MailScanner has detected a
> possible fraud attempt from "www.w3.org" claiming to be*
> "http://www.w3.org/2001/XMLSchema-instance&quot;
> xsi:schemaLocation=*MailScanner has detected a possible fraud attempt
> from "www.openplans.org" claiming to be* "http://www.openplans.org/topp
> http://192.168.201.9:8080/geoserver/wfs/DescribeFeatureType?typeName=topp
>:nmcregion_poly http://www.opengis.net/wfs
> http://192.168.201.9:8080/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd&quot;&gt;
> <gml:boundedBy>
> <gml:Box srsName=*MailScanner has detected a possible fraud attempt
> from "www.opengis.net" claiming to be*
> "http://www.opengis.net/gml/srs/epsg.xml#27200&quot;&gt; <gml:coordinates
> decimal="." cs="," ts=" ">2254760.0000013,5583607.19995544
> 2598181.89999988,5921952.89999064</gml:coordinates> </gml:Box>
> </gml:boundedBy>
> <gml:featureMember>
> <topp:nmcregion_poly fid="nmcregion_poly.13">
> <topp:regionid>14</topp:regionid>
> <topp:regionname>Canterbury</topp:regionname>
> <topp:the_geom>
> <gml:MultiPolygon srsName=*MailScanner has detected a possible
> fraud attempt from "www.opengis.net" claiming to be*
> "http://www.opengis.net/gml/srs/epsg.xml#27200&quot;&gt; <gml:polygonMember>
> <gml:Polygon>
> <gml:extrude>1</gml:extrude>
> <gml:altitudeMode>relativeToGround</gml:altitudeMode>
> <gml:outerBoundaryIs>
> <gml:LinearRing>
> ........snip......
>
> So does that mean that the head of GeoTools 2.2.x is no longer meeting
> the contract to only return the requested attributes or what? It may be
> something to check out for the next release of GeoServer.
>
> It looks as though I am going to need to apply the patch for the filters
> to the revision that 1.3.1 was built on. Is anyone able to point me in
> the right direction on how to do this please? Will I have to set up a
> Maven build environment for GeoTools? I have never actually used Maven
> so that could be interesting. I would also need to know the tag/revision
> that 1.3.1 was built against.
>
> Thanks,
> Mark
>
> Chris Holmes wrote:
>> Mark Presling wrote:
>>> Thankyou so much for getting that into 2.2.x! Now I have a question
>>> for the GeoServer people specifically...
>>>
>>> I am currently using GeoServer 1.3.1. Therefore, I will need to
>>> upgrade. Here are my questions about this:
>>> 1. Is the upgrade path from 1.3.1 to 1.3.3 likely to cause me any
>>> grief on the WFS side? Things to consider may be inconsistent
>>> GeoTools libs between version 1.1.M7 of uDig and GeoServer.
>>
>> Not very likely. The only real changes between 1.3.1 and 1.3.3 were
>> kml improvements.
>>
>>> 2. Can I patch 1.3.3 with the latest 2.2.x jars to get this patch
>>> into 1.3.3?
>>
>> Yes, you should just need a new 2.2.x main jar. In geoserver this is
>> called gt2-main.jar
>>
>>> 3. Do I need to go to 1.3.3 or can I just patch 1.3.1 somehow?
>>
>> You should be able to patch 1.3.1
>>
>>> 4. If I can patch GeoServer with the new 2.2.x jars, where can I get
>>> them from?
>>
>> I just did a build, you can grab it from:
>> http://jira.codehaus.org/browse/GEOT-821
>>
>> I only have maven1 working, so if there's any funkiness let me know,
>> and we can get another build.
>>
>>> We are trying to get the project to production immediately and this
>>> problem is holding us back, so if anyone has any suggestions on how
>>> we can achieve this in a safe manner in the shortest amount of time I
>>> would really appreciate it!
>>
>> Cool, this should hopefully get you going.
>>
>> best regards,
>>
>> Chris
>>
>>> Thanks,
>>> Mark
>>>
>>> Gabriel Roldán wrote:
>>>> Chris, Mark:
>>>>
>>>> I've applied the patch to 2.2.x and trunk, and added a test case to
>>>> ensure
>>>> the characters(char, int, int) method contract is respected (not
>>>> loosing content).
>>>>
>>>> don't know if Mark is building from source, in any case he would
>>>> need a gt-main jar to get it working.
>>>>
>>>> Cheers,
>>>>
>>>> Gabriel.
>>>>
>>>> On Monday 31 July 2006 18:56, Gabriel Roldán wrote:
>>>>> indeed,
>>>>> http://jira.codehaus.org/browse/GEOT-821
>>>>>
>>>>> going to apply the patch to 2.2.x and trunk right now.
>>>>>
>>>>> Gabriel
>>>>>
>>>>> On Monday 31 July 2006 17:59, Chris Holmes wrote:
>>>>>> I think it may actually have to do with the limitations of the SAX
>>>>>> parser, but I thought we had a workaround for it. Like it'll only
>>>>>> chunk
>>>>>> a certain number of characters at once.
>>>>>>
>>>>>> Gabriel, I feel like you may have had this bug and/or a fix for
>>>>>> it? I
>>>>>> know someone did. Maybe it didn't get ported over at some point?
>>>>>>
>>>>>> Mark Presling wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Sorry about the cross-list post but I'm not sure exactly where this
>>>>>>> problem lies.
>>>>>>>
>>>>>>> (Ignore until you read the sentence below)
>>>>>>>
>>>>>>> 598072759 [FINE] org.vfny.geoserver.servlets.AbstractService -
>>>>>>> ------------XML POST START----------- <?xml version="1.0"
>>>>>>> encoding="UTF-8"?>
>>>>>>> <GetFeature xmlns=*MailScanner has detected a possible fraud
>>>>>>> attempt from "www.opengis.net" claiming to be* *MailScanner has
>>>>>>> detected a possible fraud attempt from "www.opengis.net" claiming
>>>>>>> to be* "http://www.opengis.net/wfs&quot;
>>>>>>> xmlns:gml=*MailScanner has detected a possible fraud attempt from
>>>>>>> "www.opengis.net" claiming to be* *MailScanner has detected a
>>>>>>> possible fraud attempt from "www.opengis.net" claiming to be*
>>>>>>> "http://www.opengis.net/gml&quot;
>>>>>>> xmlns:ogc=*MailScanner has detected a possible fraud attempt from
>>>>>>> "www.opengis.net" claiming to be* *MailScanner has detected a
>>>>>>> possible fraud attempt from "www.opengis.net" claiming to be*
>>>>>>> "http://www.opengis.net/ogc&quot;
>>>>>>> version="1.0.0" service="WFS" outputFormat="GML2"><Query
>>>>>>> typeName="topp:roadevent_pnt"><ogc:PropertyName>roadeventid</ogc:Pr
>>>>>>>oper
>>>>>>>
>>>>>>> ty Name>
>>>>>>> <ogc:Filter><ogc:And><ogc:Intersects><ogc:PropertyName>the_geom</og
>>>>>>>c:Pr
>>>>>>>
>>>>>>> op ertyName>
>>>>>>> <gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates
>>>>>>> decimal="." cs="," ts=" ">2224073.5294117643,5725938.522408964
>>>>>>> 2224073.5294117643,6077972.522408964
>>>>>>> 2740784.4985994394,6077972.522408964
>>>>>>> 2740784.4985994394,5725938.522408964
>>>>>>> 2224073.5294117643,5725938.522408964</gml:coordinates>
>>>>>>> </gml:LinearRing> </gml:outerBoundaryIs>
>>>>>>> </gml:Polygon>
>>>>>>> </ogc:Intersects>
>>>>>>> <ogc:And><ogc:Not><ogc:PropertyIsGreaterThan><ogc:PropertyName>star
>>>>>>>tdat
>>>>>>>
>>>>>>> e< /ogc:PropertyName> <ogc:Literal>1.155523188718E12</ogc:Literal>
>>>>>>> </ogc:PropertyIsGreaterThan>
>>>>>>> </ogc:Not>
>>>>>>> <ogc:Not><ogc:And><ogc:PropertyIsEqualTo><ogc:PropertyName>eventsta
>>>>>>>tus<
>>>>>>>
>>>>>>> /o gc:PropertyName> <ogc:Literal>Closed</ogc:Literal>
>>>>>>> </ogc:PropertyIsEqualTo>
>>>>>>> <ogc:PropertyIsLessThan><ogc:PropertyName>enddate</ogc:PropertyName
>>>>>>>> <ogc:Literal>1.154227188718E12</ogc:Literal>
>>>>>>> </ogc:PropertyIsLessThan>
>>>>>>> </ogc:And>
>>>>>>> </ogc:Not>
>>>>>>> <ogc:Not><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</ogc:
>>>>>>>Prop
>>>>>>>
>>>>>>> er tyName> <ogc:Literal>Deleted</ogc:Literal>
>>>>>>> </ogc:PropertyIsEqualTo>
>>>>>>> </ogc:Not>
>>>>>>> <ogc:Or><ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:Pro
>>>>>>>pert
>>>>>>>
>>>>>>> yN ame> <ogc:Literal>Road Hazard</ogc:Literal>
>>>>>>> </ogc:PropertyIsEqualTo>
>>>>>>> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyNam
>>>>>>>e>
>>>>>>>
>>>>>>> <ogc:Literal>Road Work</ogc:Literal>
>>>>>>> </ogc:PropertyIsEqualTo>
>>>>>>> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyNam
>>>>>>>e>
>>>>>>>
>>>>>>> <ogc:Literal>Area Warning</ogc:Literal>
>>>>>>> </ogc:PropertyIsEqualTo>
>>>>>>> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyNam
>>>>>>>e>
>>>>>>>
>>>>>>> <ogc:Literal>Compliment</ogc:Literal>
>>>>>>> </ogc:PropertyIsEqualTo>
>>>>>>> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyNam
>>>>>>>e>
>>>>>>>
>>>>>>> <ogc:Literal>Complaint</ogc:Literal>
>>>>>>> </ogc:PropertyIsEqualTo>
>>>>>>> <ogc:PropertyIsEqualTo><ogc:PropertyName>*eventtype*</ogc:PropertyN
>>>>>>>ame>
>>>>>>>
>>>>>>> <ogc:Literal>Damage Report</ogc:Literal>
>>>>>>> </ogc:PropertyIsEqualTo>
>>>>>>> </ogc:Or>
>>>>>>> </ogc:And>
>>>>>>> </ogc:And>
>>>>>>> </ogc:Filter>
>>>>>>> </Query>
>>>>>>> </GetFeature>
>>>>>>>
>>>>>>>
>>>>>>> ------------XML POST END-----------
>>>>>>> 598072774 [FINE]
>>>>>>> org.vfny.geoserver.wfs.requests.readers.GetFeatureXmlReader - just
>>>>>>> parsed: org.xml.sax.InputSource@anonymised.com 598072774 [INFO]
>>>>>>> org.vfny.geoserver.servlets.AbstractService - handling request:
>>>>>>> Request: null
>>>>>>> output format:GML2
>>>>>>> max features:2147483647
>>>>>>> version:
>>>>>>> queries:
>>>>>>> Query
>>>>>>> feature type: topp:roadevent_pnt
>>>>>>> filter: [[ the_geom intersects POLYGON ((2224073.5294117643
>>>>>>> 5725938.522408964, 2224073.5294117643 6077972.522408964,
>>>>>>> 2740784.4985994394 6077972.522408964, 2740784.4985994394
>>>>>>> 5725938.522408964, 2224073.5294117643 5725938.522408964)) ] AND
>>>>>>> [NOT [
>>>>>>> startdate > 1.155523188718E12 ] AND NOT [[ eventstatus = Closed ]
>>>>>>> AND [
>>>>>>> enddate < 1.154227188718E12 ]] AND NOT [ eventstatus = Deleted ]
>>>>>>> AND [[
>>>>>>> eventtype = Road Hazard ] OR [ eventtype = Road Work ] OR [
>>>>>>> eventtype =
>>>>>>> Area Warning ] OR [ eventtype = Compliment ] OR [ eventtype =
>>>>>>> Complaint
>>>>>>> ] OR [ *ttype* = Damage Report ]]]] [properties: roadeventid]
>>>>>>>
>>>>>>>
>>>>>>> This is a WFS request sent to GeoServer 1.3.1 from uDig.
>>>>>>> Admittedly it
>>>>>>> is quite a big filter but I can't really get away from that.
>>>>>>>
>>>>>>> As you can see the last attribute filter in the XML post says
>>>>>>> "... or
>>>>>>> eventtype = Damage Report". However, the parsed GeoTools filter
>>>>>>> below
>>>>>>> that says "... OR [ ttype = Damage Report ]". This only happens
>>>>>>> when I
>>>>>>> have this number of attribute filters turned on, if I reduce the
>>>>>>> number
>>>>>>> by one everything works correctly.
>>>>>>>
>>>>>>> The amount of truncation appears random as well. Sometimes the
>>>>>>> filter
>>>>>>> ends up as "OR [ e = Damage Report ]".
>>>>>>>
>>>>>>> Has anyone seen this before or know what can be done about it?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Mark
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> This message has been scanned for viruses and
>>>>>>> dangerous content by *MailScanner*
>>>>>>> <http://www.mailscanner.info/&gt;, and
>>>>>>> is believed to be clean.
>>>>>>>
>>>>>>> -------------------------------------------------------------------
>>>>>>>----
>>>>>>>
>>>>>>> -- Take Surveys. Earn Cash. Influence the Future of IT
>>>>>>> Join SourceForge.net's Techsay panel and you'll get the chance to
>>>>>>> share
>>>>>>> your opinions on IT & business topics through brief surveys --
>>>>>>> and earn
>>>>>>> cash
>>>>>>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=
>>>>>>>DEVD
>>>>>>>
>>>>>>> EV
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -------------------------------------------------------------------
>>>>>>>----
>>>>>>>
>>>>>>> -
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Geoserver-users mailing list
>>>>>>> Geoserver-users@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>>>>>
>>>>>>>
>>>>>>> !DSPAM:1003,44cd6f7d13131971556521!
>>>
>>> -----------------------------------------------------------------------
>>>--
>>>
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the chance to
>>> share your
>>> opinions on IT & business topics through brief surveys -- and earn cash
>>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD
>>>EV
>>>
>>>
>>> !DSPAM:1003,44ceadb6116861362196140!
>>>
>>>
>>> -----------------------------------------------------------------------
>>>-
>>>
>>> _______________________________________________
>>> Geoserver-users mailing list
>>> Geoserver-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>
>>>
>>> !DSPAM:1003,44ceadb6116861362196140!
>>
>> ------------------------------------------------------------------------
>>- Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your opinions on IT & business topics through brief surveys -- and earn
>> cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
>>V
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Geotools-devel mailing list
>> Geotools-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
> !DSPAM:1003,44d01312239116309890654!
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/&gt;, and is
> believed to be clean.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys -- and earn
> cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> !DSPAM:1003,44d01312239116309890654!
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
> !DSPAM:1003,44d01312239116309890654!

--
Gabriel Roldán (groldan@anonymised.com)
Axios Engineering (http://www.axios.es)
Tel. +34 944 41 63 84
Fax. +34 944 41 64 90

Mark,
it is fixed now.
I apologize for the inconvenient, I've accidentally introduced another bug
when fixed the characters handling.
Please download the patched jar from http://jira.codehaus.org/browse/GEOT-821,
I've already tested it with geoserver trunk.

Gabriel.

On Friday 04 August 2006 20:17, Gabriel Roldán wrote:

hmmm...
first sorry for catching up so late, I've lose the thread and just saw the
message today.

Unfortunately I have _no idea_ of what could be happening. I though the
problem was well isolated and the test case I've added would be enough for
catching, at least, the problem in cuestion.
Obviously was wrong, going to dig into it right now, hope to come back with
an answer asap.

Gabriel

On Wednesday 02 August 2006 17:25, Chris Holmes wrote:
> Ugh. Very not fun.
>
> Looking in to it, it actually looks like the bug fix for filters
> introduced the new bug.
>
> Gabriel, any ideas for a quick fix/why it's working this way?
>
> (I just completely confirmed it was the problem, did the latest build
> _with_ the fix, and got Mark's behavior, and did the latest build with
> the only change being that I merged in the old way of doing things, and
> it worked fine).
>
> If Gabriel doesn't have an idea I'll dig in to it today. I imagine it's
> something with the characters not getting up to the property parsing in
> GeoServer.
>
> best regards,
>
> Chris
>
> Mark Presling wrote:
> > Thanks Chris. It looks as though that has fixed my filter problem.
> >
> > However, I have a curly one for you...
> >
> > Now that I have patched GeoServer 1.3.1 with the new gt-main.jar I get
> > different responses from the WFS when I use the following query:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <GetFeature xmlns=*MailScanner has detected a possible fraud attempt
> > from "www.opengis.net" claiming to be* "http://www.opengis.net/wfs&quot;
> > xmlns:gml=*MailScanner has detected a possible fraud attempt from
> > "www.opengis.net" claiming to be* "http://www.opengis.net/gml&quot;
> > xmlns:ogc=*MailScanner has detected a possible fraud attempt from
> > "www.opengis.net" claiming to be* "http://www.opengis.net/ogc&quot;
> > version="1.0.0" service="WFS" outputFormat="GML2"><Query
> > typeName="topp:nmcregion_poly"><ogc:PropertyName>regionid</ogc:Property
> >Na me>
> > <ogc:Filter><ogc:Intersects><ogc:PropertyName>the_geom</ogc:PropertyNam
> >e> <gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinates
> > decimal="." cs="," ts=" ">2454899.90234375,5850231.933593749
> > 2454899.90234375,5855725.097656249 2460393.06640625,5855725.097656249
> > 2460393.06640625,5850231.933593749
> > 2454899.90234375,5850231.933593749</gml:coordinates> </gml:LinearRing>
> > </gml:outerBoundaryIs>
> > </gml:Polygon>
> > </ogc:Intersects>
> > </ogc:Filter>
> > </Query>
> > </GetFeature>
> >
> > On the original one I get this response:
> >
> > <wfs:FeatureCollection xmlns:wfs=*MailScanner has detected a possible
> > fraud attempt from "www.opengis.net" claiming to be*
> > "http://www.opengis.net/wfs&quot; xmlns:topp=*MailScanner has detected a
> > possible fraud attempt from "www.openplans.org" claiming to be*
> > "http://www.openplans.org/topp&quot; xmlns:gml=*MailScanner has detected a
> > possible fraud attempt from "www.opengis.net" claiming to be*
> > "http://www.opengis.net/gml&quot; xmlns:xsi=*MailScanner has detected a
> > possible fraud attempt from "www.w3.org" claiming to be*
> > "http://www.w3.org/2001/XMLSchema-instance&quot;
> > xsi:schemaLocation=*MailScanner has detected a possible fraud attempt
> > from "www.openplans.org" claiming to be* "http://www.openplans.org/topp
> > https://xxx/geoserver/wfs/DescribeFeatureType?typeName=topp:nmcregion_p
> >ol y http://www.opengis.net/wfs
> > https://xxx/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd&quot;&gt; <gml:boundedBy>
> > <gml:Box srsName=*MailScanner has detected a possible fraud attempt
> > from "www.opengis.net" claiming to be*
> > "http://www.opengis.net/gml/srs/epsg.xml#27200&quot;&gt; <gml:coordinates
> > decimal="." cs="," ts=" ">2254760,5583607.2
> > 2598181.9,5921952.9</gml:coordinates> </gml:Box>
> > </gml:boundedBy>
> > <gml:featureMember>
> > <topp:nmcregion_poly fid="nmcregion_poly.13">
> > <topp:regionid>14</topp:regionid>
> > </topp:nmcregion_poly>
> > </gml:featureMember>
> > </wfs:FeatureCollection>
> >
> > Note that it has only returned the regionid attribute as requested in
> > the Query. Now, the patched GeoServer returns:
> >
> > <wfs:FeatureCollection xmlns:wfs=*MailScanner has detected a possible
> > fraud attempt from "www.opengis.net" claiming to be*
> > "http://www.opengis.net/wfs&quot; xmlns:topp=*MailScanner has detected a
> > possible fraud attempt from "www.openplans.org" claiming to be*
> > "http://www.openplans.org/topp&quot; xmlns:gml=*MailScanner has detected a
> > possible fraud attempt from "www.opengis.net" claiming to be*
> > "http://www.opengis.net/gml&quot; xmlns:xsi=*MailScanner has detected a
> > possible fraud attempt from "www.w3.org" claiming to be*
> > "http://www.w3.org/2001/XMLSchema-instance&quot;
> > xsi:schemaLocation=*MailScanner has detected a possible fraud attempt
> > from "www.openplans.org" claiming to be* "http://www.openplans.org/topp
> > http://192.168.201.9:8080/geoserver/wfs/DescribeFeatureType?typeName=to
> >pp
> >
> >:nmcregion_poly http://www.opengis.net/wfs
> >
> > http://192.168.201.9:8080/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd&quot;&gt;
> > <gml:boundedBy>
> > <gml:Box srsName=*MailScanner has detected a possible fraud attempt
> > from "www.opengis.net" claiming to be*
> > "http://www.opengis.net/gml/srs/epsg.xml#27200&quot;&gt; <gml:coordinates
> > decimal="." cs="," ts=" ">2254760.0000013,5583607.19995544
> > 2598181.89999988,5921952.89999064</gml:coordinates> </gml:Box>
> > </gml:boundedBy>
> > <gml:featureMember>
> > <topp:nmcregion_poly fid="nmcregion_poly.13">
> > <topp:regionid>14</topp:regionid>
> > <topp:regionname>Canterbury</topp:regionname>
> > <topp:the_geom>
> > <gml:MultiPolygon srsName=*MailScanner has detected a possible
> > fraud attempt from "www.opengis.net" claiming to be*
> > "http://www.opengis.net/gml/srs/epsg.xml#27200&quot;&gt; <gml:polygonMember>
> > <gml:Polygon>
> > <gml:extrude>1</gml:extrude>
> > <gml:altitudeMode>relativeToGround</gml:altitudeMode>
> > <gml:outerBoundaryIs>
> > <gml:LinearRing>
> > ........snip......
> >
> > So does that mean that the head of GeoTools 2.2.x is no longer meeting
> > the contract to only return the requested attributes or what? It may be
> > something to check out for the next release of GeoServer.
> >
> > It looks as though I am going to need to apply the patch for the
> > filters to the revision that 1.3.1 was built on. Is anyone able to
> > point me in the right direction on how to do this please? Will I have
> > to set up a Maven build environment for GeoTools? I have never actually
> > used Maven so that could be interesting. I would also need to know the
> > tag/revision that 1.3.1 was built against.
> >
> > Thanks,
> > Mark
> >
> > Chris Holmes wrote:
> >> Mark Presling wrote:
> >>> Thankyou so much for getting that into 2.2.x! Now I have a question
> >>> for the GeoServer people specifically...
> >>>
> >>> I am currently using GeoServer 1.3.1. Therefore, I will need to
> >>> upgrade. Here are my questions about this:
> >>> 1. Is the upgrade path from 1.3.1 to 1.3.3 likely to cause me any
> >>> grief on the WFS side? Things to consider may be inconsistent
> >>> GeoTools libs between version 1.1.M7 of uDig and GeoServer.
> >>
> >> Not very likely. The only real changes between 1.3.1 and 1.3.3 were
> >> kml improvements.
> >>
> >>> 2. Can I patch 1.3.3 with the latest 2.2.x jars to get this patch
> >>> into 1.3.3?
> >>
> >> Yes, you should just need a new 2.2.x main jar. In geoserver this is
> >> called gt2-main.jar
> >>
> >>> 3. Do I need to go to 1.3.3 or can I just patch 1.3.1 somehow?
> >>
> >> You should be able to patch 1.3.1
> >>
> >>> 4. If I can patch GeoServer with the new 2.2.x jars, where can I get
> >>> them from?
> >>
> >> I just did a build, you can grab it from:
> >> http://jira.codehaus.org/browse/GEOT-821
> >>
> >> I only have maven1 working, so if there's any funkiness let me know,
> >> and we can get another build.
> >>
> >>> We are trying to get the project to production immediately and this
> >>> problem is holding us back, so if anyone has any suggestions on how
> >>> we can achieve this in a safe manner in the shortest amount of time I
> >>> would really appreciate it!
> >>
> >> Cool, this should hopefully get you going.
> >>
> >> best regards,
> >>
> >> Chris
> >>
> >>> Thanks,
> >>> Mark
> >>>
> >>> Gabriel Roldán wrote:
> >>>> Chris, Mark:
> >>>>
> >>>> I've applied the patch to 2.2.x and trunk, and added a test case to
> >>>> ensure
> >>>> the characters(char, int, int) method contract is respected (not
> >>>> loosing content).
> >>>>
> >>>> don't know if Mark is building from source, in any case he would
> >>>> need a gt-main jar to get it working.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Gabriel.
> >>>>
> >>>> On Monday 31 July 2006 18:56, Gabriel Roldán wrote:
> >>>>> indeed,
> >>>>> http://jira.codehaus.org/browse/GEOT-821
> >>>>>
> >>>>> going to apply the patch to 2.2.x and trunk right now.
> >>>>>
> >>>>> Gabriel
> >>>>>
> >>>>> On Monday 31 July 2006 17:59, Chris Holmes wrote:
> >>>>>> I think it may actually have to do with the limitations of the SAX
> >>>>>> parser, but I thought we had a workaround for it. Like it'll only
> >>>>>> chunk
> >>>>>> a certain number of characters at once.
> >>>>>>
> >>>>>> Gabriel, I feel like you may have had this bug and/or a fix for
> >>>>>> it? I
> >>>>>> know someone did. Maybe it didn't get ported over at some point?
> >>>>>>
> >>>>>> Mark Presling wrote:
> >>>>>>> Hi all,
> >>>>>>>
> >>>>>>> Sorry about the cross-list post but I'm not sure exactly where
> >>>>>>> this problem lies.
> >>>>>>>
> >>>>>>> (Ignore until you read the sentence below)
> >>>>>>>
> >>>>>>> 598072759 [FINE] org.vfny.geoserver.servlets.AbstractService -
> >>>>>>> ------------XML POST START----------- <?xml version="1.0"
> >>>>>>> encoding="UTF-8"?>
> >>>>>>> <GetFeature xmlns=*MailScanner has detected a possible fraud
> >>>>>>> attempt from "www.opengis.net" claiming to be* *MailScanner has
> >>>>>>> detected a possible fraud attempt from "www.opengis.net" claiming
> >>>>>>> to be* "http://www.opengis.net/wfs&quot;
> >>>>>>> xmlns:gml=*MailScanner has detected a possible fraud attempt from
> >>>>>>> "www.opengis.net" claiming to be* *MailScanner has detected a
> >>>>>>> possible fraud attempt from "www.opengis.net" claiming to be*
> >>>>>>> "http://www.opengis.net/gml&quot;
> >>>>>>> xmlns:ogc=*MailScanner has detected a possible fraud attempt from
> >>>>>>> "www.opengis.net" claiming to be* *MailScanner has detected a
> >>>>>>> possible fraud attempt from "www.opengis.net" claiming to be*
> >>>>>>> "http://www.opengis.net/ogc&quot;
> >>>>>>> version="1.0.0" service="WFS" outputFormat="GML2"><Query
> >>>>>>> typeName="topp:roadevent_pnt"><ogc:PropertyName>roadeventid</ogc:
> >>>>>>>Pr oper
> >>>>>>>
> >>>>>>> ty Name>
> >>>>>>> <ogc:Filter><ogc:And><ogc:Intersects><ogc:PropertyName>the_geom</
> >>>>>>>og c:Pr
> >>>>>>>
> >>>>>>> op ertyName>
> >>>>>>> <gml:Polygon><gml:outerBoundaryIs><gml:LinearRing><gml:coordinate
> >>>>>>>s decimal="." cs="," ts=" ">2224073.5294117643,5725938.522408964
> >>>>>>> 2224073.5294117643,6077972.522408964
> >>>>>>> 2740784.4985994394,6077972.522408964
> >>>>>>> 2740784.4985994394,5725938.522408964
> >>>>>>> 2224073.5294117643,5725938.522408964</gml:coordinates>
> >>>>>>> </gml:LinearRing> </gml:outerBoundaryIs>
> >>>>>>> </gml:Polygon>
> >>>>>>> </ogc:Intersects>
> >>>>>>> <ogc:And><ogc:Not><ogc:PropertyIsGreaterThan><ogc:PropertyName>st
> >>>>>>>ar tdat
> >>>>>>>
> >>>>>>> e< /ogc:PropertyName>
> >>>>>>> <ogc:Literal>1.155523188718E12</ogc:Literal>
> >>>>>>> </ogc:PropertyIsGreaterThan>
> >>>>>>> </ogc:Not>
> >>>>>>> <ogc:Not><ogc:And><ogc:PropertyIsEqualTo><ogc:PropertyName>events
> >>>>>>>ta tus<
> >>>>>>>
> >>>>>>> /o gc:PropertyName> <ogc:Literal>Closed</ogc:Literal>
> >>>>>>> </ogc:PropertyIsEqualTo>
> >>>>>>> <ogc:PropertyIsLessThan><ogc:PropertyName>enddate</ogc:PropertyNa
> >>>>>>>me
> >>>>>>>
> >>>>>>>> <ogc:Literal>1.154227188718E12</ogc:Literal>
> >>>>>>>
> >>>>>>> </ogc:PropertyIsLessThan>
> >>>>>>> </ogc:And>
> >>>>>>> </ogc:Not>
> >>>>>>> <ogc:Not><ogc:PropertyIsEqualTo><ogc:PropertyName>eventstatus</og
> >>>>>>>c: Prop
> >>>>>>>
> >>>>>>> er tyName> <ogc:Literal>Deleted</ogc:Literal>
> >>>>>>> </ogc:PropertyIsEqualTo>
> >>>>>>> </ogc:Not>
> >>>>>>> <ogc:Or><ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:P
> >>>>>>>ro pert
> >>>>>>>
> >>>>>>> yN ame> <ogc:Literal>Road Hazard</ogc:Literal>
> >>>>>>> </ogc:PropertyIsEqualTo>
> >>>>>>> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyN
> >>>>>>>am e>
> >>>>>>>
> >>>>>>> <ogc:Literal>Road Work</ogc:Literal>
> >>>>>>> </ogc:PropertyIsEqualTo>
> >>>>>>> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyN
> >>>>>>>am e>
> >>>>>>>
> >>>>>>> <ogc:Literal>Area Warning</ogc:Literal>
> >>>>>>> </ogc:PropertyIsEqualTo>
> >>>>>>> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyN
> >>>>>>>am e>
> >>>>>>>
> >>>>>>> <ogc:Literal>Compliment</ogc:Literal>
> >>>>>>> </ogc:PropertyIsEqualTo>
> >>>>>>> <ogc:PropertyIsEqualTo><ogc:PropertyName>eventtype</ogc:PropertyN
> >>>>>>>am e>
> >>>>>>>
> >>>>>>> <ogc:Literal>Complaint</ogc:Literal>
> >>>>>>> </ogc:PropertyIsEqualTo>
> >>>>>>> <ogc:PropertyIsEqualTo><ogc:PropertyName>*eventtype*</ogc:Propert
> >>>>>>>yN ame>
> >>>>>>>
> >>>>>>> <ogc:Literal>Damage Report</ogc:Literal>
> >>>>>>> </ogc:PropertyIsEqualTo>
> >>>>>>> </ogc:Or>
> >>>>>>> </ogc:And>
> >>>>>>> </ogc:And>
> >>>>>>> </ogc:Filter>
> >>>>>>> </Query>
> >>>>>>> </GetFeature>
> >>>>>>>
> >>>>>>>
> >>>>>>> ------------XML POST END-----------
> >>>>>>> 598072774 [FINE]
> >>>>>>> org.vfny.geoserver.wfs.requests.readers.GetFeatureXmlReader -
> >>>>>>> just parsed: org.xml.sax.InputSource@anonymised.com 598072774 [INFO]
> >>>>>>> org.vfny.geoserver.servlets.AbstractService - handling request:
> >>>>>>> Request: null
> >>>>>>> output format:GML2
> >>>>>>> max features:2147483647
> >>>>>>> version:
> >>>>>>> queries:
> >>>>>>> Query
> >>>>>>> feature type: topp:roadevent_pnt
> >>>>>>> filter: [[ the_geom intersects POLYGON ((2224073.5294117643
> >>>>>>> 5725938.522408964, 2224073.5294117643 6077972.522408964,
> >>>>>>> 2740784.4985994394 6077972.522408964, 2740784.4985994394
> >>>>>>> 5725938.522408964, 2224073.5294117643 5725938.522408964)) ] AND
> >>>>>>> [NOT [
> >>>>>>> startdate > 1.155523188718E12 ] AND NOT [[ eventstatus = Closed ]
> >>>>>>> AND [
> >>>>>>> enddate < 1.154227188718E12 ]] AND NOT [ eventstatus = Deleted ]
> >>>>>>> AND [[
> >>>>>>> eventtype = Road Hazard ] OR [ eventtype = Road Work ] OR [
> >>>>>>> eventtype =
> >>>>>>> Area Warning ] OR [ eventtype = Compliment ] OR [ eventtype =
> >>>>>>> Complaint
> >>>>>>> ] OR [ *ttype* = Damage Report ]]]] [properties: roadeventid]
> >>>>>>>
> >>>>>>>
> >>>>>>> This is a WFS request sent to GeoServer 1.3.1 from uDig.
> >>>>>>> Admittedly it
> >>>>>>> is quite a big filter but I can't really get away from that.
> >>>>>>>
> >>>>>>> As you can see the last attribute filter in the XML post says
> >>>>>>> "... or
> >>>>>>> eventtype = Damage Report". However, the parsed GeoTools filter
> >>>>>>> below
> >>>>>>> that says "... OR [ ttype = Damage Report ]". This only happens
> >>>>>>> when I
> >>>>>>> have this number of attribute filters turned on, if I reduce the
> >>>>>>> number
> >>>>>>> by one everything works correctly.
> >>>>>>>
> >>>>>>> The amount of truncation appears random as well. Sometimes the
> >>>>>>> filter
> >>>>>>> ends up as "OR [ e = Damage Report ]".
> >>>>>>>
> >>>>>>> Has anyone seen this before or know what can be done about it?
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Mark
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> This message has been scanned for viruses and
> >>>>>>> dangerous content by *MailScanner*
> >>>>>>> <http://www.mailscanner.info/&gt;, and
> >>>>>>> is believed to be clean.
> >>>>>>>
> >>>>>>> -----------------------------------------------------------------
> >>>>>>>-- ----
> >>>>>>>
> >>>>>>> -- Take Surveys. Earn Cash. Influence the Future of IT
> >>>>>>> Join SourceForge.net's Techsay panel and you'll get the chance to
> >>>>>>> share
> >>>>>>> your opinions on IT & business topics through brief surveys --
> >>>>>>> and earn
> >>>>>>> cash
> >>>>>>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CI
> >>>>>>>D= DEVD
> >>>>>>>
> >>>>>>> EV
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> -----------------------------------------------------------------
> >>>>>>>-- ----
> >>>>>>>
> >>>>>>> -
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> Geoserver-users mailing list
> >>>>>>> Geoserver-users@lists.sourceforge.net
> >>>>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >>>>>>>
> >>>>>>>
> >>>>>>> !DSPAM:1003,44cd6f7d13131971556521!
> >>>
> >>> ---------------------------------------------------------------------
> >>>-- --
> >>>
> >>> Take Surveys. Earn Cash. Influence the Future of IT
> >>> Join SourceForge.net's Techsay panel and you'll get the chance to
> >>> share your
> >>> opinions on IT & business topics through brief surveys -- and earn
> >>> cash
> >>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DE
> >>>VD EV
> >>>
> >>>
> >>> !DSPAM:1003,44ceadb6116861362196140!
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>>-- -
> >>>
> >>> _______________________________________________
> >>> Geoserver-users mailing list
> >>> Geoserver-users@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >>>
> >>>
> >>> !DSPAM:1003,44ceadb6116861362196140!
> >>
> >> ----------------------------------------------------------------------
> >>-- - Take Surveys. Earn Cash. Influence the Future of IT
> >> Join SourceForge.net's Techsay panel and you'll get the chance to
> >> share your opinions on IT & business topics through brief surveys --
> >> and earn cash
> >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEV
> >>DE V
> >> ----------------------------------------------------------------------
> >>--
> >>
> >> _______________________________________________
> >> Geotools-devel mailing list
> >> Geotools-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/geotools-devel
> >
> > !DSPAM:1003,44d01312239116309890654!
> > --
> > This message has been scanned for viruses and
> > dangerous content by *MailScanner* <http://www.mailscanner.info/&gt;, and
> > is believed to be clean.
> >
> > -----------------------------------------------------------------------
> >-- Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> > your opinions on IT & business topics through brief surveys -- and earn
> > cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD
> >EV
> >
> > !DSPAM:1003,44d01312239116309890654!
> >
> >
> > -----------------------------------------------------------------------
> >-
> >
> > _______________________________________________
> > Geoserver-users mailing list
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
> >
> > !DSPAM:1003,44d01312239116309890654!

--
Gabriel Roldán (groldan@anonymised.com)
Axios Engineering (http://www.axios.es)
Tel. +34 944 41 63 84
Fax. +34 944 41 64 90