>> I was thinking about this discussion of servlets and application servers
>> and taking into consideration that I know nothing about EJB, but have some
>> minor experience with an app server,...
>>
>> So I pose this question to my java compatriots with experience in other
>> realms of server side java. Why would I use an app server or some other
>> technology? What does EJB give me? Couldn't I use EJB with servlets as
>> opposed to an EJB centric appserver?
>
>In a nutshell (speaking as an "expert" who's read a few dozen more EJB
>documentation pages than you have :-), EJB is good for centralizing your
beans
>on large, high-capacity server(s) that offer the sort of performance,
>scalability, and reliability you need in an enterprise. The beans live,
>serverside, in containers that handle a lot of the plumbing issues -- so, for
>example, the beans can implement the business logic and let the container
worry
>about how to connect to databases. You connect to beans from the client side
>with ordinary RMI calls.
>
As another "expert" who's working for a company doing a LOT of development
based on EJBeans, I'd say the above is correct, to a degree. I believe that
the EJB community isn't quite yet sure what they've created, and are still
fishing for the patterns they need to do efficient, effective EJB
development. (My opinion is that EJBs and its
bean-managed-persistence/container-managed-persistence is fundamentally
flawed and will be the most highly rewritten part of the EJB spec over time.)
Think "web server for generic applications" and you're not too far off the
mark. Yes you can put your business logic into beans, but it doesn't have
to be, and in fact may not want it to be there, depending on scalability
desires.
I'm not an expert; I don't think ANYBODY is with something this new.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
