Joe P. wrote:
Not really. CGIDEV2 actually is quite robust, as it has to re-invent
all of the template caching and substitution that JSP has inherently
built in.

I understand that CGIDEV2 does some things that the servlet wouldn't need to
do, but if I understand correctly the workload management and other services
provided by the servlet are beyond the scope of CGIDEV2; Launching an instance
of the RPG program for each user requesting the program, handling the
communication between each browser and each RPG program instance, ending RPG
program instances, automatically loading XML definitions for each application,
dynamically generating one or more beans for each JSP, automatically mapping
fields from RPG program data structures to beans, automatically mapping fields
from JSP-HTML forms to RPG program data structures, dynamically evoking the
right JSP for every output operation for every application, handling and
reporting errors, updating the file information data structure, and so forth.

I think I agree with your original premise, though. Given all the plumbing in
your framework, the code that the developer has to create/maintain doesn't seem
to be hard.

Nathan.







As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2024 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.