I guess it depends on what you mean by friendly urls. It would easy to
fix the page service but in looking thru the code it appears the
direct service separates it's parameters with an '&' also. While it's
possible to replace all that code it's quit a bit of work considering
the problems appears to be the '&' in the code below. I'm guessing
there is another one one the decode side.
I'm not really proposing this gets fixed and it seems a bit odd to me
that the spec prohibits '&' in a url considering everyone seems to use
them there, but it might be nice if future versions used something
other than '&' or allow you to configure it.
package org.apache.tapestry.engine.EngineServiceLink
private void addParameters(StringBuffer buffer)
{
String[] names = getParameterNames();
String sep = "?";
for (int i = 0; i < names.length; i++)
{
String name = names[i];
String[] values = getParameterValues(name);
if (values == null)
continue;
for (int j = 0; j < values.length; j++)
{
buffer.append(sep);
buffer.append(name);
buffer.append("=");
buffer.append(encode(values[j]));
sep = "&";
}
}
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
