Hi all,
I was having some problems deploying geoserver 1.4.x in tomcat and tracked the problem to the wkb4j jar. Its manifest file seems to contain some attributes that tomcat chokes on. Upon further investigation i saw that geoserver 1.3.x doesn't suffer from this problem because it used a "modified" version of the jar whose manifest does not contain said parameters.
So my question is there any reason why the geotools postgis module cant use the same jar? I ran all the tests with the modified jar and they pass.
-Justin
Justin Deoliveira wrote:
Hi all,
I was having some problems deploying geoserver 1.4.x in tomcat and tracked the problem to the wkb4j jar. Its manifest file seems to contain some attributes that tomcat chokes on. Upon further investigation i saw that geoserver 1.3.x doesn't suffer from this problem because it used a "modified" version of the jar whose manifest does not contain said parameters.
So my question is there any reason why the geotools postgis module cant use the same jar? I ran all the tests with the modified jar and they pass.
No, and I think it _should_ be using the modified jar. It contains a few needed fixes, and the maintainer of the wkb4j stuff has disappeared.
Chris
-Justin
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Chris Holmes
The Open Planning Project
thoughts at: http://cholmes.wordpress.com
No, and I think it _should_ be using the modified jar. It contains a
few needed fixes, and the maintainer of the wkb4j stuff has
disappeared.
JTS has a WKB parser in it (i think since 1.6) -- might be worth
switching to it as its actually being maintained. Check out JTS's "io"
package.
Apparently there is an Oracle SDO STRUCT parser in JTS 1.7 too.
And you MUST use the modified WKB4J jar -- the "offical WKB4J" converts
all your coordinates to floats (instead of keeping them as doubles).
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/