Hi Marcus,

I could recreate the invalid xlink:href problems without joining.
With joining, I couldn't recreate the problem. It would be faster with joining 
too.
I guess it's about time I make joining the default behaviour.
Also, I think the problem with your filters should be solved with joining.
Please let me know otherwise.

To enable joining, add this line in app-schema.properties file: 
app-schema.joining = true

Cheers
Rini

-----Original Message-----
From: Angreani, Rini (CESRE, Kensington) 
Sent: Tuesday, 5 March 2013 5:01 PM
To: 'Sen, Marcus A.'; Caradoc-Davies, Ben (CESRE, Kensington)
Cc: geoserver-users@lists.sourceforge.net
Subject: RE: [Geoserver-users] Some GeoServer 2.3.x app-schema GeoSciML v3 (GML 
3.2 application schema) tests

Hi Marcus,

Sorry for the late reply. That one seems like a bug too, but probably related 
to the xlink:href bug since it makes the output corrupted with invalid 
xlink:hrefs.
Before I go on to investigate, can you tell me if you're using joining? 

Cheers
Rini

-----Original Message-----
From: Sen, Marcus A. [mailto:m...@bgs.ac.uk]
Sent: Tuesday, 26 February 2013 6:16 PM
To: Angreani, Rini (CESRE, Kensington); Caradoc-Davies, Ben (CESRE, Kensington)
Cc: geoserver-users@lists.sourceforge.net
Subject: RE: [Geoserver-users] Some GeoServer 2.3.x app-schema GeoSciML v3 (GML 
3.2 application schema) tests

> -----Original Message-----
> From: rini.angre...@csiro.au [mailto:rini.angre...@csiro.au]
> Sent: 26 February 2013 03:11

> Re: filtering. ValueReference is not implemented in app-schema. WFS
> 1.1.0 uses PropertyName, which is supported.
> WFS 2.0 specific syntax are not supported in app-schema yet (paging, 
> resolveDepth, some filters etc.).
...
> For now, I wouldn't recommend using WFS 2.0 with app-schema unless 
> using common WFS 1.1.0 operations and syntax.
The example query using WFS/FES 1.1.0 and PropertyName querying on

gsml:relatedFeature/gsmlga:GeologicHistory/gsml:relatedFeature/
gsmlga:GeologicEvent/gsmlga:eventEnvironment/swe:Category/swe:label

from my previous email which incorrectly returned all features should therefore 
still be registered as a bug I presume?

Marcus


This message (and any attachments) is for the recipient only. NERC is subject 
to the Freedom of Information Act 2000 and the contents of this email and any 
reply you make may be disclosed by NERC unless it is exempt from release under 
the Act. Any material supplied to NERC may be stored in an electronic records 
management system.
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to