Home/ Questions/Q 7942433
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T23:58:09+00:00

For a project I’m working on, i’m adding import/export functionality. This is working OK,

  • 0

For a project I’m working on, i’m adding import/export functionality. This is working OK, no issues.

What I’m trying to do now, is to have an option called “dryRun” which allows the user to test the import before actually doing anything, and just give an report back.

So, my setup is:

  1. Getting the import data through spring mvc (with OpenSessionInView)
  2. Deserialize this into my domain classes (which are the actual mapped hibernate classes)
  3. Scan through everything and make sure that references etc are ok.
  4. All my services have a @Transactional around them

This is mostly OK, but somewhere.. a save is triggered (i never call save), and my grouping object is complaining about a transient reference.. which is correct, since it is not saved.. I assume this is some kind of default mode hibernate has, since the grouping object references another object that is mapped.. So how can I make sure that hibernate never saves anything? without removing the @Transactional and OpenSessionInView (which is needed for the normal case)

Any ideas?

Regards,
Morten

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You say

    somewhere.. a save is triggered

    That “somewhere” is in the stack trace which you get with the exception.

    [EDIT] The stack trace basically says “the method MetaDataController.importXml() is annotated with @Transactional”. When it returns, Hibernate tries to commit the transaction as it should and then, it stumbles over an unsaved dependency in OrganisationUnitGroup (and yes, it would be nice if it would say which field contains the dependency because Hibernate knows this, too).

    There are several solutions:

    1. Create two methods to import. The new one, .importXmlDryRun() must not have the @Transactional annotation. That might work but my gut feeling warns me about problems even though I couldn’t name them right now.

    2. Throw an exception in .importXml() to abort the transaction when dry run is requested and ignore this exception in the default handler. The exception will cause Hibernate to roll back. This is the safest solution.

    3. Get the hibernate session and call clear() (docs)

    • 0