der getExceptionMapperProvider() {
>> return new IProvider() {
>>
>> @Override
>> public IExceptionMapper get() {
>> return new MyCustomExceptionMapper();
>> }
>> };
>> }
>>
&g
() {
> return new MyCustomExceptionMapper();
> }
> };
> }
>
> /**
> * Our own exception mapper, so that we can display further
> information on the error page
> * in case of an exception.
> */
> public class MyCustomExceptionMapper extends Defau
information on
the error page
* in case of an exception.
*/
public class MyCustomExceptionMapper extends DefaultExceptionMapper {
@Override
public IRequestHandler map(Exception e) {
return new RenderPageRequestHandler(new PageProvider(new
MyErrorPage(e
Hi,
On Wed, Mar 4, 2015 at 6:39 AM, sameerkhanna sameerkhanna1...@gmail.com
wrote:
Hi,
I am facing a strange issue while trying to display a generic application
error page whenever some exception is thrown.
We recently upgraded from wicket 1.3 to wicket 6. However, it was a step by
step
Hi,
I am facing a strange issue while trying to display a generic application
error page whenever some exception is thrown.
We recently upgraded from wicket 1.3 to wicket 6. However, it was a step by
step upgrade for each major version. There were no issues from 1.3 to 1.4.
However, after
The exception occurred within an AjaxButton. In this case, a service was not
responding, we want to show our error page, and put a custom message up
indicating that it is a service problem, call the help line or try again
later blah blah blah...
I don't think any redirects are involved.
--
View
On Mon, Oct 27, 2014 at 1:26 PM, Entropy blmulholl...@gmail.com wrote:
The exception occurred within an AjaxButton. In this case, a service was
not
responding, we want to show our error page, and put a custom message up
indicating that it is a service problem, call the help line or try again
Well, you are definitely right that there are multiple requests for whatever
reason. I can see WicketServlet doPost called, the method runs, throws the
error, the error page gets control with the exception, then a doGet occurs
and the error page runs again without the exception.
I can't really
blmulholl...@gmail.com wrote:
Well, you are definitely right that there are multiple requests for
whatever
reason. I can see WicketServlet doPost called, the method runs, throws the
error, the error page gets control with the exception, then a doGet occurs
and the error page runs again without
the error page RUNS in the first request,
wicket is trying to redirect to it in order to make the URL bookmarkable.
Of course, nobody wants a bookmarkable error page, that would just be silly.
So I must be triggering this behavior by accident somewhere.
The error page itself just extends WebPage
/gov.usdoj.afms.esp.application.ESPApplicationErrorPage
So it seems like even though the error page RUNS in the first request,
wicket is trying to redirect to it in order to make the URL bookmarkable.
Of course, nobody wants a bookmarkable error page, that would just be
silly.
So I must be triggering
With a slight modification, that worked. I used:
return new RenderPageRequestHandler(new PageProvider(new
ESPApplicationErrorPage(ex)));
Thanks Martin!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-error-page-runs-twice-tp4668093p4668115.html
Sent from
I have a requirement that when certain kinds of exceptions are thrown, I want
to customize my exception error page. I stuffed the exception into the
requestcycle and retrieve it in the page like so:
Exception exception =
getRequestCycle().getMetaData(ESPApplication.EXCEPTION_KEY);
I watch
Hi,
It seems like the error page is being rendered after a redirect. That's why
the request cycle is empty, because it is a new one.
On Oct 25, 2014 1:42 AM, Entropy blmulholl...@gmail.com wrote:
I have a requirement that when certain kinds of exceptions are thrown, I
want
to customize my
Hi all,
we've recently moved to Wicket 6.17 from 1.4 and I'm having trouble with
NOT showing the default wicket error page when a runtime exception is
thrown from an AjaxLink.
I've set the following in the application:
getApplicationSettings().setInternalErrorPage(ErrorPage.class
and I'm having trouble with
NOT showing the default wicket error page when a runtime exception is
thrown from an AjaxLink.
I've set the following in the application:
getApplicationSettings().setInternalErrorPage(ErrorPage.class);
getExceptionSettings().setUnexpectedExceptionDisplay
We set our error page via setInternalErrorPage on IApplicationSettings in
1.6. I'd like to bury the stack trace in a comment in the rendered page in
our staging and dev environments to save time. But I have no idea how to
get the originating trace in the error page.
--
View this message
Why? You don't have access to your own log file?
On Wed, Jun 4, 2014 at 10:43 AM, Entropy blmulholl...@gmail.com wrote:
We set our error page via setInternalErrorPage on IApplicationSettings in
1.6. I'd like to bury the stack trace in a comment in the rendered page in
our staging and dev
Hi,
easiest solution is to use a custom requestCycleListener to store the
exception in a thread-local.
You can access this variable from your custom internalErrorPage.
Hope this helps
Sven
On 06/04/2014 04:43 PM, Entropy wrote:
We set our error page via setInternalErrorPage
at 10:43 AM, Entropy blmulholl...@gmail.com wrote:
We set our error page via setInternalErrorPage on IApplicationSettings in
1.6. I'd like to bury the stack trace in a comment in the rendered page
in
our staging and dev environments to save time. But I have no idea how to
get the originating
this helps
Sven
On 06/04/2014 04:43 PM, Entropy wrote:
We set our error page via setInternalErrorPage on IApplicationSettings in
1.6. I'd like to bury the stack trace in a comment in the rendered page
in
our staging and dev environments to save time. But I have no idea how to
get
object, and the examples I see online haven't been very illuminating. How
would I store and retrieve the exception from this collection by a simple
string constant?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Error-page-stack-trace-tp4666119p4666127.html
Sent from
, and the examples I see online haven't been very illuminating. How
would I store and retrieve the exception from this collection by a simple
string constant?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Error-page-stack-trace-tp4666119p4666127.html
Sent from the Users
:
http://apache-wicket.1842946.n4.nabble.com/Error-page-stack-trace-tp4666119p4666129.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
the user knowing. While I can add them to the
ignored list, I don't think this is a good design because as wicket
changes,
these exceptions can change.
I would like a way to just register my internal error page with
getApplicationSettings().setInternalErrorPage(...) but I can't because I
feature issue in JIRA for the DefaultExceptionMapper to
pass the exception to the constructor of the internal error page? Maybe it
could be a new type of UnexpectedExceptionDisplay in IExceptionSettings
called SHOW_INTERNAL_ERROR_PAGE_WITH_EXCEPTION. That way it doesn't risk
breaking existing users
wicket
can handle those without the user knowing. While I can add them to the
ignored list, I don't think this is a good design because as wicket changes,
these exceptions can change.
I would like a way to just register my internal error page with
getApplicationSettings().setInternalErrorPage
Thanks Martin. Good to know about the other option.
I'll go with Session.get().bind();
since I get the redirect to the error page. Otherwise, if I add the
RedirectPolicy.NEVER_REDIRECT to the RenderPageRequestHandler there will
still be the original value in the URL bar of the browser.
--
View
-wicket.1842946.n4.nabble.com/Cannot-get-to-desired-error-page-on-handling-RuntimeException-in-AbstractRequestCycleListener-onExce-tp4662078p4662109.html
Sent from the Users forum mailing list archive at Nabble.com
?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Cannot-get-to-desired-error-page-on-handling-RuntimeException-in-AbstractRequestCycleListener-onExce-tp4662078p4662145.html
Sent from the Users forum mailing list archive at Nabble.com
this exception?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Cannot-get-to-desired-error-page-on-handling-RuntimeException-in-AbstractRequestCycleListener-onExce-tp4662078p4662145.html
Sent from the Users forum mailing list archive at Nabble.com
and passing it to the
CustomErrorPage. Is there another means of capturing this exception?
Try with: Session.get().bind() before returning the error page *instance*.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Cannot-get-to-desired-error-page-on-handling
Here's what I've come up with.
My error page, CustomErrorPage.java, has 3 constructors:
1) no-arg
2) CustomErrorPage(PageParameters pp)
3) CustomErrorPage(Exception e)
Once I added Session.get().bind() immediately before returning the custom
error page instance I get the desired page dispatching
On Tue, Nov 5, 2013 at 10:46 PM, dgn david_nei...@hms.harvard.edu wrote:
Here's what I've come up with.
My error page, CustomErrorPage.java, has 3 constructors:
1) no-arg
2) CustomErrorPage(PageParameters pp)
3) CustomErrorPage(Exception e)
Once I added Session.get().bind() immediately
-to-desired-error-page-on-handling-RuntimeException-in-AbstractRequestCycleListener-onExce-tp4662078p4662109.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
AbstractRequestCycleListener and added it to
RequestCycleListenerCollection in Application.init() In the onException()
method there is a check for the custom exception with a dispatch to a custom
error page, otherwise the standard error page:
public IRequestHandler onException(RequestCycle cycle, Exception e
error page, otherwise the standard error page:
public IRequestHandler onException(RequestCycle cycle, Exception e) {
RepositoryProviderException rpe = Exceptions.findCause( e,
RepositoryProviderException.class );
if (rpe != null) {
return new
handling in Wicket 6.6.0 and I want
to keep the current url instead of replacing it with the url of the error
page. Anyone
Help is appreciated.
Carlos.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-preserve-current-url-in-error-page-tp4658595.html
I've got a listener that does the error handling in Wicket 6.6.0 and I want
to keep the current url instead of replacing it with the url of the error
page. Anyone
Help is appreciated.
Carlos.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-preserve-current
; rather, the
Proxy takes care of converting any underlying IOException, such as
ConnectException, into a RuntimeException.
I would like to exchange the Panel with an error message panel saying
that the service is not available rather than showing an entire error
page (which is something we
, into a RuntimeException.
I would like to exchange the Panel with an error message panel saying
that the service is not available rather than showing an entire error
page (which is something we do for other kind of exceptions, thanks to
the fabulous Wicket framework).
How could I achieve
is not available rather than showing an entire error
page (which is something we do for other kind of exceptions, thanks to
the fabulous Wicket framework).
How could I achieve something like that? Something like this can happen
during rendering time, not necessarily in onInitialize(), where I could
that the service is not available rather than showing an entire error
page (which is something we do for other kind of exceptions, thanks to
the fabulous Wicket framework).
How could I achieve something like that? Something like this can happen
during rendering time, not necessarily in onInitialize
to exchange the Panel with an error message panel saying
that the service is not available rather than showing an entire error
page (which is something we do for other kind of exceptions, thanks to
the fabulous Wicket framework).
How could I achieve something like that? Something like this can
transport layer exceptions; rather, the
Proxy takes care of converting any underlying IOException, such as
ConnectException, into a RuntimeException.
I would like to exchange the Panel with an error message panel saying
that the service is not available rather than showing an entire error
page
Hi,
is there a way to have different page expiry error pages? For my app I
would like to redirect browsing users (not logged in) to a real error
page which is plain and simple but logged in users should be redirected
to the login page on session timeout.
Thanks,
Karsten
expiry error pages? For my app I
would like to redirect browsing users (not logged in) to a real error page
which is plain and simple but logged in users should be redirected to the
login page on session timeout.
Thanks,
Karsten
...@exedio.comwrote:
Hi,
is there a way to have different page expiry error pages? For my app I
would like to redirect browsing users (not logged in) to a real error page
which is plain and simple but logged in users should be redirected to the
login page on session timeout.
Thanks,
Karsten
)
which implements #onException() to dispatch to a particular error page
depending on the exception passed in. AFAIK, this is regular Wicket
stuff and nothing terribly internal (right?).
We have a bunch of error pages which are regular WebPages with
#isErrorPage() returning true. Those
Hi,
i'm looking for a way to display the cause of a 404 send by myself on my custom
error page.
In a behavior i do
code
throw new AbortWithHttpErrorCodeException(HttpServletResponse.SC_NOT_FOUND,
Missing subsite in behavior);
/code
It is displayed in my custom error page
code
@MountPath(404
error page.
In a behavior i do
code
throw new
AbortWithHttpErrorCodeException(HttpServletResponse.SC_NOT_FOUND, Missing
subsite in behavior);
/code
It is displayed in my custom error page
code
@MountPath(404.html)
public class PageNotFound extends AbstractErrorPage {
public
?
In your application's #init()-Method, add a RequestCycleListener (e.g.
extends org.apache.wicket.request.cycle.AbstractRequestCycleListener)
which implements #onException() to dispatch to a particular error page
depending on the exception passed in. AFAIK, this is regular Wicket
stuff and nothing
in Wicket 6, which leads me to the first questions for which I found no hints
so
far:
In Wicket 1.5, there is a way to define a custom error page for
RuntimeExceptions which knows about the causing exception, by extending
WebRequestCycle and overriding the WebApplication's newRequestCycle method
Hi Robert,
I'm using a custom error page in Wicket 6 adding a
RequestCycleListener at WebApplication init like this:
/* In case of unhandled exception redirect it to a custom page */
getRequestCycleListeners().add(new AbstractRequestCycleListener() {
@Override
public
().setInternalErrorPage if the page's
class had a suitable constructor, but the proposal was voted down because
of the existence of your approach.
Cheers,
Robert
On Sat, 17 Nov 2012 15:30:33 +0100, Jordi Deu-Pons wrote:
Hi Robert,
I'm using a custom error page in Wicket 6 adding a
RequestCycleListener
Hi all
I set up an error page by calling
getApplicationSettings().setInternalErrorPage(ErrorPage.class);
in my application setup. However, I would like to redirect to a static html
page (not a wicket page) if an error occurs, preventing the wicket error
page from being shown.
I thought about
...@exedio.com wrote:
Hi all
I set up an error page by calling
getApplicationSettings().setInternalErrorPage(ErrorPage.class);
in my application setup. However, I would like to redirect to a static html
page (not a wicket page) if an error occurs, preventing the wicket error
page from being shown
.nabble.com/Fallback-for-error-page-tp4531970p4532377.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h
-pattern
dispatcherREQUEST/dispatcher
dispatcherERROR/dispatcher
/filter-mapping
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/1-5-4-error-handling-with-web-xml-error-page-issue-tp4395935p4396055.html
Sent from the Users forum mailing list archive at Nabble.com
-page
exception-typeException/exception-type
location/ErrorPage/location
/error-page
error-page
error-code404/error-code
location/ErrorPage/location
/error-page
public class ErrorPage extends WebPage
{
private
not sure if the */* matters when you mount the url.
mountPage(/ErrorPage, ErrorPage.class);
rob
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/1-5-4-error-handling-with-web-xml-error-page-issue-tp4395935p4395984.html
Sent from the Users forum mailing list
-wicket.1842946.n4.nabble.com/1-5-4-error-handling-with-web-xml-error-page-issue-tp4395935p4396055.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
Wicket show the configured error page. Inside that page you can read
the exception from the requestcycle's metadata and use it.
On Fri, Jan 27, 2012 at 9:23 PM, Chris Merrill ch...@webperformance.com
wrote:
We've replaced wicket error pages with our own, based on instructions here:
https
Hi,
In org.apache.wicket.request.cycle.IRequestCycleListener#onException()
you can return RenderPageRequestHandler with your own page that shows
the exception.
Or you can store the exception in RequestCycle's metadata and let
Wicket show the configured error page. Inside that page you can read
to
show the very useful wicket exception error page. For example, we might have
a link to it on our error page that is only turned on for development
deployments.
I have hunted around a little, but I haven't yet figured out how to get
Wicket to pass the Exception and Page to my error page - so
Dear all,
While trying to open a ModalWindow the Opera shows error page. Translated
from German it says something like “Internal Communication error. Check the
address or search for web site” In FF, IE, Safari everything works fine.
Wicket version 1.4.9
Opera 11.52
Thanks a lot in advance
On Fri, Oct 21, 2011 at 12:05 PM, Alex zeita...@googlemail.com wrote:
Dear all,
While trying to open a ModalWindow the Opera shows error page. Translated
from German it says something like “Internal Communication error. Check the
address or search for web site” In FF, IE, Safari everything
Wicket 1.5.x have fixed the problem.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-shows-Error-Page-in-Opera-tp3924738p3924885.html
Sent from the Users forum mailing list archive at Nabble.com
It is fixed in 1.4.18 too: https://issues.apache.org/jira/browse/WICKET-3615
Attila
2011/10/21 nhsoft.yhw nhsoft@gmail.com
Wicket 1.5.x have fixed the problem.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-shows-Error-Page-in-Opera
this message in context:
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-shows-Error-Page-in-Opera-tp3924738p3924885.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users
loops. That's also not
mentioned in Wicket in Action which says creating an error page is no
different than creating a normal page.
Scott
On 8/26/2011 9:15 AM, Bruno Borges wrote:
I think you must set your page as error page.
Make that change and try again.
*Bruno Borges*
(21
page. (That is how the button on the default page-expired error
page works.)
When the user first opens the web site, whether with the default or the
custom page-expired page, they see a log in page with URL
http://mydomain.com/rems/wicket/wicket/bookmarkable/com.mni.SignInPage?1.
Here
to the home page. Since we're using authorization the
user first goes to the login page so they can log in before going to the
home page. (That is how the button on the default page-expired error page
works.)
When the user first opens the web site, whether with the default or the
custom page-expired
and goes to the home page. Since we're using authorization the
user first goes to the login page so they can log in before going to the
home page. (That is how the button on the default page-expired error page
works.)
When the user first opens the web site, whether with the default or the
custom page
to
home page and goes to the home page. Since we're using authorization the
user first goes to the login page so they can log in before going to the
home page. (That is how the button on the default page-expired error page
works.)
When the user first opens the web site, whether with the default
I think you must set your page as error page.
Make that change and try again.
*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*
On Fri, Aug 26, 2011 at 1:27 AM, Scott Reed sr...@avacoda.com wrote:
A created my own PageExpiredErrorPage. There is a button that is supposed
to take the user
My apologies. I am reposting this without the distracting pseudo-formatting.
I created my own PageExpiredErrorPage. There is a button that is
supposed to take the user to the login page so they can log in (just
like the button on the default page-expired error page). /
/
When the user first
Thanks, Bruno. I added isErrorPage() just in case. The docs just say
This can help the framework prevent infinite failure loops. That's
also not mentioned in Wicket in Action which says creating an error
page is no different than creating a normal page.
Scott
On 8/26/2011 9:15 AM, Bruno
in Wicket in Action which says creating an error page is no
different than creating a normal page.
Scott
On 8/26/2011 9:15 AM, Bruno Borges wrote:
I think you must set your page as error page.
Make that change and try again.
*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*
On Fri
in case. The docs just say This
can help the framework prevent infinite failure loops. That's also not
mentioned in Wicket in Action which says creating an error page is no
different than creating a normal page.
Scott
On 8/26/2011 9:15 AM, Bruno Borges wrote:
I think you must set your page
an error page is no
different than creating a normal page.
Scott
On 8/26/2011 9:15 AM, Bruno Borges wrote:
I think you must set your page as error page.
Make that change and try again.
*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*
On Fri, Aug 26, 2011 at 1:27 AM, Scott Reedsr
, Bruno. I added isErrorPage() just in case. The docs just say
This
can help the framework prevent infinite failure loops. That's also not
mentioned in Wicket in Action which says creating an error page is no
different than creating a normal page.
Scott
On 8/26/2011 9:15 AM, Bruno Borges
A created my own PageExpiredErrorPage. There is a button that is
supposed to take the user to the login page so they can log in (similar
to the button on the default page-expired error page). /
/
When the user first opens the web site, they see a log in page with URL
/http://mydomain.com/rems
of HTML files in
apache-wicket-1.4.17/src/wicket/src/main/java/org/apache/wicket/markup/html/pages
contain XML declaration prolog. When wicket tries to show error page
exception is thrown. Top of stack trace is:
at org.apache.wicket.markup.MarkupParser.parse(MarkupParser.java:280
when you reach an error page.
I am using my own error page but also want to log the last stack trace
or exception message that created the error.
getApplicationSettings().setInternalErrorPage(ErrorPage.class);
Berlin Brown
Another question, how do I throw the default error page?
So with that request, log the exception:
public final class MyRequestCycle extends WebRequestCycle {
public WebRequestCycle(final WebApplication application, final
WebRequest request, final Response response
On Tue, Nov 23, 2010 at 3:18 PM, Brown, Berlin [GCG-PFS]
berlin.br...@primerica.com wrote:
Another question, how do I throw the default error page?
what does it mean to throw a page ?
So with that request, log the exception:
public final class MyRequestCycle extends WebRequestCycle
Is there an instance of the Default Internal Error page or should I
return null in te onRuntimeException method?
...
return new MyExceptionPage(e);
Replace with
return new org.apache.wicket.page.InternalErrorPage(e);
-Original Message-
From: Martin Grigorov [mailto:mgrigo
On Tue, Nov 23, 2010 at 3:18 PM, Brown, Berlin [GCG-PFS]
berlin.br...@primerica.com wrote:
Another question, how do I throw the default error page?
You cause an error and press the print button. You walk to your
printer and get the printout. Now you have two options:
1. cram it together
just return null and the default logic will be applied depending on your
IExceptionSettings
On Tue, Nov 23, 2010 at 3:31 PM, Brown, Berlin [GCG-PFS]
berlin.br...@primerica.com wrote:
Is there an instance of the Default Internal Error page or should I
return null in te onRuntimeException
Hi,
I have configured http error pages as per
thishttps://cwiki.apache.org/WICKET/error-pages-and-feedback-messages.html[1]
document. It works fine except I see closing the buffer error NPE
[2](see the stack trace below), on almost all the pages.
Removing
dispatcherREQUEST/dispatcher
Hi,
what is the difference between
@Override
public IApplicationSettings getApplicationSettings() {
IApplicationSettings settings= super.getApplicationSettings();
settings.setInternalErrorPage(internalErrorPage)
return settings;
}
;
}
settings.setInternalErrorPage(internalErrorPage) and
You have no acces to the exception thrown.
Perhaps this could be a RFE ?
a) Something like: ErrorWebPage extends WebPage with ErrorWebPage(Exception e)
as constructor?
b) if the annotated error Page has a constructor
We created our custom error page so any time error happens wicket redirects
to this error page , I want also want to display the exception stack trace
in this page , please tell me how to do this ?
reqauestcycle.onruntimeexception(exception e) { return new myerrorpage(e); }
-igor
On Wed, Dec 30, 2009 at 7:22 AM, tubin gen fachh...@gmail.com wrote:
We created our custom error page so any time error happens wicket redirects
to this error page , I want also want to display the exception
:
reqauestcycle.onruntimeexception(exception e) { return new myerrorpage(e);
}
-igor
On Wed, Dec 30, 2009 at 7:22 AM, tubin gen fachh...@gmail.com wrote:
We created our custom error page so any time error happens wicket
redirects
to this error page , I want also want to display the exception stack
(besides a session
expired exception), users are redirected to an error page with a form
allowing them to submit some information. Unfortunately, I need to
save the error as well, so the easy way of using
getApplicationSettings().setInternalErrorPage(ErrorPage.class) is not
sufficient because I have
a step back
and ask how I should be doing this.
I have a requirement that on an internal error (besides a session
expired exception), users are redirected to an error page with a form
allowing them to submit some information. Unfortunately, I need to
save the error as well, so the easy way
Add the following to your error page, change the error as required:
@Override
protected void configureResponse() {
super.configureResponse();
getWebRequestCycle().getWebResponse().getHttpServletResponse().setStatus(HttpServletResponse.SC_INTERNAL_SERVER_ERROR
Thanks!
On Sun, Sep 6, 2009 at 4:15 PM, Jeremy Levy jel...@gmail.com wrote:
Add the following to your error page, change the error as required:
@Override
protected void configureResponse() {
super.configureResponse();
getWebRequestCycle().getWebResponse
1 - 100 of 122 matches
Mail list logo
