On Mon, Oct 17, 2011 at 3:05 PM, Jody Garnett <jody.garn...@gmail.com>wrote:
> The second parameter; nilReason - I don't think it can be supplied as part
> of the query? Instead I think it is supplied by the backing datastore?
> Perhaps it was unable to find a suitable join target ...
>
> Yeah, that is sort of how i interpreted it in the end...
>
> Do we have an example from the wfs2 specification? I really like my filters
> being pure reusable data structures; using them as a return object (or
> giving them a slot to fill in multiple return values sounds very difficult
> to me).
>
Not really, again this was super vague and even when i asked wfs-dev i
didn't really understand. So let's kill the property for now.
> Basically I viewed this as a second return value for the expression.
>
> Yeah... i would say just leave it on the data structure for now and not
> really do anything with it.
>
> I also thought of throwing an exception (I know terrible but it is the
> traditional Java second return value). Could also hold the answer internally
> in a thread local so that different threads can maintain some independence.
> But yeah this seems a really funny idea.
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
