Hi,
I'm suffering two problems to cascade WFS datastore, as described in the
follow:
I tested it using both GeoServer 1.3.0 and 1.3.1beta, with the
geoserver-1.3.0-wfs-ext plugin. Problem 1. When adding the GeoServer itself
(the GeoServer on the local machine) as a WFS datastore, it worked fine. But
when after createing a new feature from the new-added WFS datastore, it
cannot be saved and get the java exception like
"...java.lang.NullPointerException".
Problem 2, even worse, when trying to add some WFS not on the local machine
(e.g.
http://www2.dmsolutions.ca/cgi-bin/mswfs_gmap?version=1.0.0&request=getcapab
ilities&service=wfs, you can always access this link), it get error message
saying "connection time out".
Have already searched on the mail archive without any solution. Any one has
the same problem? Any suggestion? Thanks.~~~~
Cheers,
Jack
ITEE, Uni of Queensland
Mr. Jack,Fan ZHANG wrote:
Hi,
I'm suffering two problems to cascade WFS datastore, as described in the
follow:
I tested it using both GeoServer 1.3.0 and 1.3.1beta, with the
geoserver-1.3.0-wfs-ext plugin. Problem 1. When adding the GeoServer itself
(the GeoServer on the local machine) as a WFS datastore, it worked fine. But
when after createing a new feature from the new-added WFS datastore, it
cannot be saved and get the java exception like
"...java.lang.NullPointerException".
Can you get a better stack trace? Like by looking at the logs?
Problem 2, even worse, when trying to add some WFS not on the local machine
(e.g.
http://www2.dmsolutions.ca/cgi-bin/mswfs_gmap?version=1.0.0&request=getcapabilities&service=wfs, you can always access this link), it get error message
saying "connection time out".
Hmmm... I managed to get that loading without a connection time. Though I get another odd error that I can't figure out. No error really shows up, but it doesn't go past 'submit' on the feature type, though it does generate the proper bounding box. Unfortunately WFS datastore isn't really supported yet, it's still in beta, and I don't have the time to debug it. If you figure anything out do let us know. Note that GeoServer 1.3.0 uses geotools 2.1.x and 1.3.1beta uses 2.2.x, so get your WFS datastores from the appropriate places.
best regards,
Chris
Have already searched on the mail archive without any solution. Any one has
the same problem? Any suggestion? Thanks.~~~~
Cheers,
Jack
ITEE, Uni of Queensland
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org