[Objectbridge-jdo-dev] Re: OJB - JDO Reference Enhancer

[Thomas M. <tho...@ho...>]

Hi Mika,

Mika Riekkinen wrote:

> Hi Thomas!
> I just read OJB plans about supporting JDO with OJB
> 2.0.


In fact we already have a working JDO prototype implementation !


> We are currently implementing JDO Enhancer as an open
> source project in sourceforge. It's in an very early
> stage, but we are confident about the implementation.
> 


great news!


> You may wish to take a look at it:
> http://sourceforge.net/projects/jadoe/

> 
> We have not set up any project home page or anything.
> Basically, what Jadoe does, is to make the enhancer
> part of the JDO specification. Currently we are
> implemeting this with bytecode manipulation.
> PersistenceCapable classes are created on the fly, as
> opposed to some precompiler.


cool.


> 
> We are going to support pre-compiled
> PersistenceCapable classes as well. The choice is left
> to user. Or JDO implementation.
> 
> Bytecode manipulation is done using Jiapi:
> http://sourceforge.net/projects/jiapi/
> 
> Jiapi provides high level bytecode manipulation
> capabilities.
> 


just curious: why do you use Jiapi instead of the defact-standard BCEL?


> 
> The status of jadoe is at alpha level. We have been
> succesfully been able to generate all the needed
> interfaces and methods. Some of the needed fields are
> allready generated, so we are almost there.
> There are some problems relating mostly to Jiapi, so
> we cannot finalize this Jadoe part. We will first fix
> these Jiapi related problems, and then it will take
> only a couple of weeks to finalize Jadoe.
> 


Mabe you should have a look at BCEL (to be found at JAKARTA)?


> We are looking for an opensource JDO implementation,
> so that we can plug Jadoe into it. ObjectBridge would
> be an ideal candidate for it.
> 


I agree. In our current JDO prototype we are using the enhancer from the 
JDORI. We would be happy to replace this with an opensource solution ASAP!


> I read your mailing lists, and someone pointed
> correctly out, that these two entities can be
> developed individually from each other.


ACK!


> If you think, that Jadoe would suit your needs for the
> Reference Enhancer, we are happy to merge our codebase
> to yours. 


As OJB will move to Jakarta soon (we have been as a Jakarta Toplevel 
subproject) there would be a lot of interest for your tool!

> Or if you would prefer a more pluggable RE
> scheme, we can help you defining these Reference
> Enhancer plugin mechanisms.
> 


We will need further discussions if there are special enhancement 
requirements for OJB. I'm not sure about it yet!

What exactly is your enhancer doing? is it generating the same things as 
the JDORI enhancer?
If so we can easily kickout the JDORI enhancer and plugin JADOE!

cheers,

Thomas

Mika: