>Javier Borrajo wrote:
>> Should you get yourself a workflow management system (WMS) such as
>> IBM MQSeries Workflow or SUN Forte?
>
>For heavyweight parallel tasks, sure. For lightweight parallel tasks,
>no. That's overkill. Just give me a decent threading API so that if I
>decide to multithread my session bean I can.
Then maybe implement a multithreaded service that talks to the EJB session
bean ?
RMI, CORBA or servlet.
It's either that or wait for EJB 2.0, or use some propietary JMS-EJB mix
such
as Egipt, Voyager AppServer, WebLogic, ...
Regards
Javier
>> Maybe EJB should be used for things it is meant for such as OLTP, not for
>> things it is not, such as workflow etc.
>
>But session beans (particularly stateless ones) *are* meant for
>workflow. Not *all* workflow--i.e. there are some processes that can
>take months to occur; no transaction monitor is going to block waiting
>for them; that would be silly. But there are other processes which take
>a matter of seconds where it would be nice to have multithreaded code.
>
>> You can develop OLTP apps with EJB and then link them up using the WMS.
>> WMS are very sophisticated systems that are designed to deal with
>> issues such as parallelism, long-lived transactions, compensation
actions,
>> etc.
>
>Right, so what do I do if I want to deal with parallelism in
>NON-sophisticated systems? In regular Java, I just create the Threads
>myself. In EJB I have to do this in the client, which of course means
>that I'm not using session beans to do this, which, IMHO, I should be,
>all things being equal.
>
>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".
