> Why you have to implement a new PortletRequestCycle?
Because I do a custom-error-handling, as you can see in the following
fragment of the already-posted-snippet (onRuntimeException):
protected IRequestCycleFactory getDefaultRequestCycleFactory() {
...
public Page onRuntimeException(Page page, RuntimeException e) {
if (e instanceof
NTWebException) {
return new
ErrorPage((NTWebException) e);
}
return new ErrorPage(new
NTWebException(new NTWebError(new String[] {
ErrorConst.ERR$EXC }), e));
}
...
}
> Maybe you should check out the new portlet support from http://
svn.apache.org/viewvc/incubator/wicket/branches/wicket-1.3-portlet-
support/ ?
Hmmm... I was recommended not to use wicket-1.3, as it's still experimental;
I am working on wicket-1.2.6.
--
View this message in context:
http://www.nabble.com/IRequestCycleProcessor-on-PortletRequestCycle-implementation-tf3959585.html#a11252715
Sent from the Wicket - Dev mailing list archive at Nabble.com.
