Hi James,
so you want to configure a component inside a (possibly deeply) nested
hierarchy from the outside?
Searching up the component tree for an implementation of an interface
seems like a good idea.
Problem with that solution is that this interface might grow bigger and
bigger as your re
Cve db also updated :)
WBR, Maxim
(from mobile, sorry for the typos)
On Fri, Apr 20, 2018, 19:22 Sebastien Briquet wrote:
> FYI.
>
> Thanks Maxim! :)
>
> -- Forwarded message --
> From: Maxim Solodovnik
> Date: Wed, Apr 18, 2018 at 6:39 PM
> Subject: [ANNOUNCE] CVE-2018-1325 -
Component#isVisible() uses internally Component#isVisibleInHierarchy(), so
it should just work.
Or maybe I didn't understand you.
On Fri, Apr 20, 2018 at 3:25 PM, James Carman
wrote:
> I have a scenario where a certain type of component should typically be
> invisible, but in certain scenarios,
I have a scenario where a certain type of component should typically be
invisible, but in certain scenarios, it neeeds to become visible. That
visibility can be changed by anybody in its ancestry and the closest one to
the component should decide. Anyway, do we have established patterns for
this?
FYI.
Thanks Maxim! :)
-- Forwarded message --
From: Maxim Solodovnik
Date: Wed, Apr 18, 2018 at 6:39 PM
Subject: [ANNOUNCE] CVE-2018-1325 - Wicket jQuery UI: XSS while displaying
value in WYSIWYG editor
To: Openmeetings user-list , dev <
d...@openmeetings.apache.org>, user-russ..
Hi,
You can use wicket-examples as inspiration:
https://github.com/apache/wicket/blob/master/wicket-examples/src/main/java/org/apache/wicket/examples/ajax/builtin/AjaxDownloadPage.java
On Fri, Apr 20, 2018 at 1:20 AM, Lon Varscsak
wrote:
> Okay, cool. I did see this, but one of the things I wa
On Thu, Apr 19, 2018 at 5:40 PM, tomask79 wrote:
> Hi Martin,
>
> I created a Wicket 6.21 patch with following change:
>
>
A diff/patch format is much easier to review and comment on.
> static class ProxyReplacement implements IClusterable {
> private static final long serialVersionUID
