Hello again Justin Sorry for the big delay: I finally got access to the server again and was able to extract some info, as you requested. I put it on the previously created JIRA issue GEOT-2961.
If you need any other info, I'll be happy to send it over. I have to admit, though, that I wasn't really sure what you meant before with "the gml getting sent back to the wfs datastore". Cheers Milton Milton Jonathan wrote: > Hey Justin > > Thanks for the reply. I've just created the JIRA issue, but I haven't > attached anything because the server is not reachable right now. I'll > add that when it becomes available, ok? > > Cheers > Milton > > Justin Deoliveira wrote: >> Interesting, thanks for the detailed description. My guess is that >> somehow the server is not reporting the schema in a way that is >> getting picked up properly. >> >> Can you a) open a jira report and b) attach the following to it: >> >> 1) the gml getting sent back to the wfs datastore >> 2) the describe feature type response for the relevant feature types >> >> Thanks. >> >> -Justin >> >> On 2/22/10 1:56 PM, Milton Jonathan wrote: >>> Hello there >>> >>> I've been having some trouble with a particular WFS server when trying >>> to access its data using the GeoTools WFS DataStore (unfortunately, the >>> server is not a public one for you guys to test). >>> >>> What happens is that SchemaIndexImpl seems to get into trouble (ending >>> in a NPE) because that server returns XSDSchemas that do not have a >>> "Schema For Schema" (which I admit not to know what it is). >>> >>> The problems seem to start in SchemaIndexImpl's constructor: it receives >>> an array of schemas and creates interally a copy of the array with one >>> extra entry, computed by calling "schemas[0].getSchemaForSchema()" (I >>> have no idea why). In this case, it ends up that this last entry remains >>> null. As such, a NPE ends up being thrown by its own buildElementIndex() >>> method, which never checks for a null schema in the array. >>> >>> I thought of opening a JIRA issue with this, but I'm actually not sure: >>> - is it the server's fault that there is an XSDSchema without a "Schema >>> for Schema"? >>> - if it is the server's fault, should GeoTools shield itself from that >>> kind of behavior? (I'd say yes) >>> >>> Cheers >>> Milton >>> >> >> > -- Milton Jonathan Grupo GIS e Meio Ambiente Tecgraf/PUC-Rio Tel: +55-21-3527-2502 ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
