Chris Raber wrote:
> It's a good example, but for this sort of thing a work flow engine might be
> more appropriate anyway. If you find yourself hand coding direct graph
> execution, you're re-inventing the wheel. Check out www.verveinc.com.
<rant target="not at all chris personally">Oh good grief, if every time
I want to do three or four quick tasks in parallel I have to drag out a
workflow engine, I would go batty.</rant>
What I'm slowly beginning to grok is that session beans are NOT best
characterized as "extensions of the client", since the client, in fact,
is infinitely more powerful and reusable (can open files, can use
threads, can block on sockets, has support for full unbridled
inheritance, can do any damn thing it wants to). Session beans
(stateful or stateless) are merely--and I emphasize
merely--transactional wrappers. That's it. What hacks me off is that
they could be so much more.
{switches to decaf}
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".
