[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-general
Subject:    Re: EJB = bad = MS.net [People are stupid!]
From:       dIon Gillard <dion () multitask ! com ! au>
Date:       2002-02-25 5:43:52
[Download RAW message or body]

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.  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?) is a more productive discussion.  Slam EJB by getting something
>far better up on Jakarta.
>
Go for it....so far noone one the con side has provided any decent 
arguments about how/why EJBs are bad, just slamming WebLogic doesn't 
really make much of an argument.

>
>
>-Andy
>
>On Fri, 2002-02-22 at 23:22, Aaron Smuts wrote:
>
>>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 glad I only have to wait 5 minutes for the damn thing to
>>restart.
>>
>>I've migrated my current application out of EJB's (weblogic) because
>>they do nothing but slow down the application and the development life
>>cycle.  I don't like programming in xml and having to shutdown
>>production to make patches.  The appserver specific deployment files
>>make them unportable and vendor dependent.  Weblogic tries its best to
>>lock you into T3 and its deployment.
>>
>>For most modest transactional needs, you can out build and out perform
>>any appserver using the JDBC.
>>
>>You can't even get small result sets with reasonable performance using
>>EJB.
>>
>>No matter what you try to do with EJB, I can provide a simpler, faster,
>>more scalable, and cheaper solution.
>> 
>>
>>>1) CTO (or some manager) gets the idea the EJBs are cool (after
>>>
>>reading a
>>
>>>BEA press release) and decides that his team's next project will be
>>>
>>done
>>
>>>using EJBs - without any thought as to whether EJBs are the correct
>>>
>>tool
>>
>>>for the Job.
>>>
>>Amen.
>>
>>This is exactly the problem.  
>>
>>Aaron
>>
-- 
dIon Gillard, Multitask Consulting
http://www.multitask.com.au/developers




--
To unsubscribe, e-mail:   <mailto:general-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:general-help@jakarta.apache.org>

[prev in list] [next in list] [prev in thread] [next in thread]