Identifying the 'clicked' line when iterating over collection

2004-08-30 Thread andy wix
Hi, In my jsp page I have an ArrayList of contact objects and I use this to build an html table; one contact per row. At the end of each table row I have edit and delete links such that the form looks roughly like: Name Number Fred1234edit delete Barney

RE: Identifying the 'clicked' line when iterating over collection

2004-08-30 Thread Jim Barrows
> -Original Message- > From: andy wix [mailto:[EMAIL PROTECTED] > Sent: Monday, August 30, 2004 1:04 PM > To: [EMAIL PROTECTED] > Subject: Identifying the 'clicked' line when iterating over collection > > > Hi, > In my jsp page I have an ArrayList

Re: Identifying the 'clicked' line when iterating over collection

2004-08-30 Thread benanderson
It sounds like you want to attach parameters to your link? How bout something like this: ... ... Quoting andy wix <[EMAIL PROTECTED]>: > Hi, > In my jsp page I have an ArrayList of contact objects and I use this to > build an html table; one contact per row. At the end of each table row I >

RE: Identifying the 'clicked' line when iterating over collection

2004-08-30 Thread James Childers
y. -= J > -Original Message- > From: andy wix [mailto:[EMAIL PROTECTED] > Sent: Monday, August 30, 2004 3:04 PM > To: [EMAIL PROTECTED] > Subject: Identifying the 'clicked' line when iterating over collection > > > Hi, > In my jsp page I have an ArrayList of contact

Re: Identifying the 'clicked' line when iterating over collection

2004-08-30 Thread Rick Reumann
[EMAIL PROTECTED] wrote: It sounds like you want to attach parameters to your link? How bout something like this: ... ... The above is nice, or I just use the JSTL url tag so for a row you might have (if using one dispatch Action called contactAction ) ... EDIT DELETE or if JSP 2.0 ED

Re: Identifying the 'clicked' line when iterating over collection

2004-08-31 Thread andy wix
Hi, I have tried most of the code in the replies and, alas, fear my brain is too small to get any working. I am persevering with Rick Reumann's method (because I liked the Struttin' with Struts stuff!) but I don't get a session parameter in my next page after the link is followed (I have changed

RE: Identifying the 'clicked' line when iterating over collection

2004-08-31 Thread Jim Barrows
> -Original Message- > From: andy wix [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 31, 2004 9:19 AM > To: [EMAIL PROTECTED] > Subject: Re: Identifying the 'clicked' line when iterating over > collection > > > Hi, > > I have tried most

RE: Identifying the 'clicked' line when iterating over collection

2004-08-31 Thread Daniel Perry
ugust 2004 17:19 > To: [EMAIL PROTECTED] > Subject: Re: Identifying the 'clicked' line when iterating over > collection > > > Hi, > > I have tried most of the code in the replies and, alas, fear my > brain is too > small to get any working. > I am persevering with

Re: Identifying the 'clicked' line when iterating over collection

2004-08-31 Thread Rick Reumann
andy wix wrote: session). To get the ID would be something, but it would save me needing an action class at all if I could get the contact object representing the 'clicked' row into the session or request scope. To do what you want above would take a slightly different approach. Say you had you

Re: Identifying the 'clicked' line when iterating over collection

2004-08-31 Thread Rick Reumann
Rick Reumann wrote: To do what you want above would take a slightly different approach. Say you had your ArrayList of Contacts in Session scope and after the user clicked on a link you wanted to edit one of those objects. In this case you wouldn't use the "ID" to look him up you'd have to use th

RE: Identifying the 'clicked' line when iterating over collection

2004-09-01 Thread andy wix
Hi, I am trying to follow the advice given yesterday but am now baffled by the basic jstl stuff. I have cut it down to basics and still get no output actually written to the page. I've tried all variations on the theme (have the arraylist in the session, use c:outs in the "" tags etc). The code