> 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?
Of course I am not sure, I have to achieve running the portlet in the
portlet-container first. That code worked fine as a WebApp, so it's just
inherited in this portlet after the webapp-2-portlet-transformation, which
consists, in most cases, swapping from WebPage to PortletPage and
refactoring some code fragment (You and me had a conversation about this
various month ago, remember?).
So, you are the expert in wicket-vs-portlet, you might tell why are you
doubting that code snippet might not work!?
> 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.
Well, so you suggesting me to migrate the application to 1.3... should I
guess that portlet-support for wicket is only continued in 1.3, but not in
1.2 anymore?
Appart from this, I am wondering: if wicket-portlet-api is experimental,
both 1.2 and 1.3, why was it distributed and released as
non-explicitly-expermintal some month ago at wicket's site? I began testing
wicket because of its apparent stable release and support on portlets when
deciding which web-front-tech to use in this project. This is not complaint,
it's an obvious question, but with not an obvious answer, I am afraid.
--
View this message in context:
http://www.nabble.com/IRequestCycleProcessor-on-PortletRequestCycle-implementation-tf3959585.html#a11286139
Sent from the Wicket - Dev mailing list archive at Nabble.com.
