Hani Suleiman wrote:
Well, we're not talking about writing a tx system here, just providing the calls to begin/commit/rollback. And that's definitely a good idea to put here, especially if you're doing a straight servlets/db application, i.e. no EJB's to do the tx demarcation. And even if you *do* use EJB, sometimes it's better to do tx demarcation at this level instead of introducing a new session bean just to be able to do tx mgmt for a set of operations.I have to say, I really do think that adding tx on this level is a bad idea. For one thing, webwork is NOT a tx system, whatever it talks to should provide whatever tx support you require. Reinventing the wheel by handling the tx on this level seems....a waste of effort (vendors have already spent years getting their tx impls to work very nicely).
To my mind (I'll admit I didnt read all the previous emails about interceptorsAnd also *do* stuff.
in great detail, so I might be repeating old/known/wrong stuff), interceptors
are pretty much like filters. An interceptor would choose what to intercept,
then have access to context and whatnot to adds its own stuff.
I think Pat's example of a tx interceptor was great, and I think many people who are using WebWork (me included) think it's a good idea to have it.
/Rickard
--
Rickard Öberg
[EMAIL PROTECTED]
Senselogic
Got blog? I do. http://dreambean.com
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
