Andrew C. Oliver wrote:
>There are times when a scalable remoteable solution is necessary.
>Granted these are 1 in 100 projects, (or fewer). Secondly, EJB is
>purely a bad implementation of this.
>
Note how many good ones you're citing...
>I recommend we table this discussion, it has drawn on.
E/EJB,
etc. blows should be banned from this thread. These technologies are exactly
what this email group is about so obviously we like something about them. We
just want to share our work and make the technology better.
>From: "Andrew C. Oliver" Reply-To: "Jakarta General Li
Andrew,
>I recommend we table this discussion, it has drawn on. EJB/J2EE
>bitch-fest is not something that has a logical conclusion. I suggest
>participation in the design and development of AltiRMI and AJB (sp on
>both?)
>
Spelling corrections - AltRMI and EOB :-)
>is a more productive dis
There are times when a scalable remoteable solution is necessary.
Granted these are 1 in 100 projects, (or fewer). Secondly, EJB is
purely a bad implementation of this.
I recommend we table this discussion, it has drawn on. EJB/J2EE
bitch-fest is not something that has a logical conclusion. I
With EJB you complicate the deployment, slow down the performance and
save nothing except looking for middleware modules. Gee, I just don't
know where I'd find a connection pool or a logger or a single phase
transaction management system. Good thing I have Weblogic to save me so
much time. I'm
I think the biggest problem is with developers.
I've been involved with several EJB projects, and have watched many other
EJB projects from the side lines.
Many EJB projects are highly successful, and use the technology very
appropriately. In these cases EJBs were utilized correctly (in conj
