Posted by jtuchel on May 11, 2011; 12:04pm
URL: https://forum.world.st/Rolling-back-twice-tp3514457p3514495.html

There's one little question for extra points here:

in search for a place in our web framework where I could register: the "main" object to be handled in a component, I came to the problem that some of our components handle a "model object" that is not to be persisted in the DB and therefor not an instance of one of the classes that the GLORP descriptor describes.

Now in order to avoid problems, I would first check with the descriptor that an object is really to be handled by GLORP, but I was just wondering if that shouldn't be done by ObjectTransaction>>#register: anyways. It sure sounds cool that GLORP can (theoretically) rollback any object, but on the other hand it is likely the user will get an exception at #commit time if an object is not in the descriptor system...

Or maybe the check I'm asking for is in current versions of GLORP anyways?

Joachim

--
You received this message because you are subscribed to the Google Groups "glorp-group" group.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/glorp-group?hl=en.