tag:blogger.com,1999:blog-637417304187784899.post3268013330442450948..comments2024-01-04T09:04:42.121+00:00Comments on James Strachan's Blog: OpenJPA no longer requires mandatory bytecode postprocessingJames Strachanhttp://www.blogger.com/profile/12591119339035350067noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-637417304187784899.post-37197780688418610642007-08-03T07:57:00.000+00:002007-08-03T07:57:00.000+00:00As it turns out, OpenJPA has supported runtime byt...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.<BR/><BR/>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.<BR/><BR/>-PatrickPatrick Linskeyhttps://www.blogger.com/profile/15619761689277098184noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-77848271122427352892007-07-31T08:44:00.000+00:002007-07-31T08:44:00.000+00:00No pun intended, but what are the priorities of th...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.Anonymoushttps://www.blogger.com/profile/02874466783900738920noreply@blogger.com