Re: Compressed 'ConcatResourceBundleReference'?

But, I think, that the migration of Wicket Portlet should not be that difficult, as I have the feeling, that there were not so many changes as between 1.4 and 1.5. Maybe some changes with ajax handling... -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Compressed-Con

Re: Compressed 'ConcatResourceBundleReference'?

Hi Martin, i'm, not sure, if i'll have time to migrate the wicket portlet to wicket 6 so soon. Currently I've only started using Wicket 6 for my private projects. Portlets are necessary evil, that we have to use at work, so it has to wait for some new project, where we apply it. That's why the ent

Re: Portlet / ServetWebRequest / WICKET-4387 fix - Introduced a bug???

I think, that this has been fixed in wicket-portlet version 1.5.7.2, which can be downloaded from https://issues.apache.org/jira/browse/WICKET-4019 (which seems to be currently down for maintenance). I checked github, but there is also an old version, maybe because wicketstuff 1.5.8 has not been re

Re: UrlEncoder - question mark not encoded for parameter values

aah, that was really long time ago, when I used this for SpringComponentInjector, thanks for the tip. Peter. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/UrlEncoder-question-mark-not-encoded-for-parameter-values-tp3785027p3785702.html Sent from the Users forum mail

Re: UrlEncoder - question mark not encoded for parameter values

n Fri, Sep 2, 2011 at 11:05 AM, pasto <[hidden email]> wrote: >> Now I remembered, why I did not check the 'nextSequenceValue'. It returns >> an >> integer and I don't know about any unique portlet identifier, that is a >> number and could be used to make the

Re: UrlEncoder - question mark not encoded for parameter values

Now I remembered, why I did not check the 'nextSequenceValue'. It returns an integer and I don't know about any unique portlet identifier, that is a number and could be used to make the markup ID unique. Of course, I can generate a hash or use a part of the portlet name, but that does not look that

Re: UrlEncoder - question mark not encoded for parameter values

Thanks a lot, somehow I did not expect it so be so easy to override :). I have filed a bug for the UrlEncoder https://issues.apache.org/jira/browse/WICKET-4019. Peter. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/UrlEncoder-question-mark-not-encoded-for-parameter-

UrlEncoder - question mark not encoded for parameter values

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 Li

Re: Replacement of a markup container with nested components by a panel / fragment

d you attach a panel to "foo" who is going to render "bar"? > > -igor > > > On Sun, Jun 19, 2011 at 6:42 AM, pasto <[hidden email]> wrote: >> Hi, >> >> I guess, this is the same question as the 'WICKET-1190' issue. >> >>

Replacement of a markup container with nested components by a panel / fragment

Hi, I guess, this is the same question as the 'WICKET-1190' issue. Extending AjaxLazyLoadPanel and overriding the xhtml markup file and the getLoadingComponent method causes, as soon as there is a child component in the 'content' component, "Close tag not found for tag" exception. http://wicket.