Isolating Servlet dependencies could potentially ease portlet support, too.
It won't be an easy task, though. Some of the main classes of the framework, like WicketFilter, are deeply coupled to the Servlet API. But I'm not sure if the benefits out-weight the cost of doing the changes and probably breaking (once more) compatibility with older versions. On Thu, Jan 17, 2013 at 8:53 PM, Michael Mosmann <[email protected]> wrote: > What i want to know: Is there any chance, that this can succeed? This will > change wicket in many places, and i understand, that nobody will accept > this as an wicket 6.x.y "improvment". Maybe this is the wrong direction, > maybe the right thing to early, not the best thing we could do now... >
