I have and action that has two getters that return ints. Is there a way
for my view to render the sum of them? Currently I use a bean that has a
method int sum(int x, int y) { return x+y; }. Is there a better way?
--Erik
---
This sf.net email
Erik Beeson wrote:
I have and action that has two getters that return ints. Is there a way
for my view to render the sum of them? Currently I use a bean that has a
method int sum(int x, int y) { return x+y; }. Is there a better way?
Nope. You're doing it the right way. I'm not sure what
I return a very, very long list and would like to be able to page through
it. I have a startIndex and count. The link to the next page should be
startIndex=(startIndex+count); Since the business end was getting the list
in the first place, this indexing stuff seemed like it belonged on the
view
I'm a firm believer in keeping business logic out of your presentation
tier... but even to me... this seems like an appropriate place to use a
JSP scriptlet.
-Tim.
Quoting Erik Beeson [EMAIL PROTECTED]:
I return a very, very long list and would like to be able to page
through
it. I have a
I return a very, very long list and would like to be able to page through
it. I have a startIndex and count. The link to the next page should be
startIndex=(startIndex+count); Since the business end was getting the list
in the first place, this indexing stuff seemed like it belonged on the
Hello,
boxed wrote:
How about just 'out' for print? To go along with out.println etc.
Yes, as this aligns better with JSTL. The syntax of ww:out ... should
probably be the same or a superset of c:out
I know that out is the name in JSTL but I personally feel that this is an
argument
Erik,
The smart way to do this is abstract the business logic from that particular
page.
For example, create a 'Pager' object that stores the start and max items per
page.
Then you can have pager.getNextStart(), pager.getLastStart(),
pager.getEnd(), pager.getMax() etc.
Your action only needs
