Kenneth McMenamy skrev den 25-09-2007 22:06:
structured approach to design applications that consistently performed. Now we are faced with multiple language choices with ever changing frameworks JSP, JSF, Grails, Spring, Hibernate, EJB, AJAX (Google API), PHP. . . The list goes on and on...
My two cents is to pick a language **cough** -Java- **cough**, a framework and stick with it. By the time you complete your GUI'fication an entirely new set of standards will have surfaced.
For a web application written in Java I would recommend sticking with JSF - the Sun approach to standards combined with the Apache Jakarta implementations (which tend to be well-maintained and long living) - have worked well so far - I have a complete application where the pages contain only JSF-tags and an occasional JavaScript submit(). This works well for maintainability.

Additionally the JSF AJAX stuff seems very easy to get up and running when you have a JSF application already.

But in short: When you choose what to use, it is hard to guess what will be available and maintained in the next 10-20 years. The Sun standards tend to hold - notice that all J2EE servers still must implement the earlier EJB standards so the code will still run - and the Apache site does not seem to be going away soon.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.