IWETHEY v. 0.3.0 | TODO
1,095 registered users | 1 active user | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New As I understand it, the problem EJBs tried to solve was

the need for server logic that could be isolated & thus made persistent if needed, but more importantly an EJB conformed to a standard design that supported getters setters *and* introspection.

A EJB container being the mechanism for managing the persistence of the beans.

AFAIR IBM's Hursley lab (of CICS fame) had a lot to do with the architecting & developement of EJB despite any dubious claims to the contrary from Sun. IBM were trying to bring some scalability to Java.

As a former strong proponent of Java, I find it has become so damned complex and has so many non-OOT exceptions to the rule, that I wonder why the world missed ST.

But such is life ...

Doug Marker

(Java was so digestable to former C programmers)
New EJB Complexity
Just the fact that you need a Home Interface for EJB's is ridiculous. It stems from the static typing and function calling orientation of Java. In a true message passing system these issues go away.
New The Home interface is the class interface
Since Java doesn't have real class objects, they found they had to put the class hierarchy back via the home mechanism. Its quite lame.



"Packed like lemmings into shiny metal boxes.
Contestants in a suicidal race."
    - Synchronicity II - The Police
     EJB's and classic OO theory - (bluke) - (5)
         Somewhat... - (admin)
         As I understand it, the problem EJBs tried to solve was - (dmarker) - (2)
             EJB Complexity - (bluke) - (1)
                 The Home interface is the class interface - (tuberculosis)
         Classic OO theory is fscked, modern OO is double fscked - (tablizer)

If there were bombs.
42 ms