You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by oj...@db.apache.org on 2004/09/26 10:09:28 UTC
[DB OJB Wiki] Updated: OJBNextSteps
Date: 2004-09-26T01:09:27
Editor: JakobBraeuchi <jb...@gmx.ch>
Wiki: DB OJB Wiki
Page: OJBNextSteps
URL: http://wiki.apache.org/db-ojb/OJBNextSteps
no comment
Change Log:
------------------------------------------------------------------------------
@@ -113,6 +113,8 @@
* deprecation of 'extent-class' in favour of an extends attribute for the sub-class descriptor (i.e. more like Java, but without the separation into Class/Interface)
+ * full support mixing of mapping strategies. -- MixingMappingStrategies
+
= Goals for OJB 1.x =
* support for generics (Java 1.5) -- JavaGenerics
@@ -128,7 +130,7 @@
* clear separation of API and SPI parts. In the ATM we this already, having it in the other layers as well ease the maintenance process, as OJB developers we'll immediately see which parts can be changed without changing parts of the API. -- ApiSpiSeparation
- * full support mixing of mapping strategies. -- MixingMappingStrategies
+ * full support mixing of mapping strategies. -- MixingMappingStrategies (parts of it in OJB 1.1)
* i'm playing with oracle spatial at the moment ... not sure if there is a way to support stuff like this .. but it would be nice ;-) -- OracleSpatial
''[Martin Kalén] We (Curalia AB) have are back-end running in production that is reading and writing Oracle Spatial geometries using OJB (slightly-pre-)1.0 and OJB !RowReaders with Oralce Spatial converters for convertering the STRUCT data. In a way OJB already supports spatial since the STRUCT datatype is supported. I don't think that geospatial functionality should be handled by OJB, there are many other !OpenSource products handling this well.''
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org