Monday 30 July 2007

OpenJPA no longer requires mandatory bytecode postprocessing

See OpenJPA no longer requires bytecode processing from Patrick.

Awesome! This makes it pretty trivial to switch Hibernate <-> OpenJPA


Unknown said...

No pun intended, but what are the priorities of the OpenJPA team if they still hadn't included bytecode modification at runtime? I don't use bytecode postprocessing since JBoss 2.4.

Patrick Linskey said...

As it turns out, OpenJPA has supported runtime bytecode modification for a while now. The problem is that it requires specification of a javaagent, since when doing so it needs to translate classes as they're loaded.

The new feature allows direct usage of classes without load-time redefinition, and automatically gracefully steps down to a lower QoS level depending on the execution environment.