|
From: Jody G. <jod...@gm...> - 2011-10-17 03:13:24
|
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
|