> If something's badly architected, it's
> badly architected.
Before you go talking "badly architectured," I suggest
you get on a plane and go visit Ruben, sign a NDA, and
look at his stuff. Otherwise you're nothing but a
biget. And a poorly informed one, at that, to
paraphrase Marc's reply to you on a similar topic.
I believe that someone who maps Use Cases 1:1 to
Session Beans should be careful in pronouncing others
work as "bad." Why bother with use cases if you're
already thinking implementation? 8-)
If you read Ruben's recent post in reply to mine,
you'll see I hit the nail on the head.
> EJBs place particular
> constraints on how you should build your
> system (big is beautiful). Pedantic arguing
> isn't going to change the fact that EJB
> beans in general and entity beans in particular
> are very expensive for the appserver to
> manage - there is a significant overhead.
>
> Selling someone short, as you put it, would be
> to whitewash over the issues (perhaps you just
> don't understand them ?)
LOL! Get on a plane man!
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
