The main argument against using EJB's is development costs, and larger
up front hardware costs for similar performance. There is no need for
the complexity involved in an EJB application for most webapps.
Properly used JSP should be just as easily written by a non-programmer
as WM/Velocity templates and if it is done right there should be a MVC
separation. Templates just enforce the separation whereas JSP does
nothing in this regard.
Carl Ludewig wrote:
>
> Hi Everyone,
>
> I'm in charge of selecting the technology for a new web system at AudioBase. I'm
> inclined to use Turbine, and was wondering if someone could answer a question
> for me. The marketing and management folks have heard a lot of the hype
> surrounding J2EE, JSP & EJBs. Can someone make a compelling argument that would
> go over well with business types on why we should ignore the 'enterprise
> standard' promoted by Sun and use Turbine. Jason Hunter has provided a good
> argument for using WebMacro or Velocity, so I guess I'm really looking for why
> Turbine is better than EJB solutions provided by others. You don't need to
> convince me as a programmer. I'm looking for reasoning that would appeal to the
> biz types.
>
> Much Thanks,
>
> Carl
>
> --
> Carl Ludewig
> Director of Research & Development
> AudioBase, Inc.
> (415) 389-6875
> [EMAIL PROTECTED]
> http://www.audiobase.com/
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
