Just found out the beta is no longer beta, PostgreSQL 9.0.0 has reached “release” status. Version 9 has native x64 Windows support, and per-column-triggers. Nice! Read the release notes for more information about the new version.
No info about a new version of PostGIS (yet).
The GeoServer team “released” GeoServer 2.1 beta, you can read about it on this page. Especially the WMS-cascading and SQL-layers sound very promising. But the icing on the cake perhaps are the WPS capabilities. I wonder if the commercial vendors are as enthusiastic about this release as I am…. 🙂
If you’re a happy GeoServer 1.7.x user, then seriously consider upgrading to GeoServer 2.0. It’s a lot faster, its menu structure is a lot better, the UI is much improved (with a touch of Ajax here and there). I found some minor issues (which I’m looking into before raising my voice), but nothing that should keep you from updating.
I run GeoServer in Oracle’s OC4J 10gR2 (the standalone development version), and it runs without any problems. Since the OC4J is declared dead, I will be looking into deploying it to Weblogic, but that’s a completely different monster to conquer…
Finally, it works. I found some new samples on the OpenLayers site and some posts in the mailinglist that OpenLayers.Layers.WFS just plainly sucks. Indeed, so I experienced. Instead the writer suggested to use OpenLayers.Layer.Vector and give it a type WFST. So I googled around for some samples, found one, modified it, and….voila….no more empty geometries in the database. YEAH!
Yesterday I installed JBoss 4.2.3 and deployed Geoserver 1.7.6 to it and installed the OracleNG plugin. Unfortunately, after setting up the Oracle datastore and some features, inserting via WFS-T still resulted in an empty geometry in the database.
SVN access to the OpenLayers trunk gives an error at the moment, so I guess I’ll have to do some further testing with the 2.0RC of Geoserver.
I tried Geoserver with Oracle 11g, and still I get empty geometries inserted into the database. With Firebug I can see that the GML sent is correct, it contains the correct geometry information (in this case: point coordinates), but the receiving end fucks it up. Not sure whether the OracleNG plugin for Geoserver or Openlayers does the fucking up, but I suspect it is the plugin.
Dear all,
I’ve been struggling with Geoserver and Oracle as a datastore. In a webpage that uses OpenLayers, I’m trying to use the WFS-T features. Don’t get me wrong, WFS works great. That is, the read-only part. WFS-T works great with shape files. WFS-T works great with PostGIS. But the same page, same WFS-server (my local Geoserver) with Oracle as a datastore just inserts empty geometry columns (NULL). When making the geometry column “NOT NULL” Geoserver and/or OpenLayers just inserts a point with 0.0,0.0 as coordinates. Which is NOT where I clicked on the map (0.0,0.0 isn’t even close to being visible on screen).
So, anyone got WFS-T with an Oracle datastore working? I’m using Geoserver 1.7.5 on Tomcat 6.0.something (latest as of now), OracleNG plugin, OpenLayers 2.8 (local, not the hosted version). With Firebug I can see that the GML being sent in the POST command is CORRECT, i.e. it shows the correct coordinates. Somewhere along the line these are discarded and NULL or 0,0 (depending on the column definition) is inserted.
Change to PostGIS (with almost the same table definition, that’s the beauty of PostgreSQL) and everything works like a charm. PostGIS + Geoserver + OpenLayers is a killer combination!
Let the comments pour in……