See the "The Problem" discussion at http://virtualschool.edu/jwaa to
see whether the analysis presented there of the root problem applies
in your company.
In my view, whether the programming interface is graphical or not is
not the biggest different. The biggest is that conventional aps are
entirely within the scope of the programming language whereas big
parts of a web app are dynamically linked to the application and thus
immune to compile time type checks.
If this is the problem you're trying to solve, the software at this
link within a graphical environment like Visual Age could be exactly
what you're looking for.
At 7:36 PM +0200 8/6/01, Arkady Kasianski wrote:
>Whereas the programming model for traditional applications is well
>established and supported by a lot of tools and development
>environments, Web programming is a hodgepodge of markup languages,
>scripting environments, and server platforms. And unfortunately for
>the average programmer, the knowledge and skills required to write a
>Web application have little in common with those needed to do
>traditional application development.
--
For industrial age goods there were checks and credit cards.
For everything else there is http://virtualschool.edu/mybank
Based on Java Web Application Architecture: http://virtualschool.edu/jwaa
Brad Cox, Ph.D.; [EMAIL PROTECTED] 703 361 4751
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
