No, of course not. Transactions are just a good base case because they are a
type of interceptor that works on both sides of the action (before and
after) and behavior can change based on possible configurations, changes in
the action contex, etc.

-Pat

----- Original Message -----
From: "Hani Suleiman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 10, 2003 2:37 AM
Subject: Re: [OS-webwork] XWork Interceptors


> Quoting Rickard Öberg <[EMAIL PROTECTED]>:
>
> > 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.
> >
> Sure, however, please do keep in mind that many people do choose to use
EJB's
> for the tx stuff. Session beans really are great for that kind of thing. I
> realise that you and others have much against EJBs, and that's fair
enough, but
> I was just voicing the sentiment that I don't want xwork to become a
framework
> that aims to replace EJBs.
>
> Hani
>
>
>
>
> -------------------------------------------------------
> 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



-------------------------------------------------------
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

Reply via email to