On Sun, May 30, 2010 at 8:04 AM, Witold Szczerba <pljosh.mail_at_gmail.com> wrote:
> OK, so how the "pass values to the view" part is supposed to be done?
> Servlet has the "response" object and someone, sooner or later, will
> have to write to it...
But not your servlet. Your servlet(s) simply perform whatever logic
they're intended to do and place the appropriate values into the
request (or session) and then forward the request to the view. The
container is responsible for writing that view to the response.
> So, going back to my original question: how
> should it look like? Should the "out.close();" happen unconditionally
> (finally block)?
It's irrelevant, you shouldn't be doing it, but theoretically, yes, of
course; why would you *not* want that PrintWriter closed??
> So, I was trying my luck with one level lower: servlets. Security +
> full Java EE integration works like a charm here, it seems like a good
> facade for AJAX calls. But, as I just said: sooner or later - it will
> happen and data will go into PrintWriter.
If you're doing it right, you'll never be calling a PrintWriter yourself. Not
ever :-)
--
Hassan Schroeder ------------------------ hassan.schroeder_at_gmail.com
twitter: @hassan