Patrick Linskey-2 wrote: > >> How hard is it to add a reflection/cglib type alternative to the upfront >> bytecode generation (like hibernate does) to save us from the >> development-time pain? > > Not particularly hard. There are a few APIs that would break for some > cases, but it's even pretty straightforward to do a subclassing > approach for property-based access type without losing much > performance -- the only cost in that configuration is with > persistent-new instances. > > -Patrick > Awesome - can't wait for it to be supported :) Should I raise a JIRA? -- James ------- http://macstrac.blogspot.com/ -- View this message in context: http://www.nabble.com/the-pain-of-post-processing-bytecode-%28another-beg-for-a-simple-reflection-cglib-alternative-like-hibernate%29-tf3770760.html#a10723139 Sent from the open-jpa-dev mailing list archive at Nabble.com.
- Re: the pain of post processing bytecode (anot... Michael Dick
- Re: the pain of post processing bytecode (another beg f... Patrick Linskey
- Re: the pain of post processing bytecode (another ... Marc Prud'hommeaux
- Re: the pain of post processing bytecode (anot... David Ezzio
- Re: the pain of post processing bytecode (... Marc Prud'hommeaux
- Re: the pain of post processing byteco... David Ezzio
- RE: the pain of post processing b... Phill Moran
- Re: the pain of post processi... Craig L Russell
- Re: the pain of post processing bytecode (anot... James.Strachan
- Re: the pain of post processing bytecode (... Marc Prud'hommeaux
- Re: the pain of post processing bytecode (another ... James.Strachan
- Re: the pain of post processing bytecode (another beg f... David Jencks
- Re: the pain of post processing bytecode (another ... James.Strachan
- Re: the pain of post processing bytecode (anot... Patrick Linskey