RE: beans and JSPs and stuff...

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

And to that end you're absolutely right, Brad.  My guess is that for a typical 
low-end AS/400 shop, the CGI approach, either via servlets or e-RPG, is 
probably the most cost-effective approach.  By using things you've already 
designed and perhaps tweaking them a bit, a competent RPG programmer can 
quickly web-face an application (although I'd argue that a good library of JSP 
component widgets will do much of what your CGI does, but since nobody has one 
readily available, e-RPG wins that debate by default).

Unfortunately, the CGI approach hits the wall when it comes to the more 
sophisticated aspects of web content design.  But then again, you're likely not 
going to hit that wall in a small shop.  So, if someone is just looking to get 
a basic web presence, and they like the way your stuff looks, then using your 
concepts is probably going to be the best solution, certainly for the short 
term, if not longer.

But if someone wants a truly scalable, deployable web application that happens 
to interface with legacy systems, then they're almost forced to use JSPs and, 
in the larger world, they may even have to start thinking about EJBs.

But the crux of your point, I think, is that no one size fits all in the 
dynamic web content market, and we cannot lose sight of that.  There are places 
where e-RPG fits, and places where servlets and JSPs fit.  The correct answer 
is "the one that does the job".

--------
But we have to remember that no one is perfect, not every shop as a team of
programmers, another of web designers, etc.. etc... which is seems is the
assumption when comparing these technologies.  

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---