Hi,
Why you have to implement a new PortletRequestCycle? Take a look at
PortletActionRequestCycle and PortletRenderRequestCycle, and the
default getDefaultRequestCycleFactory method from
PortletApplication. As you can access all the original portlet
Action/Render Request/Responses from the default implementations,
there should not really be any reason to re-implement these.
Maybe you should check out the new portlet support from http://
svn.apache.org/viewvc/incubator/wicket/branches/wicket-1.3-portlet-
support/ ?
Janne
On 21.6.2007, at 18.46, manunabble wrote:
Hi,
I am on testing my recently-"old"-webapp, now migrated
without-code-compilation-errors to a portlet-application, and my
custom-session implementation forces me to implement
new-PortletRequestCycle, and its IRequestCycleProcessor-abstract-
method.
My code-snippet, inside my PortletApplication-extension is this:
...
protected IRequestCycleFactory getDefaultRequestCycleFactory() {
return new IRequestCycleFactory() {
private static final long serialVersionUID = 1L;
public RequestCycle newRequestCycle(Session session, Request request,
Response response) {
return new PortletRequestCycle((WicketPortletSession) session,
(WicketPortletRequest) request, response) {
public Page onRuntimeException(Page page, RuntimeException e) {
...
}
public IRequestCycleProcessor getProcessor() {
// TODO Auto-generated method stub
return null;
}
};
}
};
...
What should I do at the TODO, instead of returning null?
Thank you ;)
Cheers
--
View this message in context: http://www.nabble.com/
IRequestCycleProcessor-on-PortletRequestCycle-implementation-
tf3959585.html#a11235892
Sent from the Wicket - Dev mailing list archive at Nabble.com.
