Maybe I didn't explain it precise enough, the subclass ain't the right place
to do that cause my usecase is like:
class Super {
onBeforeRender() {
if (!isValid()) {
throw Abort...Exception(404);
}
}
abstract boolean isValid();
}
class Sub extends Super
While creating a quickstart for the jira issue, I noticed that it only occurs
when using custom error pages as described on
http://cwiki.apache.org/WICKET/error-pages-and-feedback-messages.html ... so
maybe jetty creates a new (internal) web request and the application gets
detached before the "ol
thats really a strange error at that time the application should still be
there.
On Wed, Apr 2, 2008 at 11:41 AM, Michael Sparer <[EMAIL PROTECTED]>
wrote:
>
> (Using wicket 1.3.2) I have a super class (WebPage) that throws a
> AbortWithWebErrorCodeException(404) depending on some properties of
jira...
-igor
On Wed, Apr 2, 2008 at 2:41 AM, Michael Sparer <[EMAIL PROTECTED]> wrote:
>
> (Using wicket 1.3.2) I have a super class (WebPage) that throws a
> AbortWithWebErrorCodeException(404) depending on some properties of its
> subclasses. Therefore I can't check the subclasses' properti
Why not implement this in the subclass itself? It sounds really specific for
a certain class right? So I think the subclass itself is the correct place.
On Wed, Apr 2, 2008 at 11:41 AM, Michael Sparer <[EMAIL PROTECTED]>
wrote:
>
> (Using wicket 1.3.2) I have a super class (WebPage) that throws a
