Hi,
In our web application we have a dashboard-like homepage that displays a
number of user-configurable 'portlets' (which are really just ordinary
Wicket components and have nothing to do with the Portlet spec). I'm
looking for a way of preventing the application from becoming unusable
in
Wouldn't it be possible to embed the failing prone porlets inside
iframes so that each one is a Wicket page?
On Fri, Oct 10, 2014 at 11:12 AM, Tobias Gierke
tobias.gie...@voipfuture.com wrote:
Hi,
In our web application we have a dashboard-like homepage that displays a
number of
Hi,
As explained elsewhere the disabling of a button/link/... is not a single
solution that works for everyone. That's why it is not part of Wicket
itself.
If it is just about suppressing the clicks on the button then using
AjaxChannel.Type.ACTIVE is good enough. By using ACTIVE type you tell
Hi,
Wouldn't it be possible to embed the failing prone porlets inside
iframes so that each one is a Wicket page?
I already thought about this but the page uses quite a lot of fancy
CSS/Ajax/Javascript (portlets are rendered in a grid with configurable
row/column count, drag'n'drop to move
Hi,
On Fri, Oct 10, 2014 at 11:50 AM, Tobias Gierke
tobias.gie...@voipfuture.com wrote:
Hi,
Wouldn't it be possible to embed the failing prone porlets inside
iframes so that each one is a Wicket page?
I already thought about this but the page uses quite a lot of fancy
Hi,
There is no support for this, even in 7.x.
I remember Carl-Eric Menzel asking for the same functionality before ...
Behavior#onException() sounds like something similar but there is no way to
suppress the bubbling of the exception at the moment.
The bigger problem is that the rendering can
I am using wicket for the following test case scenario:
1. group of radio buttons- radiochoice
2. group of check boxes- checkgroup
3. when option is selected from 1, we update checkboxes for 2. This works
fine.
4. now user can select more checkboxes in 2 and Goal is to retrieve the
information
Hi,
Using 7.0.0-SNAPSHOT, I've got a UnsupportedOperationException (see below)
whereas I do not have it on 7.0.0-M3. I don't really know how to
investigate as an UnsupportedOperationException seems to be the expected
result [1], or maybe #sendError is not supposed to be called anyway, or it
is a
Hi Sebastien,
With https://issues.apache.org/jira/browse/WICKET-5701 I've added support
for RequestCycle.find(AjaxRequestTarget.class) and actually proper support
for scheduling any kind of IRequestHandler.
In M3 your ErrorCodeRequestHandler has been just send to /dev/null.
One option is to
Hi Martin,
Thanks for your quick answer!
Just to be sure we are on the same page, I do not call #sendError myself...
I suppose it is called automatically because an exception is thrown
elsewhere (let's considering this is the intended behavior in my case...).
One option is to replace throw
On Fri, Oct 10, 2014 at 6:40 PM, Sebastien seb...@gmail.com wrote:
Hi Martin,
Thanks for your quick answer!
Just to be sure we are on the same page, I do not call #sendError myself...
I suppose it is called automatically because an exception is thrown
elsewhere (let's considering this is
11 matches
Mail list logo
