Hi,
Check org.apache.wicket.settings.ExceptionSettings#setAjaxErrorHandlingStrategy
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Fri, Sep 26, 2014 at 1:25 PM, Wayne W waynemailingli...@gmail.com
wrote:
Hi all,
we've recently moved to Wicket 6.17 from 1.4
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 on
Btw, this is what you want:
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/request/cycle/AbstractRequestCycleListener.html#onException%28org.apache.wicket.request.cycle.RequestCycle,%20java.lang.Exception%29
Add your own IRequestCycleListener (AbstractRequestCycleListener)
On Wed, Jun 4, 2014 at 5:34 PM, Sven Meier s...@meiers.net wrote:
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.
Prefer RequestCycle's metadata instead.
Hope this
The meta data facility looks intriguing but is a bit confusing. How is this
supposed to work? I was expecting something like a map, but the key has to
be this abstract object that takes an arrya of entry objects? And each
entry object demands reference back to it's key? This is a confusing
See
declare a key:
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/request/cycle/PageRequestHandlerTracker.java#L40
set a value:
Nevermind, I figured out from other examples that they tend to share the key
in a static constant so that it becomes the object identity that allows you
to access the meta data object. I wonder if that is really the intended
use, but intended or not, it works.
--
View this message in context:
Hi,
what is the difference between
@Override
public IApplicationSettings getApplicationSettings() {
IApplicationSettings settings= super.getApplicationSettings();
settings.setInternalErrorPage(internalErrorPage)
return settings;
}
Hi,
what is the difference between
@Override
public IApplicationSettings getApplicationSettings() {
IApplicationSettings settings= super.getApplicationSettings();
settings.setInternalErrorPage(internalErrorPage)
return settings;
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
what is the difference between
@Override
public IApplicationSettings getApplicationSettings() {
IApplicationSettings settings= super.getApplicationSettings();
settings.setInternalErrorPage(internalErrorPage)
return settings;
12 matches
Mail list logo