RE: Aaron Bartell's RPG/Java comparison

["Joe Teff" <JoeTeff@xxxxxxxxxxxxx>]

Include is a great way to copy in a peice of standard
code. I see includes the same as /COPY in RPG. Good
for standard chunks of code, but not for code where
dynamic data will be placed. BTW - Java supports an
include method using a RequestDispatcher.

"dirty work" simply refers to any programming. JSPs
should contain as little programming code as possible.
You know, separate logic and database from presentation.

   html page --calls--> a servlet
   servlet accesses parms from the request
           builds object(s) [i.e. beans]
           binds objects to request, session, etc
   servlet --forwards request--> jsp
   jsp contains html with tags to access beans
   jsp --sends--> document to browser

The servlet can make choices and forward to different
jsp. HTML designers can learn enough jsp syntax as its
very similar to htmlitself. This means programmers write
Java and web designers write jsp.

Tag libraries give another level of support because you
write Java code that can be used by the jsp writers.
Think of this as the ability to write your own jsp syntax.

Joe Teff

-----Original Message-----
> >>And "seperating business logic from processing layer" is
> >>99% buzzword.  I've done it with my app as much as you can
> >>with any Java App.
 
> >The separation comes with JSP. Your HTML calls a servlet
> >which does the dirty work and then forwards the request
> >to a JSP that builds the page.
 
Ok, what is this "dirty work" that you're referring to. Why
does it have to be done with JSP, as compared to SSIs?
+---
| 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
+---