Bernd Resch ha scritto:
Hey,
...
two exceptions here:
java.lang.NullPointerException: null
java.lang.NullPointerException
at java.io.FileInputStream.<init>(Unknown Source)
at org.vfny.geoserver.global.xml.XMLConfigReader.loadServices(XMLConfigReader.java:254)
This one can occurr if you're pointing geoserver to a directory
that's not a data directory (does not contain the services.xml file)
15.01.2008 18:36:28 org.vfny.geoserver.jetty.Start main
SCHWERWIEGEND: Could not start the Jetty server: Address already in use: JVM_Bind
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
Well, this one occurrs if there is already another app using the same port Jetty is trying to bind to (usually 8080). It's either another instance of Jetty, but I've noticed Oracle Express grabs it on startup
as well.
Cheers
Andrea
Hi Andrea,
thanks for your reply. I tried to set the GEOSERVER_DATA_DIR manually on my server, which is running GeoServer 1.6.0-beta4 on Tomcat 6.0.13.
The error, which is now thrown in the "FeatureType Editor", when I try to auto-generate the BBOX is:
The FeatureType 'UmweltparameterLuft' has a NULL extent.
HINT: the dataset is empty or has no default geometry attribute.
I didn't set a geometry attribute as it is not necessary. I have two columns in my data (longitude, latitude), which represent the geographical position. How can I make GeoServer notice this?
Thanks and best,
Bernd.
Andrea Aime wrote:
Bernd Resch ha scritto:
Hey,
...
two exceptions here:
java.lang.NullPointerException: null
java.lang.NullPointerException
at java.io.FileInputStream.<init>(Unknown Source)
at org.vfny.geoserver.global.xml.XMLConfigReader.loadServices(XMLConfigReader.java:254)
This one can occurr if you're pointing geoserver to a directory
that's not a data directory (does not contain the services.xml file)
15.01.2008 18:36:28 org.vfny.geoserver.jetty.Start main
SCHWERWIEGEND: Could not start the Jetty server: Address already in use: JVM_Bind
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
Well, this one occurrs if there is already another app using the same port Jetty is trying to bind to (usually 8080). It's either another instance of Jetty, but I've noticed Oracle Express grabs it on startup
as well.
Cheers
Andrea
Bernd Resch ha scritto:
Hi Andrea,
thanks for your reply. I tried to set the GEOSERVER_DATA_DIR manually on my server, which is running GeoServer 1.6.0-beta4 on Tomcat 6.0.13.
The error, which is now thrown in the "FeatureType Editor", when I try to auto-generate the BBOX is:
The FeatureType 'UmweltparameterLuft' has a NULL extent.
HINT: the dataset is empty or has no default geometry attribute.
I didn't set a geometry attribute as it is not necessary. I have two columns in my data (longitude, latitude), which represent the geographical position. How can I make GeoServer notice this?
GeoServer cannot figure out the two columns have a geographic meaning,
your datastore has to. You need to alter it so that the two columns
are used to create a JTS Point geometry that will be stored in the
feature type and in the features.
Chers
Andrea
Hello,
I finally managed to integrate my SWE O&M datastore into GeoServer. Thanks a lot for your precious feedback!
However, there's a last problem, which I can't really overlook as it probably requires deeper insight in GeoServer's interior processes. After having successfully executed GetCapabilities and DescribeFeature requests, I tried to send a GetFeature request. This one returned all features, but only showed the geom attribute, i.e. no other attributes were returned. All other attributes are shown automatically when creating the datastore in the "FeatureType Editor".
In a Java test application I wrote (create datastore -> getFeatureReader -> next() -> getAttribute()), everything works fine, each of the attributes is returned.
Any help would be appreciated!
Bernd.
Andrea Aime wrote:
Bernd Resch ha scritto:
Hi Andrea,
thanks for your reply. I tried to set the GEOSERVER_DATA_DIR manually on my server, which is running GeoServer 1.6.0-beta4 on Tomcat 6.0.13.
The error, which is now thrown in the "FeatureType Editor", when I try to auto-generate the BBOX is:
The FeatureType 'UmweltparameterLuft' has a NULL extent.
HINT: the dataset is empty or has no default geometry attribute.
I didn't set a geometry attribute as it is not necessary. I have two columns in my data (longitude, latitude), which represent the geographical position. How can I make GeoServer notice this?
GeoServer cannot figure out the two columns have a geographic meaning,
your datastore has to. You need to alter it so that the two columns
are used to create a JTS Point geometry that will be stored in the
feature type and in the features.
Chers
Andrea