Well this was just a quick fix. A need more thoughts need to go into it to leverage other proxying logic possibilities. We will do this in trunk I think. For now it's really nice to have it running on GAE again. And as calls to Unsafe are not allowed on GAE, I fear there is other way than newInstance() to create proxies.
Please note that we usually only will create a single instance of each proxy and cache it! So it does not hurt that heavily as one might think. LieGrue, strub > On Saturday, 22 November 2014, 0:39, PÉNET LUDOVIC <[email protected]> wrote: > > > Mark Struberg a écrit : >> Hi! >> >> Could you please checkout the latest branches/owb-1.2.x? >> >> I implemented some fallbacks which get used when running on GAE now. >> >> It basically boils down to not using Unsafe but newInstance() if we cannot >> get the allocate method from Unsafe. Of course this has some impact and >> might slow down your beans a bit, but it should work fine for now. > I tested it and it seems to work. Thanks ! > > However, it seems to me that the SPI approach that you suggested first is > better. For complex objects, running the constructor everytime might be > significant performance hit. The newInstance way could be another > selectable implementation... > > Thanks again, > > > Ludovic > > | > | AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT. > | >
