On 22.6.2007, at 16.53, manunabble wrote:
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));
}
...
}
Are you sure that is going to work on your portlet container?
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.
Yeah, Wicket 1.3 is in beta and it's portlet support is experimental,
but the portlet support of 1.2 is as much experimental: http://
svn.apache.org/viewvc/incubator/wicket/branches/wicket-1.2.x/wicket/
src/main/java/wicket/protocol/http/portlet/WARNING.README?view=co .
If I would have to do some portlet stuff now, I would choose Wicket 1.3.
Janne
