Closed GoogleCodeExporter closed 9 years ago
um... forgot to say: now ch.lambdaj.function.argument.ArgumentsFactoryTest
fails obviously, because of this capability. It has of course to be adjusted
accordingly.
Original comment by google-a...@codesmell.de
on 7 Mar 2012 at 1:38
any progress/feedback on this?
Original comment by google-a...@codesmell.de
on 4 May 2012 at 7:32
From lambdaj 2.4 it is already possible to overcome this problem by providing a
custom strategy for placeholder creation as described here:
http://code.google.com/p/lambdaj/wiki/Lambdaj24ReleaseNotes
In general I want to limit the use of objenesis when possible because it is not
compatible with many environments like Android and Google App Engine.
I also just added allowed the ArgumentFactory to automatically create
placeholder even for final classes with a 2-args constructor like java.util.UUID
Original comment by mario.fu...@gmail.com
on 8 Jul 2012 at 10:52
Original issue reported on code.google.com by
google-a...@codesmell.de
on 7 Mar 2012 at 1:25Attachments: