I'm not too sure what I'm taking about here which is why I'm putting it out to
the list for feedback rather than raising a jira issue. My understanding was
that Dspace provided transactional processing by setting the database
connection to auto-commit=false and doing a 'commit' once all processing had
completed successfully. However, Manakin has a filter called
DSpaceCocoonServletFilter which contains the following code that runs after the
request has been passed on for further processing...
// Close out the DSpace context no matter what.
ContextUtil.closeContext(realRequest);
This appears to run, commiting changes to the database, even if an Exception is
thrown in the main code.
Am I missing something here ? Any guidance would be appreciated.
Cheers, Robin.
Robin Taylor
Main Library
University of Edinburgh
Tel. 0131 6513808
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
