Hi,

On Fri, Sep 2, 2011 at 2:12 AM, pasto <[email protected]> wrote:
> Hi,
>
> while patching the original portlet support in Wicket 1.4 to Wicket 1.5, I
> run into 2 problems:
>
> 1) Url returned by the RequestMapper does not seem to be properly rendered,
> as it does not encode question mark character in the Url parameter value (I
> haven't checked the w3c spec, but at least Liferay Portal seems to require
> it to be encoded)
>
> The reason is this definition in the UrlEncoder:
>                        case QUERY :
>                                // to allow direct passing of URL in query
>                                dontNeedEncoding.set('/');
>                                // to allow direct passing of URL in query
>                                dontNeedEncoding.set('?');
File a bug for this. We need to verify it.
I also found a bug there few months ago so it is not impossible.
>
> Is it a bug or (according to the comment) a feature?
>
> 2) I could not find an easy way to make the markup ID unique across
> applications (multiple applications per page). The original portlet support
> adds a portlet identifier to the markup ID in the PortletRequestContext. Is
> there a way to do it in Wicket 1.5? (I haven't checked, if it's possible,
> but maybe a MarkupFilter?)
The unique id (its suffix) is generated by
org.apache.wicket.Session.nextSequenceValue().
Override it with something that will produce an unique id for your case.
>
> Thanks,
> Peter.
>
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/UrlEncoder-question-mark-not-encoded-for-parameter-values-tp3785027p3785027.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to