Is it possible to create a transaction that spans both Session and StatelessSession operations? obviously the operations would not occur concurrently.

can i manually fetch a connection from a C3P0 datasource (autocommit is false), then open a new Session using that connection, use it then open a StatelessSession using the same connection?

im guessing i would have to manually commit the connection and then close the Session and StatelessSession.

anyone have experience doing such a thing?

i have found the solution to this and posted it in the other related thread i had started here:

http://forum.hibernate.org/viewtopic.php?p=2388548#2388548

pretty interesting for anyone considering this Transaction that spans Session and StatelessSession pattern.

Who even knew it was a pattern?

Great info!

haha. well i coined that term myself. but im surprised no one had really brought this up before... mixing a Session and StatelessSession together.

all the examples i see of other people doing large batch operations with the StatelessSession API seem to be designed in a non-atomic way (for example, demarcating transaction boundaries around each JDBC batch rather than around the entire batch.

my main use case didnt seem all that uncommon. im loading a bunch of records from files into a db, and i need to maintain a history of loaded files (modeled using more complicated objects that arent suitable for the StatelessSession). of course all changes to the information must be atomic in order to ensure that a system crash doesnt lead to synchronization problems.

anyways, i hope the topic was useful to someone in the future.