I was working on an application this week, and while it works, I am not sure I 
did it correctly.  The application consists of a page which lists records, 35 
at a time, and a page that displays that record in detail.  I had a couple of 
issues implementing this revolving around parameter passing.  In the list page 
there exist a property called pageNum which contains the current page in the 
list of records to display.  Using straight JSPs, I would just pass pageNum as 
a request parameter.  Using tapestry, I marked the property as 
@Persistent(“client”).  This produces some strange URLs, but my real question 
is whether or not I implemented this in a good way.

 

The second issue I have is that when a record is clicked, I set a property on 
the detail page which contains the record id.  Initially, I passed the whole 
bean, but I dumped that idea when I saw the urls that were produced.  The 
problem that I have with the current strategy is that the bean has to be looked 
up again on the detail page.  Again, did I do this in the correct way?

 

Thanks for your help,

Rob Dennett


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/204 - Release Date: 12/15/2005
 

Reply via email to