The 'problem' is that you are processing your data in your view controller
JSP which is not really where it belongs. You should just move that code up
a layer into Java. The t:action comes from using http://tagonist.tigris.org/.
Tagonist (or something like it that allows you to execute java code as
On 3/25/2010 10:31 AM, Jon Stevens wrote:
I don't mind using JSP's for some of the (separated) control logic.
For example, you have a form action:
Inside of it, it looks like this:
http://code.google.com/p/subetha/source/browse/trunk/web/email_confirm_submit.jsp
That said, look at that code
I don't mind using JSP's for some of the (separated) control logic. For
example, you have a form action:
Inside of it, it looks like this:
http://code.google.com/p/subetha/source/browse/trunk/web/email_confirm_submit.jsp
That said, look at that code. The logic for determining the next page to
It's not in the view layer. We segregate our controller JSPs from our
view JSPs. So you will change your argument to say that we should not
use JSPs at the control layer, and of course _most_ of our control logic
is in pure Java, but there are cases where having our controller logic
written i
This is why you don't put application logic into the view layer. Before you
'push' your data into the view, figure out if you want to do the redirect or
not.
jon
On Thu, Mar 25, 2010 at 7:49 AM, Aaron Freeman wrote:
> We take some fairly lengthy queries (lengthy row based on row count), and
> p
We take some fairly lengthy queries (lengthy row based on row count),
and push the data into hashmaps in JSTL pages. After that sometimes we
evaluate the hashmap and sometimes have to redirect the request to
another page. In 3.0.23 it works with no problems. In 4.0.5 we get
"java.lang.Illega
