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?
I would agree that this would be limiting.
We almost always have transactional and non transactional methods on a given
session or entity bean. In sessions, writers are marked _required_, and
readers are marked _supports_. In entities, writers get _mandatory_, and
readers get _supports_.
There may be a few cases where we just mark it at the bean level and leave it,
but I can't think of any right now.
-Kevin
===========================================================================
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".
