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 them around etc.) and I'd rather
not touch the existing code if there's a Java-side only solution ;-)
Cheers,
Tobias
On Fri, Oct 10, 2014 at 11:12 AM, Tobias Gierke <
[email protected]> wrote:
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
case one or more of these portlets continuously fail to render because of
some internal error/bug.
We're currently using a custom RequestCycleListener with the onException()
method redirecting to a generic error page, thus when rendering of a
'portlet' fails the user will never get to see the homepage and always end
up on the error page - which is obviously not really desirable.
Is there a way to to hook into Wicket's rendering cycle so that I can
provide some default markup in case rendering of a component (subtree)
fails with a RuntimeException ?
I understand that this maybe be very tricky since the component subtree
might've rendered partially and thus internal state will be inconsistent.
It would probably require serializing the initial state of the component
(subtree) before rendering starts and reverting the wholle subtree to its
initial state once a RuntimeException is thrown.
We're running Wicket 1.5.12.
Thanks in advance,
Tobias
--
Tobias Gierke
Development
VOIPFUTURE GmbH Wendenstraße 4 20097 Hamburg, Germany
Phone +49 40 688 900 164 Fax +49 40 688 900 199
Email [email protected] Web http://www.voipfuture.com
CEO Jan Bastian
Commercial Court AG Hamburg HRB 109896, VAT ID DE263738086
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
