-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robert,
Robbert wrote: > Christopher Schultz-2 wrote: >> Whether or not you use struts, I highly recommend that you avoid tricks >> like calling a servlet from a JSP in order to execute your business >> logic. If you have a waterfall-style logical flow (i.e. execute servlet >> first, then JSP), it's only natural to have the flow actually do that. >> It's okay if you application isn't 100% "pull-based" ;) >> >> -chris > > It seemed like a good way of doing things at the time, since the Servlet's > output is not needed for the page itself. :p But I am doing more things than > necessary, yeah. Aah, I see that you're saying. Often, servlets emit no output. I would say that /almost all/ servlets emit no output, but that they are generally used to set up the request so that control can be passed to an output-generating mechanism (JSP, Velocity, whatever). This is the natural way that pretty much everybody does servlet programming. The best reason to switch is that you are having problems with your awkward setup, eh? ;) Good luck, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFXG/29CaO5/Lv0PARAshOAKCGunDTgL5egrEieSYKwS7Hi48F/ACcCsh4 TeB3BczhDR/32arMc1MjpwA= =HsIr -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
