At the mo I don't have the code in front of me (on holiday at moment) but some part answers...

> Spring Declarative transactions...
I think Ebean does need to do something here. From memory my thoughts were that with Spring you'd use the standard spring jdbc transaction manager (rather than a Ebean specialised one) and Ebean could be configured to pick up the java.sql.Connection from the thread local that spring uses... and wrap them for use in Ebean.

I didn't get time to actually do it... but that was my initial plan/thought.

> query and sqlQuery serializable...
Yes, that should have been done. My mistake for missing that :(