Re: Custom ClassLoader

On Fri, Jan 10, 2014 at 5:11 AM, Justin T. Sampson <[email protected]>wrote:

> Hi Christian,
>
> Oh, I see now what you mean about the the JavaSerializer hardcoded in the
> constructor. That does seem unfortunate. :) If you're comfortable modifying
> the Prevayler source and building it yourself, it should be pretty trivial
> to add the journal serializer as a constructor parameter.
>
Ja. Had this option running locally for some days - but that'd introduce a
hard dependency to "my" prevayler.jar ... which didn't feel right, either.
But if an official Prevayler 2.6.1 included a class loader aware
NullSnapshotManager ... ;-)

> Your VolatilePrevayler approach is certainly reasonable, though. I just
> have a couple of suggestions regarding the serializability checking:
>
> First, queries don't need to be serializable, so you can remove the check
> from there.
>
That means, in Querys you may reference domain objects? Removed the check
anyway.

> Second, it will be more realistic if you actually _use_ the deep copy of
> each transaction rather than throwing it away. That is, execute the
> deserialized copy rather than the original transaction object.
>
Thanks - using the deserialized object copy now.

Cheers,
Christian

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk

_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org