Chris Holmes wrote:
any ideas?
I think it is pretty clear - I have a bug!
I really need access to an oracle again 
And I wish that output had a line number for me, could we ask the user to turn on such?
Basically http://jira.codehaus.org/browse/GEOT-283 needs to be done and have MultiLineString vetted. I can also revisit the entire SDO class to take advantage of JTS 1.6 (given recent changes CoordinateAccess and CoordinateAccessFactory are no longer needed).
Jesse can you ping me on this when JTS1.6 is available?
Jody
This problem arises when i want to create a new entity. I select the Oracle Spatial table and request table spatial extension.
Here is when, in the "Start Geoserver" console appears: 839047 [FINA] org.geotools.data.oracle.attributeio.SDOAttributeIO - About to create Geometry convertor for DIS1_ELE_ACO
_DIS.OBJ
839063 [ADVERTENCIA] org.geotools.data.oracle.sdo.SDO - Could not create MultiLineString with INTERPRETATION 1 - we can
only represent 1 for straight edges
839063 [ADVERTENCIA] org.geotools.data.oracle.sdo.SDO - Could not create MultiLineString with INTERPRETATION 1 - we can
only represent 1 for straight edges
839063 [ADVERTENCIA] org.geotools.data.oracle.sdo.SDO - Could not create MultiLineString with INTERPRETATION 1 - we can
only represent 1 for straight edges
839063 [ADVERTENCIA] org.geotools.data.oracle.sdo.SDO - Could not create MultiLineString with INTERPRETATION 1 - we can
only represent 1 for straight edges
839063 [ADVERTENCIA] org.geotools.data.oracle.sdo.SDO - Could not create MultiLineString with INTERPRETATION 1 - we can
only represent 1 for straight edges
839063 [ADVERTENCIA] org.geotools.data.oracle.sdo.SDO - Could not create MultiLineString with INTERPRETATION 1 - we can
only represent 1 for straight edges....
.....and lower bounds are matched to: xmin 0
ymin 0
xmax -1 ¿?
ymas -1 ¿?