>> Then maybe implement a multithreaded service that talks to the EJB
session
>> bean ?
>
>Right, which is a job that a session bean SHOULD be able to do, IMHO.
<very-long-and-interesting-post />
>IMHO you've just been forced to write a session bean, but without any of
>the transaction/security perks. That's silly.
>
>Nothing here is unworkable; it's just inconvenient, that's all. A
>well-designed API makes things more convenient, not less.
I agree with everything you say, but it would be better you get
somebody like Scott McNealy agree with this too ;-)
EJB 1.x are meant for OLTP, not for workflow, neither for a few more things.
Regards
Javier
===========================================================================
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".
