I have a version 7.x application where I have an Ajax component that I add
some javascript to via this method:
@Override
protected void updateAjaxAttributes(AjaxRequestAttributes
attributes) {
super.updateAjaxAttributes(attributes);
attribute
Hi,
I think it's actually a bug. Could you open an issue on JIRA?
Andrea.
PS: thank you for investigating the issue!
On 24/05/2017 18:45, Claudia Hirt wrote:
Sorry, I think my description was a little unspecific.
The problem appears with the following HTML-code:
with autolinking set
Hi,
WDYT ? Do we need to implement #detach() in #map(), #filter(), etc ?
yes, I think this is a good idea: the returned model holds a reference
to the given model, so it should detach it.
Regards
Sven
On 24.05.2017 21:36, Martin Grigorov wrote:
On Tue, May 23, 2017 at 11:17 PM, Martin Gri
On Tue, May 23, 2017 at 11:17 PM, Martin Grigorov
wrote:
> Hi,
>
> On Tue, May 23, 2017 at 5:40 PM, Ihmehlmenn wrote:
>
>> Hello everyone,
>>
>> while trying out some of the very cool new features in Wicket 8,
>> specifically replacing PropertyModels with lambda expressions, I had a few
>> quest
On Wed, May 24, 2017 at 12:18 PM, Peter Henderson <
peter.hender...@starjar.com> wrote:
> On 24 May 2017 at 11:05, Peter Henderson
> wrote:
>
> >
> >
> > On 23 May 2017 at 22:24, Martin Grigorov wrote:
> >
> >> Hi,
> >>
> >> I'm afraid a quickstart would be needed to be able to tell what goes
>
Sorry, I think my description was a little unspecific.
The problem appears with the following HTML-code:
with autolinking set to true.
This leads to the following exception:
org.apache.wicket.markup.MarkupException: Unable to find component with
id 'top' in [WebMarkupContainer [Compone
On 24 May 2017 at 11:05, Peter Henderson
wrote:
>
>
> On 23 May 2017 at 22:24, Martin Grigorov wrote:
>
>> Hi,
>>
>> I'm afraid a quickstart would be needed to be able to tell what goes wrong
>> there.
>>
>
> Thanks for looking, I thought you'd say that.
> Attached is a quick (ish) start.
>
> br
On 23 May 2017 at 22:24, Martin Grigorov wrote:
> Hi,
>
> I'm afraid a quickstart would be needed to be able to tell what goes wrong
> there.
>
Thanks for looking, I thought you'd say that.
Attached is a quick (ish) start.
browse to
https://localhost:/redirect/protected/path/pageA/112233
Press