> -----Original Message-----
> From: resdev [mailto:[EMAIL PROTECTED]
> Sent: 04 April 2003 07:04
> To: Struts Users Mailing List
> Subject: Re: Re: Which is the best Struts or Expresso ?
>
>
> Hi,
>
>
> wht happend ? im not getting any valuable reply that says
> Struts is best.
>
>
> does that mean Expresso is better ? i think even the Struts
> developers are confused .......;)
--////--
How do you do
As an Expresso core committer, as would have to say is that the main
difference is that Jakarta Struts is a framework that provides
a defacto and complete Model View Controller implementation,
it fully implies Sun's Blueprint 2 Model architecture.
Both Struts and Expresso are frameworks, tools to help you, the developer,
write web applications. Expresso uses Struts as its MVC implementation.
At this moment I integrated Struts 1.1 into Expresso last month.
Expresso provides more bits and pieces, such as an object relational
mapping layer, a caching API, database connection pool, action
state controllers, administration interface, security, componentisation
service architecture and so on.
I tend to think of the arguments are building A B C blocks.
I would rather not rewrite the wheel, hence I like Struts as a MVC.
I can concentrate on writing applications for myself or get paid
as a contractor. Whether to adopt Struts or Expresso
depends on the business requirements and the project. Struts is
a lighter weight because it only concentrates on MVC, and therefore
fits a lot of organisations, it is a smaller puzzle piece.
Whereever Expresso, you might have to think about other tools
from the J2EE architecture. Your business might have its own
business database pool API. Or it might use a different security
mechanism. This has been a problem, admittedly, that made Expresso
harder to push in to more enterprise, but help is it hand, because
a clever guy called Micheal Rimov, came up with a modular
service framework architecture recently. This new API is
still in development mode at the moment, but it looks promising,
very promising, because you will be able to define what Expresso
modules are loaded from a XML configuration. Customisation of the
framework.
So if you only need the default object caching API from Expresso,
and the connection the pool, you can write XML configuration.
But the bueaty of the service layer is that you could override,
write your caching API, or enhance the existing in,
and dynamically plug-in the module. The service layer will be
appearing in Expresso version 5.1 or beyond.
HTH - Now I got to go back to work ....
--
Peter Pilgrim,
Struts/J2EE Consultant, RBoS FM, Risk IT
Tel: +44 (0)207-375-4923
********************************************************************
Visit our Internet site at http://www.rbsmarkets.com
This e-mail is intended only for the addressee named above.
As this e-mail may contain confidential or privileged information,
if you are not the named addressee, you are not authorised to
retain, read, copy or disseminate this message or any part of it.
The Royal Bank of Scotland plc is registered in Scotland No 90312
Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB
Regulated by the Financial Services Authority
********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
