[Geotools-devel] GeoTools Build Report [ 2006/04/27 23:55 ]
GeoTools2 module build report 20060427 gt2:referencing cleaned, compiled, tested, INSTALLED 2357 gt2:sample-data cleaned, compiled, tested, INSTALLED 2358 gt2:coverage cleaned, compiled, tested, INSTALLED 2359 gt2:api cleaned, compiled, tested, INSTALLED 2359 gt2:main cleaned, compiled, tested, INSTALLED 0002 gt2:shapefile cleaned, compiled, tested, INSTALLED 0002 gt2:indexed-shapefile cleaned, compiled --- release is 2.1.x --- --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
RE: [Geotools-devel] GeoTools license information incorrect in the Wiki
Here is a list of GPL-licensed files that we found (by searching for GPL in the files): ext\indexed-shapefile\src\org\geotools\data\shapefile\indexed\IndexedSha pefileDataStoreFactory.java ext\validation\src\org\geotools\validation\attributes\EqualityValidation .java ext\validation\src\org\geotools\validation\attributes\NullZeroValidation .java ext\validation\src\org\geotools\validation\attributes\RangeValidation.ja va ext\validation\src\org\geotools\validation\attributes\UniqueFIDValidatio n.java ext\validation\src\org\geotools\validation\attributes\UniquityValidation .java ext\validation\src\org\geotools\validation\DefaultFeatureValidation.java ext\validation\src\org\geotools\validation\DefaultIntegrityValidation.ja va ext\validation\src\org\geotools\validation\dto\PlugInDTO.java ext\validation\src\org\geotools\validation\dto\TestDTO.java ext\validation\src\org\geotools\validation\dto\TestSuiteDTO.java ext\validation\src\org\geotools\validation\FeatureValidation.java ext\validation\src\org\geotools\validation\IntegrityValidation.java ext\validation\src\org\geotools\validation\PlugIn.java ext\validation\src\org\geotools\validation\relate\ContainsIntegrity.java ext\validation\src\org\geotools\validation\relate\ContainsIntegrityBeanI nfo.java ext\validation\src\org\geotools\validation\relate\CrossesIntegrity.java ext\validation\src\org\geotools\validation\relate\CrossesIntegrityBeanIn fo.java ext\validation\src\org\geotools\validation\relate\DisjointIntegrity.java ext\validation\src\org\geotools\validation\relate\DisjointIntegrityBeanI nfo.java ext\validation\src\org\geotools\validation\relate\IntersectsIntegrity.ja va ext\validation\src\org\geotools\validation\relate\IntersectsIntegrityBea nInfo.java ext\validation\src\org\geotools\validation\relate\OverlapsIntegrity.java ext\validation\src\org\geotools\validation\relate\OverlapsIntegrityBeanI nfo.java ext\validation\src\org\geotools\validation\relate\RelateIntegrity.java ext\validation\src\org\geotools\validation\relate\RelateIntegrityBeanInf o.java ext\validation\src\org\geotools\validation\relate\RelationIntegrity.java ext\validation\src\org\geotools\validation\relate\RelationIntegrityBeanI nfo.java ext\validation\src\org\geotools\validation\relate\SpatialTestCase.java ext\validation\src\org\geotools\validation\relate\TouchesIntegrity.java ext\validation\src\org\geotools\validation\relate\TouchesIntegrityBeanIn fo.java ext\validation\src\org\geotools\validation\relate\WithinIntegrity.java ext\validation\src\org\geotools\validation\relate\WithinIntegrityBeanInf o.java ext\validation\src\org\geotools\validation\spatial\IsValidGeometryValida tion.java ext\validation\src\org\geotools\validation\spatial\LineCoveredByPolygonV alidation.java ext\validation\src\org\geotools\validation\spatial\LineNoSelfOverlapping Validation.java ext\validation\src\org\geotools\validation\spatial\LinesNotIntersectVali dation.java ext\validation\src\org\geotools\validation\Validation.java ext\validation\src\org\geotools\validation\ValidationBeanInfo.java ext\validation\src\org\geotools\validation\ValidationResults.java ext\validation\src\org\geotools\validation\Validator.java ext\validation\src\org\geotools\validation\xml\ArgHelper.java ext\validation\src\org\geotools\validation\xml\ReaderUtils.java ext\validation\src\org\geotools\validation\xml\ValidationException.java ext\validation\src\org\geotools\validation\xml\WriterUtils.java ext\validation\src\org\geotools\validation\xml\XMLReader.java ext\validation\test\org\geotools\validation\attributes\NullZeroValidatio nTest.java ext\validation\test\org\geotools\validation\attributes\RangeFeatureValid ationTest.java ext\validation\test\org\geotools\validation\FeatureValidationTest.java ext\validation\test\org\geotools\validation\IntegrityValidationTest.java ext\validation\test\org\geotools\validation\relate\OverlapsIntegrityTest .java ext\validation\test\org\geotools\validation\RoadNetworkValidationResults .java ext\validation\test\org\geotools\validation\RoadValidationResults.java ext\validation\test\org\geotools\validation\UniqueFIDIntegrityValidation .java ext\validation\test\org\geotools\validation\ValidationPlugInTester.java ext\validation\test\org\geotools\validation\ValidationProcessorTest.java ext\validation\test\org\geotools\validation\xml\XMLReaderTest.java module\main\test\org\geotools\filter\TestFilterHandler.java plugin\mysql\src\org\geotools\data\mysql\MySQLDataStoreFactory.java plugin\tiger\src\org\geotools\data\tiger\TigerDataStoreFactory.java Pertti -Original Message- From: ext Jody Garnett [mailto:[EMAIL PROTECTED] Sent: 18 April 2006 16:20 To: Haggstrom Hans (Nokia-NET/Espoo) Cc: geotools-devel@lists.sourceforge.net; Tapola Pertti (Nokia-NET/Espoo); Richard Gould Subject: Re: [Geotools-devel] GeoTools license information incorrect in the Wiki [EMAIL PROTECTED] wrote: Good timing Hans, we are in the middle of an IP review as part of our involvement with the OSGEO Foundation, it seems you
RE: [Geotools-devel] GeoTools license information incorrect in the Wiki
This is what I found in the (version 2.1.0) sources, at the beginning of MySQLDataStoreFactory.java: /* Copyright (c) 2001, 2003 TOPP - www.openplans.org. All rights reserved. * This code is licensed under the GPL 2.0 license, availible at the root * application directory. */ /* *Geotools2 - OpenSource mapping toolkit *http://geotools.org *(C) 2002, Geotools Project Managment Committee (PMC) * *This library is free software; you can redistribute it and/or *modify it under the terms of the GNU Lesser General Public *License as published by the Free Software Foundation; *version 2.1 of the License. * *This library is distributed in the hope that it will be useful, *but WITHOUT ANY WARRANTY; without even the implied warranty of *MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *Lesser General Public License for more details. * */ So, there are two conflicting licenses in it. Pertti -Original Message- From: ext Richard Gould [mailto:[EMAIL PROTECTED] Sent: 23 April 2006 23:34 To: Tapola Pertti (Nokia-NET/Espoo) Cc: [EMAIL PROTECTED]; Haggstrom Hans (Nokia-NET/Espoo); geotools-devel@lists.sourceforge.net Subject: Re: [Geotools-devel] GeoTools license information incorrect in the Wiki Thanks Pertti. I have updated all of the modules to indicate that there is an issue. I will bring it up during tomorrow's GeoTools meeting as well. Note that I could not find anything wrong in MySQLDataStoreFactory.java Updated the pages at: http://docs.codehaus.org/display/GEOTOOLS/Indexed-Shapefile http://docs.codehaus.org/display/GEOTOOLS/Main http://docs.codehaus.org/display/GEOTOOLS/Tiger http://docs.codehaus.org/display/GEOTOOLS/Validation Cheers, Richard [EMAIL PROTECTED] wrote: Here is a list of GPL-licensed files that we found (by searching for GPL in the files): ext\indexed-shapefile\src\org\geotools\data\shapefile\indexed\IndexedS ha pefileDataStoreFactory.java ext\validation\src\org\geotools\validation\attributes\EqualityValidati on .java ext\validation\src\org\geotools\validation\attributes\NullZeroValidati on .java ext\validation\src\org\geotools\validation\attributes\RangeValidation. ja va ext\validation\src\org\geotools\validation\attributes\UniqueFIDValidat io n.java ext\validation\src\org\geotools\validation\attributes\UniquityValidati on .java ext\validation\src\org\geotools\validation\DefaultFeatureValidation.ja va ext\validation\src\org\geotools\validation\DefaultIntegrityValidation. ja va ext\validation\src\org\geotools\validation\dto\PlugInDTO.java ext\validation\src\org\geotools\validation\dto\TestDTO.java ext\validation\src\org\geotools\validation\dto\TestSuiteDTO.java ext\validation\src\org\geotools\validation\FeatureValidation.java ext\validation\src\org\geotools\validation\IntegrityValidation.java ext\validation\src\org\geotools\validation\PlugIn.java ext\validation\src\org\geotools\validation\relate\ContainsIntegrity.ja va ext\validation\src\org\geotools\validation\relate\ContainsIntegrityBea nI nfo.java ext\validation\src\org\geotools\validation\relate\CrossesIntegrity.jav a ext\validation\src\org\geotools\validation\relate\CrossesIntegrityBean In fo.java ext\validation\src\org\geotools\validation\relate\DisjointIntegrity.ja va ext\validation\src\org\geotools\validation\relate\DisjointIntegrityBea nI nfo.java ext\validation\src\org\geotools\validation\relate\IntersectsIntegrity. ja va ext\validation\src\org\geotools\validation\relate\IntersectsIntegrityB ea nInfo.java ext\validation\src\org\geotools\validation\relate\OverlapsIntegrity.ja va ext\validation\src\org\geotools\validation\relate\OverlapsIntegrityBea nI nfo.java ext\validation\src\org\geotools\validation\relate\RelateIntegrity.java ext\validation\src\org\geotools\validation\relate\RelateIntegrityBeanI nf o.java ext\validation\src\org\geotools\validation\relate\RelationIntegrity.ja va ext\validation\src\org\geotools\validation\relate\RelationIntegrityBea nI nfo.java ext\validation\src\org\geotools\validation\relate\SpatialTestCase.java ext\validation\src\org\geotools\validation\relate\TouchesIntegrity.jav a ext\validation\src\org\geotools\validation\relate\TouchesIntegrityBean In fo.java ext\validation\src\org\geotools\validation\relate\WithinIntegrity.java ext\validation\src\org\geotools\validation\relate\WithinIntegrityBeanI nf o.java ext\validation\src\org\geotools\validation\spatial\IsValidGeometryVali da tion.java ext\validation\src\org\geotools\validation\spatial\LineCoveredByPolygo nV alidation.java ext\validation\src\org\geotools\validation\spatial\LineNoSelfOverlappi ng Validation.java ext\validation\src\org\geotools\validation\spatial\LinesNotIntersectVa li dation.java ext\validation\src\org\geotools\validation\Validation.java ext\validation\src\org\geotools\validation\ValidationBeanInfo.java
[Geotools-devel] (no subject)
Martin Desruisseaux wrote: [EMAIL PROTECTED] a écrit : Okay, its there now. I had awful problem moving the changes from 2.2.x to trunk. Thanks, it seems to compile file now. I noticed the addition of the following dependency: import EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap; Is it appropriate if I had the following comment? // TODO: replace by java.util.concurrent.ConcurrentHashMap // when we will be allowed to target J2SE 1.5. I dont know anything about this -- where is it used? dave -- This mail sent through IMP: https://webmail.limegroup.com/ --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642 ___ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
[Geotools-devel] more than one layer on a map
Hello! Back in May 2005 I tested GeoServer, and there was Tasmania and I was able to turn on and to turn off layers. Download GeoServer this week again, many things have happened - this is great. The Tasmanian example as I saw it back in May 2005 is gone. Not that I am worried about Tasmania. I would like to have a number of Layers, beeing able to turn those on and off, I am using Shapefiles. Is there any tutorial on this ? If so, could you direct med there. If not, how would I create a map with X-number of layers ? best regards, i _ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] more than one layer on a map
in er wrote: Hello! Back in May 2005 I tested GeoServer, and there was Tasmania and I was able to turn on and to turn off layers. Download GeoServer this week again, many things have happened - this is great. The Tasmanian example as I saw it back in May 2005 is gone. Not to worry it will be back in the next release, the questions you are are mostly about the MapBuilder application that geoserver ships with (so I am not sure how to help), but there are a number of great map viewers out there that can talk to GeoServer... Jody --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
[Geotools-devel] Making FeatureType/AttributeType serializable
Hi, we are working on an application where we need to edit FeatureType/AttributeType stuff in a rich client, and the send them back to the server for update. The problem is, the communication protocol uses serialization, and these classes are not serializable. Can we mark them as Serializable or you do see a good reason not to? Please vote :-) Cheers Andrea Aime PS: btw, also DefaultFeature and the like are not serializable. Too bad in my opinion, they should be. What about changing these too? --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] Making FeatureType/AttributeType serializable
First off, I like the idea. I though I'd provide a heads up here ... a couple months back I was doing some Jump developement, where features are serializable. During this time, the client did some data processing and saved the serialized results ... and thus came the issue: we could not read the pevious build ... Now I will admit it was some legacy code we were working with, and the serial guid/version had not been set, but I was hoping people would think about this issue. Some solutions which some to mind, include versioning the serializable pieces independantly (so take the feature stuff into it's own jar ... not always versioning the jar when GT versions). Alternatively, I believe serialization has some methods of forcing versions to work across compilations (without writing a custom serialization routine) ... but I havn't done this so not sure how well it works. Cheers David On 4/28/06, Richard Gould [EMAIL PROTECTED] wrote: Jody Garnett wrote: Andrea Aime wrote: Hi, we are working on an application where we need to edit FeatureType/AttributeType stuff in a rich client, and the send them back to the server for update. The problem is, the communication protocol uses serialization, and these classes are not serializable. Can we mark them as Serializable or you do see a good reason not to? Please vote :-) +1(although perhaps edit is too strong a word as they are immutable). PS: btw, also DefaultFeature and the like are not serializable. Too bad in my opinion, they should be. What about changing these too? That would be a nice experiment, but you would need to ensure that any and all data stored in the feature is serializable.As a compromise please talk to justing about making SimpleFeature serialiable (as it is already restricted to simple types).+1 ---Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___Geotools-devel mailing listGeotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] Making FeatureType/AttributeType serializable
David Zwiers ha scritto: First off, I like the idea. I though I'd provide a heads up here ... a couple months back I was doing some Jump developement, where features are serializable. During this time, the client did some data processing and saved the serialized results ... and thus came the issue: we could not read the pevious build ... Now I will admit it was some legacy code we were working with, and the serial guid/version had not been set, but I was hoping people would think about this issue. Some solutions which some to mind, include versioning the serializable pieces independantly (so take the feature stuff into it's own jar ... not always versioning the jar when GT versions). Alternatively, I believe serialization has some methods of forcing versions to work across compilations (without writing a custom serialization routine) ... but I havn't done this so not sure how well it works. Using serialization for long time persistance is a way to look for problems. There are better ways, such as using XStream if you don't have other means (such as GML). I'm asking serialization as a mean to send things over the wire, so the versioning problem is not an issue (client and server should use the same geotools jars). Cheers Andrea --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] Making FeatureType/AttributeType serializable
Richard Gould wrote: Jody Garnett wrote: Andrea Aime wrote: Hi, we are working on an application where we need to edit FeatureType/AttributeType stuff in a rich client, and the send them back to the server for update. The problem is, the communication protocol uses serialization, and these classes are not serializable. Can we mark them as Serializable or you do see a good reason not to? Please vote :-) sounds good... +1 --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
[Geotools-devel] [CC-Trunk] geotools Build Failed
View results here - http://geovista16.geog.psu.edu/cruisecontrol/buildresults/geotools_current?log=log20060428150005 --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
[Geotools-devel] Programmers' Manual Prototype done.
Hey all, I'm done with the prototype for the Programmers' Manual. http://docs.codehaus.org/display/GEOTOOLS/Programmers+Manual+Prototype There are several decisions that are needed by the PMC: 1) what the tutorial examples' package(s) should be 2) what the tutorial examples' license should be 3) where the tutorial examples should live 4) where the graphics should live (all are svg done with inkscape) Comments, revisions, and insults are welcome. Jody, you were interested in particular in the design for each tutorial section. My vision for the tutorial section on the geometric model is essentially fully outlined in the Geometry Tutorial. The section needs a lot more work but you should get the full idea of what I want in it. Finally, I'm still struggling with semantic (mental) models of the library and some of you may have ideas. Are you all aware of how you conceptualize of the library when you use it? I'm hopelessly confused but at least I now have all of my confusion well organized in my head. Currently, I have six different 'looks' on the library: Code Stack view: the library in the context of the hardware, Java stack, outside libs... Model view: what's in the doc Dependency graph view: what you all did at the module level but maybe should be done at the package level. Package list: Each of the two hundred odd packages and where it fits into the code directories, where its api hangs out, where it fits in the 'model view' API list: where the various API's are, probably in context of the Model view. Data model: where the various pieces are, e.g. where a feature's coordinates can be found, where its CRS hangs out... Once I find some clarity with those, I'll draw or compose them and add them to the doc if they look like they help. cheers, adrian --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] Programmers' Manual Prototype done.
Adrian Custer wrote: Hey all, I'm done with the prototype for the Programmers' Manual. http://docs.codehaus.org/display/GEOTOOLS/Programmers+Manual+Prototype Thanks Adrian, Before we get going I am very interested in locking down writing style (sound like a broken record), I want to know what is and what is not fair game to write about. Example Java syntax no (assumed), Web Feature Server maybe (query is inspired by it), Naming yes (implemented by gt)? There are several decisions that are needed by the PMC: 1) what the tutorial examples' package(s) should be The packages should match the module they target. 2) what the tutorial examples' license should be LGPL same as all code, will that get in anyones way? 3) where the tutorial examples should live subversion demo/ 4) where the graphics should live (all are svg done with inkscape) we can directly link pictures in svn into geotools, so perhaps they would be well suited next to the demo the document? Comments, revisions, and insults are welcome. Blood good job mate :-) Jody, you were interested in particular in the design for each tutorial section. My vision for the tutorial section on the geometric model is essentially fully outlined in the Geometry Tutorial. The section needs a lot more work but you should get the full idea of what I want in it. Will review. Finally, I'm still struggling with semantic (mental) models of the library and some of you may have ideas. Are you all aware of how you conceptualize of the library when you use it? I'm hopelessly confused but at least I now have all of my confusion well organized in my head. Currently, I have six different 'looks' on the library: Code Stack view: the library in the context of the hardware, Java stack, outside libs... Only interested for deployment. Model view: what's in the doc Ah abstractions, its whats for breakfast. It is hard because you *need* to start from the middle - aka data. And then work down through aggregation (geometry coordinates) and up through context (featureType, attributeType, geometryAttirbuteType, CRS) and you miss out on the whole data access. Dependency graph view: what you all did at the module level but maybe should be done at the package level. package is supposed to reflect module, put it on the QA list for geotools 3 :-) Package list: Each of the two hundred odd packages and where it fits into the code directories, where its api hangs out, where it fits in the 'model view' Not sure how useful this is, it is already covered by javadocs, and better document using package.html files. API list: where the various API's are, probably in context of the Model view. Not sure what you mean here ... Data model: where the various pieces are, e.g. where a feature's coordinates can be found, where its CRS hangs out... Once I find some clarity with those, I'll draw or compose them and add them to the doc if they look like they help. I would start with the model view, and then with that foundation work on explaining data access. Jody --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
[Geotools-devel] Geometry Function Filters
I am using the Geometry Function Filter for the styles used for
rendering FeatureTypes of type Geometry because I want polygons to be
rendered as polygons and lines as lines and so on.
The problem I'm encountering is that when streaming renderer is
making the request to the Datastore it sends those filters as
well... In the case of WFS the WFS encodes the filters as xml (See
request attachment). At a glance the request looks ok but geoserver
throws an exception, I assume it can't handle the functional
expression.
{\rtf1\mac\ansicpg1\cocoartf824\cocoasubrtf350
{\fonttbl\f0\fswiss\fcharset77 Helvetica;}
{\colortbl;\red255\green255\blue255;}
\margl1440\margr1440\vieww9000\viewh8400\viewkind0
\pard\tx566\tx1133\tx1700\tx2267\tx2834\tx3401\tx3968\tx4535\tx5102\tx5669\tx6236\tx6803\ql\qnatural\pardirnatural
\f0\fs24 \cf0 \
XML POST END---\
115549 [INFO] org.vfny.geoserver.servlets.AbstractService - Had an undefined error: null\
115551 [FINE] org.vfny.geoserver.ServiceException - java.lang.NullPointerException\
115554 [WARNING] org.vfny.geoserver.ServiceException - encountered error: java.lang.NullPointerException\
StackTrace: java.lang.NullPointerException\
at org.geotools.filter.ExpressionSAXParser.end(ExpressionSAXParser.java:205)\
at org.geotools.filter.ExpressionSAXParser.end(ExpressionSAXParser.java:162)\
at org.geotools.filter.FilterFilter.endElement(FilterFilter.java:314)\
at org.geotools.gml.GMLFilterGeometry.endElement(GMLFilterGeometry.java:203)\
at org.geotools.gml.GMLFilterDocument.endElement(GMLFilterDocument.java:286)\
at org.xml.sax.helpers.ParserAdapter.endElement(ParserAdapter.java:626)\
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)\
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)\
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)\
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)\
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)\
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)\
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)\
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)\
at org.xml.sax.helpers.ParserAdapter.parse(ParserAdapter.java:405)\
at org.vfny.geoserver.wfs.requests.readers.GetFeatureXmlReader.read(GetFeatureXmlReader.java:72)\
at org.vfny.geoserver.servlets.AbstractService.doPost(AbstractService.java:375)\
at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doResponse(WfsDispatcher.java:286)\
at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doPost(WfsDispatcher.java:175)\
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)\
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)\
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)\
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:342)\
at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:122)\
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334)\
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:286)\
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)\
at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)\
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)\
at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)\
at org.mortbay.http.HttpServer.service(HttpServer.java:879)\
at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)\
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:961)\
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)\
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:197)\
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:276)\
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)\
\
115558 [FINE] org.vfny.geoserver.ServiceException - return wfs exception is ?xml version=1.0 ?\
ServiceExceptionReport\
version=1.2.0\
xmlns=http://www.opengis.net/ogc\
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance\
xsi:schemaLocation=http://www.opengis.net/ogc http://localhost:8080/geoserver/schemas//wfs/1.0.0/OGC-exception.xsd;\
ServiceException\
java.lang.NullPointerException /ServiceException\
/ServiceExceptionReport\
org.vfny.geoserver.wfs.WfsException: java.lang.NullPointerException\
at
