Tapestry handles that ok - twice "sp" or more, its no problem.
In your listener you use (for example):
public <return-type> action(String name, int number) {
}
tapestry will do the work to translate the parameters to the right values...
hope that answers...
ציטוט Wouter De Vaal:
I don't think you understood me correctly.
What I meant was that two times the parameter sp is used. It is my
understanding you should use different names for parameters to
distingish them.
On a basic level what value would I get when I would call
getParameter("sp") on HttpServletRequest? 1 or 2? This just looks
wrong..
Wouter
On 11/2/05, Hensley, Richard <[EMAIL PROTECTED]> wrote:
Nope, that's right. Tapestry doesn't really do much with the parameter
names, they are just place holders. The real important thing is the order of
the parameters.
Richard
-----Original Message-----
From: Wouter De Vaal [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 02, 2005 11:51 AM
To: Tapestry users
Subject: DirectLink with multiple parameters - bug?
Hi,
When I create a DirectLink with multiple parameters like this:
<a href="#" jwcid="@DirectLink" listener="ognl:listeners.showDetail"
parameters="ognl:{1,2}">
The link gets rendered as
...$DirectLink.direct?sp=1&sp=2
So two times the sp=. This doesn't seem correct. Might this be a bug,
or am I missing something?
I'm using 4 beta 12
Regards,
Wouter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
