> So next step is someone with experience in portlets to try to create a > separate project with the classes > from org.apache.wicket.protocol.http.portlet and whatever else is > needed.
Probably mostly a WicketPortletFilter to be used in front of WicketFilter that builds on the portlet-oriented code from the 1.4.x branch and sets up what is needed if it detects a portlet request? - Tor Iver