[snip]
>
> I bet Encina allows you to associate your threads with a transaction,
> and doesn't attempt to control their lifecycle.
Yes it does and does it quite efficiently and very elegantly.
> > It is hard to work with these restrictions, but as Sriram says
> in the other
> > post it should be documented as not a good idea for so and so reason and
> > left at that.
> It can be done, but it needs some additional APIs, way more specs and
> documentation.
>
> Complex issues like that tend to fail not when you develop the code and
> run it, but in production environment. And as they say, YMMV. I could be
> running an application using threads for years without a problem, give
> it to you, and ten days later it breaks.
This here treats the bean developers with a bit of contempt. Indicating that
the container/server developers/vendors will be better at managing the
thread lifecycle than the bean developers. While this may be mostly the
case, there are exceptions and it best for an architecture to be successful
to span the whole breadth of all possible development than to cater for
least common denominator.
>
> To avoid that you need very good documentation upfront.
>
> Also, once you add threads people will be asking for transactional
> control, security context and more features than the EJB 1.1 lacks.
>
Even if you can't document it and say you can't. There are certain portions
of an application that needs such parallel tasking features. Now, the
standard response to that would be that you should not do that using EJBs.
That is fine, but then I have a CIO breathing down my neck asking me why on
earth did we all invest in this programming model in the first place when it
can do this.
> So someone has to beat Sun on the head, say there are many people out
> there requesting these features, figure out how to make them work for
> 2.0.
>
I guess this will be a lost cause, as most people have been over this last
year and nothing much has happened.
-- Aravind
===========================================================================
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".
