The following comparison is by the authors of "Designing Enterprise Application" by 
the J2EE blue print team, which clearly says it is the other way. You can also check 
it at 
http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/web-tier/web-tier5.html#1094743

J2EE BluePrints Web Application Framework ("WAF")--The Web Application Framework forms 
the infrastructure of the sample application. This framework offers a Front Controller 
servlet, an abstract action class for Web-tier actions, a templating service, several 
generic custom tags, and internationalization support. WAF demonstrates both the 
mechanisms and effective use of a Web-tier framework layer in an application design. 
It is suitable for small, non-critical applications, and for learning the principles 
of Web-tier application framework design and usage. 

Apache Struts--Struts is a free, open-source, Web-tier application framework under 
development at the Apache Software Foundation. Struts is highly configurable, and has 
a large (and growing) feature list, including a Front Controller, action classes and 
mappings, utility classes for XML, automatic population of server-side JavaBeans, Web 
forms with validation, and some internationalization support. It also includes a set 
of custom tags for accessing server-side state, creating HTML, performing presentation 
logic, and templating. Some vendors have begun to adopt and evangelize Struts. Struts 
has a great deal of mindshare, and can be considered an industrial-strength framework 
suitable for large applications. But Struts is not yet a "standard" for which J2EE 
product providers can interoperably and reliably create tools. 

Jayaraman


-----Original Message-----
From: Khan, Manuchehar A (ACF) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 11, 2002 10:37 AM
To: 'Struts Users Mailing List'
Subject: Question for using struts as our standard MVC framework


Hello Folks. I work for Govt and we have major policy meeting for using
struts as our stantard framework. 
One developer in our team took the Sun pet store example and created a
framework that is basically a router/controller with xml configuration files
to define handlers and views. And that controller works fine..
He claims that strut has not followed sun standards and guidelines and
struts is not reliable. It can only support maximum 100 users and next year
struts team is coming up with new version based in JSTL and will trash all
releases.
I need some inputs from people here to make solid arguments for changing to
struts. 
Thanks...



-----Original Message-----
From: James Mitchell [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 11, 2002 10:34 AM
To: Struts Users Mailing List; Dariusz Wojtas
Subject: RE: JDO example - rozpakowywac Commanderem


Was there a question in there I missed?

James Mitchell
Software Engineer\Struts Evangelist
Struts-Atlanta, the "Open Minded Developer Network"
http://www.open-tools.org/struts-atlanta




> -----Original Message-----
> From: Dariusz Wojtas [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 11, 2002 3:19 AM
> To: Struts Users Mailing List
> Subject: JDO example - rozpakowywac Commanderem
>
>
> Wednesday, September 11, 2002, 6:55:25 AM, you wrote:
> JM> Sorry for the delay.  I've decided to post this on our website.
>
> JM> Please feel free to download and try it out.
>
> JM>  http://www.open-tools.org/struts-atlanta/downloads/DBMessageResources
>
> JM> If for some reason the site goes down, just send me an email
> and I'll get it
> JM> to you.
>
>
>
>
> JM> James Mitchell
> JM> Software Engineer\Struts Evangelist
> JM> Struts-Atlanta, the "Open Minded Developer Network"
> JM> http://www.open-tools.org/struts-atlanta
>
>
>
>
> >> -----Original Message-----
> >> From: James Mitchell [mailto:[EMAIL PROTECTED]]
> >> Sent: Tuesday, September 10, 2002 3:06 PM
> >> To: Struts Users Mailing List
> >> Subject: [Announce] [New Extension]
> ApplicationResources.properties from
> >> Database
> >>
> >>
> >> For anyone interested, I have finished implementing DBMessageResources
> >> which allows you to keep the key-value pairs (from your
> >> ApplicationResources.properties) in a single database table.
> >>
> >> You can load your property files into a table (generic schema
> is provided)
> >> and with this extension, by only modifying <message-resources> in the
> >> struts-config.xml your application will run WITHOUT ANY code
> changes. (See
> >> the readme.txt file included)
> >>
> >> This extension uses OJB (http://jakarta.apache.org/ojb) O/R mapping for
> >> database configuration and connection pool management.
> >>
> >> I have included a modified version of the (1.1b2) struts-example to
> >> demonstrate.
> >>
> >> I have tested this with Struts 1.1b2, and I'm sure it will
> work with 1.1b1
> >> (If anyone requires a 1.0.x compatible, I can look at that also)
> >>
> >> I will get this project available as soon as I work through some
> >> cvs issues
> >> on sf.net:
> >>
> >> If anyone is REALLY itching to get their hands on it sooner, send me a
> >> email.
> >>
> >> For those who were waiting, thanks for your patience.
> >>
> >>
> >> James Mitchell
> >> Software Engineer\Struts Evangelist
> >> Struts-Atlanta, the "Open Minded Developer Network"
> >> http://www.open-tools.org/struts-atlanta
> >>
> >>
> >> --
> >> To unsubscribe, e-mail:
> >> <mailto:[EMAIL PROTECTED]>
> >> For additional commands, e-mail:
> >> <mailto:[EMAIL PROTECTED]>
> >>
> >>
>
>
> JM> --
> JM> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
JM> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>




--
Best regards,
 Dariusz Wojtas                 mailto:[EMAIL PROTECTED]


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to