Assaf Arkin wrote:
> Where does the specification imply you can use td?
It does not. I was hoping it did so that my group's work over the past year
would not now be destined for the trash heap. Alas.
> The ban on thread is not specific to the EJB class, it is specific to
> all the application code running inside the EJB container. That covers
> everything underneath the container (EJB, related classes, related
> libraries) and above the resource managers and connectors (JDBC, JMS,
> etc).
Right. So we just have to hope and pray that some of the third-party class files
we make calls to are not implemented by using Threads. Of course, we have no way
of knowing whether they are, since good &$!? object oriented programming style is
supposed to let you forget about this. If ThirdPartyProviderWidget.class uses
three threads to implement its frobnicate() method, I shouldn't have to care; I
just should care that frobnication takes place in a speedy and safe manner. Now,
if I want to call that method from within, say, a Session bean, I suddenly have
to violate every layer of encapsulation, call the vendor and ask them just how
many Thread.new() calls there are in their code. This is ridiculous.
Cheers,
Laird
===========================================================================
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".
