The stuff we did for resource id (mostly just the interface/class and the
xml bindings for it) has not been committed along with the other wfs2 work.
Reason being simple... it is experimental. Plus given how over deadline we
are for getting this work committed onto the trunk of geotools and geoserver
I simply had to cut it out of the proposal.
That said it should be pretty easy to extract the patch for the new
interface, and the xml bindings. I can do that and you can use that as a
base for discussion/proposal?
On Sun, Oct 16, 2011 at 9:13 PM, Jody Garnett <jody.garn...@gmail.com>wrote:
> Morning Gabriel:
>
> One of the things I was looking out for was how ResourceId was handled in
> WFS2; in reviewing Justin's patch ResourceIdTypeBinding has the following
> ...
>
> public Class getType() {
> return FeatureId.class;
> }
>
> public QName getTarget() {
> return FES.ResourceIdType;
> }
>
> We also have kicking around the code base the concept of an ObjectID as
> defined by Filter 1.1 (apparently it comes from an example in the Filter
> specification which we pressed into the code to ensure we did not assume
> FeatureId everywhere). Is the ResourceID an appropriate place to make use of
> ObjectId - or can we kill it.
>
> I was under the impression that wfs2 used resource id as part of Query in
> order to handle revisions for geogit.
>
> Looking forward to hearing from you.
> --
> Jody Garnett
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>
--
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