Hey All,
Everyone says for performance purposes, working directly with the resultset is
optimal. But, with MVC, we can't just push the RS to the JSP to display and ignore
closing.
Is it possible with Filters to do a M->C1->V->C2 where C1 sets resultsets in the
request, then pushes the response up to the JSP to render the content and then closes
the resultset after rendering. I know 'programatically' it would work, but, I'm
wondering about exceptions and making sure that the resultsets get closed. An example
would be passing the request/response to the JSP, but then an exception occurs up the
chain, does the exception trickle back down through the filters no matter what to
catch and close my JDBC items?
Best Regards,
Jacob Hookom
