Is GID the feature id or primary key of the table by any chance? If it is then you will not be able to use it in the attribute filtering configuration since it is not used as an attribute.
Sean
From: Bronwyn Cook [mailto:bronwyn.cook@anonymised.com]
Sent: Monday, 19 January 2004 9:12 AM
To: ‘Geoghegan, Sean’
Cc: Geoserver List
Subject: RE: [Geoserver-devel] How do you limit exposed attributes for Oracle?
Sean:
I just tried capitalising the attributes (both in info.xml and schema.xml) but I still get the same error.
From: Geoghegan, Sean [mailto:Sean.Geoghegan@anonymised.com]
Sent: Friday, January 16, 2004 3:49 PM
To: ‘Bronwyn Cook’; Geoserver List
Subject: RE: [Geoserver-devel] How do you limit exposed attributes for Oracle?
Hi Bronwyn,
I haven’t seen this attribute filtering code before, but ahve you tried capitalising the attribute names? I think the oracle case issue also extends to column names.
Sean
From: Bronwyn Cook [mailto:bronwyn.cook@anonymised.com]
Sent: Friday, 16 January 2004 2:31 PM
To: Geoserver List
Subject: [Geoserver-devel] How do you limit exposed attributes for Oracle?
Hi,
I have got Geoserver 1.1 working successfully with an Oracle feature type however I can’t seem to limit the list of exposed attributes. As soon as I add in the attributes stuff to the info.xml file I get the following error when I restart the server:
org.vfny.geoserver.config.ConfigurationException: Error obtaining schema for top
p:QLDRSTN: the FeatureType topp:QLDRSTN does not contains the configured attribu
te gid. Check your catalog configuration
at org.vfny.geoserver.config.FeatureTypeConfig.(FeatureTypeConfig.
java:154)
at org.vfny.geoserver.config.CatalogConfig.loadFeatureTypes(CatalogConfi
g.java:539)
at org.vfny.geoserver.config.CatalogConfig.loadFeatureTypes(CatalogConfi
g.java:530)
at org.vfny.geoserver.config.CatalogConfig.loadFeatureTypes(CatalogConfi
g.java:530)
at org.vfny.geoserver.config.CatalogConfig.(CatalogConfig.java:207
)
at org.vfny.geoserver.config.ServerConfig.load(ServerConfig.java:310)
at org.vfny.geoserver.config.ServerConfig.(ServerConfig.java:88)
at org.vfny.geoserver.config.ServerConfig.load(ServerConfig.java:205)
at org.vfny.geoserver.servlets.FreefsLog.init(FreefsLog.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.
java:935)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:82
3)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex
t.java:3422)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3
623)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:821)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:80
7)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDep
loyer.java:307)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:788)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.j
ava:559)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:401
)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:718)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
:358)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:166)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1196)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:754)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:363
)
at org.apache.catalina.core.StandardService.start(StandardService.java:4
97)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:219
0)
at org.apache.catalina.startup.Catalina.start(Catalina.java:512)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Caused by: org.vfny.geoserver.config.ConfigurationException: the FeatureType top
p:QLDRSTN does not contains the configured attribute gid. Check your catalog con
figuration
at org.vfny.geoserver.config.FeatureTypeConfig.getSchema(FeatureTypeConf
ig.java:510)
at org.vfny.geoserver.config.FeatureTypeConfig.(FeatureTypeConfig.
java:151)
… 37 more
3328 [WARNING] org.vfny.geoserver.config.CatalogConfig - could not add FeatureT
ype at C:\Program Files\jakarta-tomcat-4.1.29\webapps\geoserver110\data\featureT
ypes\QLDRSTN\info.xml due to org.vfny.geoserver.config.ConfigurationException: E
rror obtaining schema for topp:QLDRSTN: the FeatureType topp:QLDRSTN does not co
ntains the configured attribute gid. Check your catalog configuration
The attributes section of the info.xml file looks like:
If I comment out the attributes stuff then all works fine.
Cheers
Bronwyn
Bingo! That was it. I took the GID entry out of the attributes tag and it now the attribute filtering works fine.
This is what the attribute filtering section looks liek now:
Thanks
Bronwyn
From: geoserver-devel-admin@anonymised.comt [mailto:geoserver-devel-admin@lists.sourceforge.net] On Behalf Of Geoghegan, Sean
Sent: Monday, January 19, 2004 10:38 AM
To: ‘Bronwyn Cook’; Geoghegan, Sean
Cc: Geoserver List
Subject: RE: [Geoserver-devel] How do you limit exposed attributes for Oracle?
Is GID the feature id or primary key of the table by any chance? If it is then you will not be able to use it in the attribute filtering configuration since it is not used as an attribute.
Sean
From: Bronwyn Cook [mailto:bronwyn.cook@anonymised.com]
Sent: Monday, 19 January 2004 9:12 AM
To: ‘Geoghegan, Sean’
Cc: Geoserver List
Subject: RE: [Geoserver-devel] How do you limit exposed attributes for Oracle?
Sean:
I just tried capitalising the attributes (both in info.xml and schema.xml) but I still get the same error.
From: Geoghegan, Sean [mailto:Sean.Geoghegan@anonymised.com]
Sent: Friday, January 16, 2004 3:49 PM
To: ‘Bronwyn Cook’; Geoserver List
Subject: RE: [Geoserver-devel] How do you limit exposed attributes for Oracle?
Hi Bronwyn,
I haven’t seen this attribute filtering code before, but ahve you tried capitalising the attribute names? I think the oracle case issue also extends to column names.
Sean
From: Bronwyn Cook [mailto:bronwyn.cook@anonymised.com]
Sent: Friday, 16 January 2004 2:31 PM
To: Geoserver List
Subject: [Geoserver-devel] How do you limit exposed attributes for Oracle?
Hi,
I have got Geoserver 1.1 working successfully with an Oracle feature type however I can’t seem to limit the list of exposed attributes. As soon as I add in the attributes stuff to the info.xml file I get the following error when I restart the server:
org.vfny.geoserver.config.ConfigurationException: Error obtaining schema for top
p:QLDRSTN: the FeatureType topp:QLDRSTN does not contains the configured attribu
te gid. Check your catalog configuration
at org.vfny.geoserver.config.FeatureTypeConfig.(FeatureTypeConfig.
java:154)
at org.vfny.geoserver.config.CatalogConfig.loadFeatureTypes(CatalogConfi
g.java:539)
at org.vfny.geoserver.config.CatalogConfig.loadFeatureTypes(CatalogConfi
g.java:530)
at org.vfny.geoserver.config.CatalogConfig.loadFeatureTypes(CatalogConfi
g.java:530)
at org.vfny.geoserver.config.CatalogConfig.(CatalogConfig.java:207
)
at org.vfny.geoserver.config.ServerConfig.load(ServerConfig.java:310)
at org.vfny.geoserver.config.ServerConfig.(ServerConfig.java:88)
at org.vfny.geoserver.config.ServerConfig.load(ServerConfig.java:205)
at org.vfny.geoserver.servlets.FreefsLog.init(FreefsLog.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.
java:935)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:82
3)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex
t.java:3422)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3
623)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:821)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:80
7)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDep
loyer.java:307)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:788)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.j
ava:559)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:401
)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:718)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
:358)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:166)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1196)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:754)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:363
)
at org.apache.catalina.core.StandardService.start(StandardService.java:4
97)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:219
0)
at org.apache.catalina.startup.Catalina.start(Catalina.java:512)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Caused by: org.vfny.geoserver.config.ConfigurationException: the FeatureType top
p:QLDRSTN does not contains the configured attribute gid. Check your catalog con
figuration
at org.vfny.geoserver.config.FeatureTypeConfig.getSchema(FeatureTypeConf
ig.java:510)
at org.vfny.geoserver.config.FeatureTypeConfig.(FeatureTypeConfig.
java:151)
… 37 more
3328 [WARNING] org.vfny.geoserver.config.CatalogConfig - could not add FeatureT
ype at C:\Program Files\jakarta-tomcat-4.1.29\webapps\geoserver110\data\featureT
ypes\QLDRSTN\info.xml due to org.vfny.geoserver.config.ConfigurationException: E
rror obtaining schema for topp:QLDRSTN: the FeatureType topp:QLDRSTN does not co
ntains the configured attribute gid. Check your catalog configuration
The attributes section of the info.xml file looks like:
If I comment out the attributes stuff then all works fine.
Cheers
Bronwyn
I’m currently unable of updating my code tree from sf cvs repository with developer access. I’m getting
a connection refused error on port 22.
I was able of checking it out throug anonymouse pserver access.
Does anybody knows if it is actually a problem with SF CVS servers?
thanks,
gabriel