On Fri, Oct 8, 2010 at 9:03 AM, Niels 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 time I had available in
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, wrote:
Yes actually that
2010 5:55 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, wrote:
> Yes actually that
On Tue, Oct 5, 2010 at 11:42 AM, 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 validation is called in
ngton)
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:13 AM, wrote:
> OK Victor pointed out that your attributes x and y have minOccurs = 0
On Tue, Oct 5, 2010 at 11:13 AM, 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 itself is nillable.
> Ho
vel] Mapping an optional element whose attributes are
not optional
On Tue, Oct 5, 2010 at 10:45 AM, 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 reall
On Tue, Oct 5, 2010 at 10:45 AM, 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 recycles
> the
en (CESRE, Kensington)
Sent: Tuesday, 5 October 2010 4:14 PM
To: Andrea Aime
Cc: Geotools-Devel list; Angreani, Rini (CESRE, Kensington)
Subject: Re: [Geotools-devel] Mapping an optional element whose attributes are
not optional
I think you want these:
http://docs.geoserver.org/latest/en/user/data/app-s
On Tue, Oct 5, 2010 at 10:13 AM, Ben Caradoc-Davies
wrote:
> 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
Thanks. I don't have
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 16:04,
Hi,
in my target schema I have this attribute:
As you can see the attribute is optional, but the x/y inside of it are not.
I made the following mapping
12 matches
Mail list logo
