Hi,
No, that's not totally correct. Geoserver works fine with Oracle spatial for WMS and non-transactional WFS. The Oracle driver in Geoserver is reliable and fast. In our environment and use it is quite a lot faster (perhaps 40%) than UMN MapServer which is not especially slow either.
However, there are problems with Oracle spatial if you need to play with different projections because Oracle is sadly using its own SRID codes and neither Oracle nor Geoserver can translate between them and EPSG codes automatically. At least this was the case before Oracle 10g service pack 2.
I have been able to read our Oracle spatial tables with Geoserver simply by defining no projection at all in the Oracle end, but giving the correct EPSG code for Geoserver FeatureType configuration. As I said, this way WMS and non-transactional WFS works fine. However, if you want to make transactions then Geoserver WFS service is serving Oracle some EPSG codes within the SQL sentences. And because those are unknown to Oracle then transactions fail.
It would be extremely nice to get this problem solved in some way, either in Oracle of Geoserver side.
Regards,
-Jukka Rahkonen-
________________________________
Lähettäjä: geoserver-users-bounces@lists.sourceforge.net puolesta: Michael Ewing
Lähetetty: to 15.2.2007 1:10
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: Re: [Geoserver-users] GeoServer 1.4.0, Oracle Spatial doesn´t recognize geometry [Sec=Unclassified]
So, as far as you say, GeoServer doesn´t work out with Oracle Spatial?
In this post people say it works fine, does it depends on version?
If so, it would be very useful for everyone in this community knowing which
are the Oracle Spatial versions and platforms where it runs ok. (I use
PostGIS:-))
aaime wrote:
José Enrique Soriano Sevilla ha scritto:
Hello,
An extract of my geoserver.log:
org.geotools.referencing.operation.projection.NewZealandMapGrid$Provider
org.geotools.referencing.operation.projection.Krovak$Provider
14-feb-2007 12:54:49 org.geotools.data.oracle.OracleDataStore
getSDOGeometryAttribute
ADVERTENCIA: Could not map SRID 23030 to CRS:java.io.IOException: No CRS
for srid 23030
This happens because Oracle does not play well with standard.
The WKT definitions found in Oracle database do not conform to the OGC
specification, and as a result geotools cannot parse them (wrong syntax).
So far nobody stepped out to try and fix this, we would have to
make the geotools WKT parser accept the Oracle broken WKT as well,
or find a way to manipulate it before parsing so that it becomes
a valid one 
Cheers
Andrea
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
View this message in context: http://www.nabble.com/Re%3A-GeoServer-1.4.0%2C-Oracle-Spatial-doesn´t-recognize-geometry--Sec%3DUnclassified--tf3224234.html#a8976703
Sent from the GeoServer - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
