Comments on: An Easier Java ORM Part 3

By: Christian

Christian — Thu, 28 Feb 2008 07:21:51 +0000

Thanks for your fast Reply Daniel.
It is enough for me to know that its is a Beanshell problem.

By: Daniel Spiewak

Daniel Spiewak — Wed, 27 Feb 2008 18:21:27 +0000

I’m going to take a wild guess and say that it’s probably got something to do with the way that BeanShell creates dynamic proxies for objects and such. I honestly don’t know though (don’t use BeanShell very much).

By: Christian

Christian — Wed, 27 Feb 2008 18:17:15 +0000

Hello!

Do you have any idea why this do not work in beanshell?

bsh % new Transaction(fimi.Main.em){
public void run(){
null;
}
}.execute();
// Error: EvalError: Error constructing inner class instance: bsh.ReflectError: Can’t find constructor: global$2( net.java.ao.EntityManager ) in class: global$2 : at Line: 1 : in file: : new Transaction ( fimi .Main .em ) {

bsh %

The EntityManager should be OK:
bsh % print(fimi.Main.em.toString());
net.java.ao.EntityManager@16c9867
bsh %

Thank You
Christian

By: Daniel Spiewak

Daniel Spiewak — Fri, 27 Jul 2007 17:17:32 +0000

Ammentos is interesting, but it still relies upon the POJO model, Lists, etc… It doesn’t do migrations or schema generation, and it requires a *ton* of parameterized annotations to wire everything together. It’s kind of cool, but it seems like just an XML-less JPA.

By: Nicola Viragine

Nicola Viragine — Fri, 27 Jul 2007 13:52:09 +0000

Hi Daniel,

There is another interesting ORM framework called Ammentos:

http://ammentos.biobytes.it/

I find it very amazing..

thanks

Nicola

By: Daniel Spiewak

Daniel Spiewak — Fri, 27 Jul 2007 03:28:24 +0000

It’s fully available and working (as far as I can tell). I don’t have any applications which explicitly test to see if they’re working.

By: David Marko

David Marko — Thu, 26 Jul 2007 05:56:29 +0000

Is described transaction syntaxt already available in ActiveObject ot is it the proposal only?

Thanks
David