If your boss can read french, be carreful he doesn't find this link:
http://www.application-servers.com/comments.do?reqCode=readComments&sid=2003-03-23-22:17:22
To find good arguments, we have to know what you should use if NOT using struts :
- nothing but J2EE (lots of servlets and JSP build for tour app)
=> Struts will help you have your application "well builded" as using lots of best
practice or design-patterns
=> Struts is a good example for OO developments
=> Struts is not a w3 standard, but is becoming ever more popular
=> Struts has support from an active community
=> Struts has a readable code and can be easily extended if needed
- another framework (?)
=> begin a new "foo vs Struts" thread
- build a framework for internal use
=> I've done it as Struts was 0.5 and we cannot use it for "political" reasons. We
built our own framework on same
idea (but with less OO design experience) and have to maintain it on old apps today.
Compared to nowaday Struts 1.1 it
is realy poor and confuse.
=> Struts can be easily extended if needed. You can contribute and see your
extends beeing improved and debugged by
other (formulated this way, it is a good argument for your boss)
=> Struts has been build by and with help from java, J2EE and OO design experts
for 3 years. You're very lucky if
you have such developpers in your team.
Nico.
Hi!
I have to convince my boss about using or not Struts in our next project. I
really want to use but I have to explain the arguments.
Anybody knows any document, presentation or anything else that can help me?
Thanks,
Jo�o Paulo.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
