Re: [Geoserver-devel] Storing VirtualTable inside the FeatureTypeInfo XML

Justin Deoliveira ha scritto: > On 10-05-28 10:25 AM, Andrea Aime wrote: >> Andrea Aime ha scritto: >>> The idea of grafting a jdbc specific bit in the FeatureTypeInfo >>> interface does not really make me jump of joy. Alternatives? >>> Extending the brief map converter to support complex objects a

Re: [Geoserver-devel] Storing VirtualTable inside the FeatureTypeInfo XML

On 10-05-28 10:25 AM, Andrea Aime wrote: > Andrea Aime ha scritto: >> The idea of grafting a jdbc specific bit in the FeatureTypeInfo >> interface does not really make me jump of joy. Alternatives? >> Extending the brief map converter to support complex objects as >> values I guess, which kind of s

Re: [Geoserver-devel] Documentation guide?

Actually, even though it's not 100% correct, I thought it would be less confusing and more visible to put it with the top links. But it's easy to move around, so please suggest away. http://docs.geoserver.org Thanks, Mike Pumphrey OpenGeo - http://opengeo.org On 5/27/2010 10:40 PM, Ben Carad

[Geoserver-devel] [jira] Created: (GEOS-3989) Add support for Postgis 1.5 geography columns

Add support for Postgis 1.5 geography columns - Key: GEOS-3989 URL: http://jira.codehaus.org/browse/GEOS-3989 Project: GeoServer Issue Type: Improvement Components: PostGIS Re

Re: [Geoserver-devel] Storing VirtualTable inside the FeatureTypeInfo XML

Andrea Aime ha scritto: > The idea of grafting a jdbc specific bit in the FeatureTypeInfo > interface does not really make me jump of joy. Alternatives? > Extending the brief map converter to support complex objects as > values I guess, which kind of seems to invalidating the reason > to have a br

[Geoserver-devel] Storing VirtualTable inside the FeatureTypeInfo XML

Hi, I'm trying to store a VirtualTable object (for the sql view stuff) in the MetadataMap, everything appears to be working in memory, but when I try to save, I get this: false org.geotools.jdbc.virtualta...@3fd372cf Looked in the brief map converter and noticed it assumes the ma

Re: [Geoserver-devel] Switching GeoServer to ECQL?

On Friday 28 May 2010 12:20:03 pm Jody Garnett wrote: > Interesting problem: > - My technical direction was to be strict superset of CQL, so although I > think it looks funny, the solution of id{'fid1','fid2','fid3'} is a strict > superset. (sigh). > > However: even CQL has the problem of a confli

Re: [Geoserver-devel] Switching GeoServer to ECQL?

Interesting problem: - My technical direction was to be strict superset of CQL, so although I think it looks funny, the solution of id{'fid1','fid2','fid3'} is a strict superset. (sigh). However: even CQL has the problem of a conflict between keywords and property name references; ie cannot hav

[Geoserver-devel] [jira] Created: (GEOS-3988) Feature type reload warning dialog fails to display properly

Feature type reload warning dialog fails to display properly Key: GEOS-3988 URL: http://jira.codehaus.org/browse/GEOS-3988 Project: GeoServer Issue Type: Bug Affects Versions:

[Geoserver-devel] [jira] Created: (GEOS-3987) Clearing resource cache after adding a new store results in a NPE

Clearing resource cache after adding a new store results in a NPE - Key: GEOS-3987 URL: http://jira.codehaus.org/browse/GEOS-3987 Project: GeoServer Issue Type: Bug

[Geoserver-devel] Build failed in Hudson: geoserver-2.0.x-nightly #215

See -- [...truncated 325 lines...] [INFO] [compiler:compile] [INFO] Compiling 235 source files to