Re: Making transaction calls act like a Java method call would

Klaus,
Do you believe this should be an option in Prevayler? As a beginner I
was expecting direct transactions and having to beware of Prevayler's
recoverability requirements. I actually find this simpler, although
now I know it does carry more risk with respect to recoverability. I'd
probably use that app-wide "recoverability checker" mode, if it
existed, along with it, during development.

I've made a version which takes
prevaylerFactory.configureDeserializeThenExecute(false);
to make it behave this way.
Alternatively, to use deserialize-then-execute behaviour, you simply
do nothing (as it's default).

Having said that, I'd prefer Java-method-like behaviour as default,
only because I'm accustomed to the behaviour of Java methods and don't
have to think about Prevayler transactions behaving any differently.
1. Do you think it should be an option? 2. If so, should
deserialize-then-execute be the default or Java-method-like behaviour?
2b. If not, there are riskier options already offered as options, like
transient prevayler, and removing transaction filtering, so I would
wonder why not? Also, someone (maybe yourself) wrote: "//TODO
Optimizations ... 2) Make the baptism fail-fast feature optional
(default is on). If it is off, the given transaction can be used
instead of deserializing a new one from the byte array.", so it seems
to have been intended all along.

P.S. I can deliver this along with removing the "Serializable"
requirement as you requested in another thread.

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org