So what is happening with this and who's doing it? Cause this is quite
related to what I am doing with the xlink/href patch. So I make it part
of my patch? Or will it be dealt with separately?
On 05/10/10 17:55, Andrea Aime wrote:
On Tue, Oct 5, 2010 at 11:42 AM,rini.angre...@csiro.au wrote:
On Fri, Oct 8, 2010 at 9:03 AM, Niels niels.charl...@csiro.au wrote:
So what is happening with this and who's doing it? Cause this is quite
related to what I am doing with the xlink/href patch. So I make it part of
my patch? Or will it be dealt with separately?
Unfortunately I used all the
Hi,
in my target schema I have this attribute:
xs:element name=positionAccuracyVector
type=csn:PositionAccuracyVectorType minOccurs=0/
xs:complexType name=PositionAccuracyVectorType
xs:sequence
xs:element name=x type=xs:integer
I think you want these:
http://docs.geoserver.org/latest/en/user/data/app-schema/polymorphism.html#null-or-missing-value
http://docs.geoserver.org/latest/en/user/data/app-schema/polymorphism.html#recode-function
But I don't know if they will help without feature chaining. Rini?
On 05/10/10
On Tue, Oct 5, 2010 at 10:13 AM, Ben Caradoc-Davies
ben.caradoc-dav...@csiro.au wrote:
I think you want these:
http://docs.geoserver.org/latest/en/user/data/app-schema/polymorphism.html#null-or-missing-value
an optional element whose attributes are
not optional
I think you want these:
http://docs.geoserver.org/latest/en/user/data/app-schema/polymorphism.html#null-or-missing-value
http://docs.geoserver.org/latest/en/user/data/app-schema/polymorphism.html#recode-function
But I don't know if they will help
On Tue, Oct 5, 2010 at 10:45 AM, rini.angre...@csiro.au wrote:
You can only use functions to skip the attribute if you use the feature
chaining syntax.
I said syntax, because you can omit linkField, therefore it's not really
chaining it and won't generate the extra joining queries, it only
an optional element whose attributes are
not optional
On Tue, Oct 5, 2010 at 10:45 AM, rini.angre...@csiro.au wrote:
You can only use functions to skip the attribute if you use the feature
chaining syntax.
I said syntax, because you can omit linkField, therefore it's not really
chaining
On Tue, Oct 5, 2010 at 11:13 AM, rini.angre...@csiro.au wrote:
OK Victor pointed out that your attributes x and y have minOccurs = 0, and
that they should be skipped.
He actually put in a logic that will skip the parent's attributes if the
children are missing (skipped) and the parent
, Ben (CESRE, Kensington);
geotools-devel@lists.sourceforge.net
Subject: Re: [Geotools-devel] Mapping an optional element whose attributes are
not optional
On Tue, Oct 5, 2010 at 11:13 AM, rini.angre...@csiro.au wrote:
OK Victor pointed out that your attributes x and y have minOccurs = 0
On Tue, Oct 5, 2010 at 11:42 AM, rini.angre...@csiro.au wrote:
Yes actually that'd be a good idea, since there's already validation at the
end of creating a complex feature (cleanEmptyElements).
It also checks for xlink:href there, so it should cover all our problems.
The problem is the
PM
To: Angreani, Rini (CESRE, Kensington)
Cc: Caradoc-Davies, Ben (CESRE, Kensington);
geotools-devel@lists.sourceforge.net
Subject: Re: [Geotools-devel] Mapping an optional element whose attributes are
not optional
On Tue, Oct 5, 2010 at 11:42 AM, rini.angre...@csiro.au wrote:
Yes actually
12 matches
Mail list logo
