Hi!
I'm setting tx attributes on the method level. Most often it is to distinguish
between methods that are to be runned within a tx and methods, like getter that
doesn't need a tx. Why? My thought was that the container would have lesser
overhead when running these no-tx methods. I also have one EJB entity component
that when created always have to have the tx commited, but the rest of the
method may be called within an ongoing tx. So i think there is a need to be
able to specify tx on the method level.

Other thoughts!?
/Lennart

Rickard �berg wrote:

> Hey
>
> I think I'm going crazy. I'm currently looking into COM+, and it seems
> you can only set transactional attributes on a per component basis. In
> EJB you can set these on the method level.
>
> IMHO this is extremely limiting. So, I was wondering, does people use
> the possibility to have different tx settings on different methods in
> the same method, or do you only use them on a component level?
>
> If it is indeed a good thing to be able to set these per method, then
> the only workaround in COM+ would be to have one(1) method per
> component. Which would be completely ridiculous...
>
> Help me out here... what am I missing!?!
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> Homepage: http://www-und.ida.liu.se/~ricob684
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST".  For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".

--
________________________________
Lennart Petersson
Benefit AB
Bergendorffsgatan 5A
S-652 24 Karlstad
Phone: +46 (0)54 177253
mailto:[EMAIL PROTECTED]
Yahoo! Messenger, my nickname is: bit_av_en_kaka
http://www.benefit.se

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to