SO all you can do for the moment is to wait for our own full JDO
implementation that will not have such limitations.
So when does this start?
In fact it has already started. Have a look at the folder
src/java/org/apache/ojb/jdo in the source distribution.
This new implementation is a thin layer on top of the OTM API.
SOme things are still missing:
1. a JDOQL Parser
2. a bytecode enhancer
3. an extension to the repositoryPersistor that allows to use a .JDO file
instead of a repository.xml
Cool. I'll peek at it some time, like maybe tonight or next weekend....
1 and 3 look interesting. I know nothing about bytecode however... What
about an xdoclet based source code enhancer as an additional option?
what java version compatability do you need to maintain for ojb stuff?
Do you have a developer doc that has all those details somewhere? I hope
it's not 1.1, I hate working with enumerations :).
Will it use the current JDO related
classes or
rewrite them?
It will be a complete rewrite, as we won't rely on the JDORI any longer...
ok so the migration from the jdori based stuff to the native stuff will
probably not be trivial then... I hope the jdori based version will be
maintained for those who are using it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
