(boolean), parameters are simply appended to
a wicket url using &.
In a web application environment this is valid as the base wicket url is always
(???) using a query string so the required initial ? to mark the start of the
query string is already provided.
But PortletURLs are (and must be)
fer a facility for parsing query
parameters in this form using slashes, only using the query string beginning
with "?" so you'd better avoid encoding slashes in the bookmarkable page
parameters. Wicket does its best to parse the slashes-delimited query
parameters, but it'
+ * the appropriate request target, calling getURI(requestParameters) to get
+ * requested uri. Note that this request coding strategy takes other page
+ * parameters from the query string directly, it does not use hierarchical path
+ * for parameters.
+ *
+ * @author mailto:[EMAIL PROTECTED]"&
{
-
url.append("?"); /* Begin query string. */
- firstParam
m error
*validation error
*/
@@ -307,7 +304,7 @@
/**
* Gets the request parameter for this component as a string.
-*
+*
* @return The value in the request for this component
*/
// TODO Post 1.2:
.newCrypt();
-
+
// Decrypt the query string
String queryString =
urlCrypt.decryptUrlSafe(secureParam);
-
+
// The querystring might have been shortened
(length reduced).
.coding.IRequestTargetUrlCodingStrategy;
import wicket.request.target.component.IBookmarkablePageRequestTarget;
@@ -60,7 +61,7 @@
* @author Eelco Hillenius
* @author Jonathan Locke
*/
-public class WebRequestCodingStrategy implements IRequestCodingStrategy
+public class WebRequestCodingStra
