Ok, I think I've solved this problem. I believe a bug was introduced
that
broke readCoords when some better handling of coordinate buffers was
added. I fixed it in geotools cvs, and updated the jars in geoserver
cvs
on head and wms-merge.
Well, the coordinate reading does work now, but I get an exception from
the server now:
"Logisches Handle nicht mehr gültig" means something like "logical
handle no longer valid"
org.vfny.geoserver.responses.WfsTransactionException:
org.vfny.geoserver.responses.WfsTransactionException: Problem updating
features
: org.geotools.data.DataSourceException: Geometry Conversion error when
adding features: java.sql.SQLException: Logisches Handle nich
t mehr gültig cause: oracle.sdoapi.geom.InvalidGeometryException:
java.sql.SQLException: Logisches Handle nicht mehr gültig
at
org.vfny.geoserver.responses.TransactionResponse.getSub(TransactionRespo
nse.java:212)
at
org.vfny.geoserver.responses.TransactionResponse.getXmlResponse(Transact
ionResponse.java:105)
at
org.vfny.geoserver.servlets.Transaction.doPost(Transaction.java:65)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241
7)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa
lve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:78
1)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:549)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:58
9)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:666)
at java.lang.Thread.run(Thread.java:534)
Caused by: org.vfny.geoserver.responses.WfsTransactionException: Problem
updating features: org.geotools.data.DataSourceException: Ge
ometry Conversion error when adding features: java.sql.SQLException:
Logisches Handle nicht mehr gültig cause: oracle.sdoapi.geom.Inv
alidGeometryException: java.sql.SQLException: Logisches Handle nicht
mehr gültig
at
org.vfny.geoserver.responses.TransactionResponse.doInsert(TransactionRes
ponse.java:252)
at
org.vfny.geoserver.responses.TransactionResponse.getSub(TransactionRespo
nse.java:195)
... 33 more
Looking at the code, I think the Z coord should work with Oracle. It
does
not work with Postgis at this time however, as it communicates with
Well
Known Text (or Binary), and the well known stuff is fuzzy on the z
coordinate, so JTS just doesn't use it in its WKT reader/writer. When
we
move to WKB4J it may be easier to support, it looks like it deals with
3d
stuff a bit better.
Chris
On Wed, 10 Dec 2003, Simon Räss wrote:
> I cannot get inserts working. The features I receive on the server
side
> do not have any attributes. The attributes are somehow dropped along
the
> xml filter chain. It is (most likely) not a data source related
problem.
> I believe the source of problems lies in TransactionFeatureHandler.
>
> Any ideas what might cause this problem? Otherwise I will start to
debug
> the filter chain step by step and see where the attributes are
dropped
> (the received xml seems to be ok).
>
> An example of what I receive on server side:
> <?xml version="1.0" encoding="utf-16"?>
> <wfs:Transaction version="1.0.0" service="WFS"
> xmlns:wfs="http://www.opengis.net/wfs">
> <wfs:Insert handle="insert gps point">
> <RQS_POINT xmlns="http://www.someserver.com/myns">
> <GEOM>
> <Point xmlns="http://www.opengis.net/gml">
> <coord>
> <X>202238.869</X>
> <Y>604600.558</Y>
> <Z>578.672</Z>
> </coord>
> </Point>
> </GEOM>
> </RQS_POINT>
> </wfs:Insert>
> </wfs:Transaction>
>
> Another question: are optional attributes supported by the
> TransactionFeatureHandler? The above feature type could have some
more
> attributes but they are all optional (in short: the FeatureType has
a
> corresponding attribute for them, but the created feature does not).
> Does this cause any problems? I think I've glimpsed some potential
> problem areas, that's why I ask.
>
> Simon
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive? Does it
> help you create better code? SHARE THE LOVE, and help us help
> YOU! Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
--
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel