Hi,Wicket's native portlet support is still a work in progress, but so far it works fine. So far I have only done some testing with it (see wicket-portlet-examples subproject), but I'm expecting to start a real world application based on it in a month or two. So far I have tested running the
Does anyone have experience using Wicket with a Portal solution? We
have a set of requirements that are very nicely satisfied with a CMS
framework. It might help to reduce effort if we utilized the platform,
and design the elements in the UI featuring dynamic content as portlets
(JSR 168). We'd
Janne will try to answer some more later, but JSR 168 is support is
built in Wicket in a basic version. It uses a page per portlet, so if
you have four wicket portlets in your portal, you'll have four wicket
pages. The match is there.
I think it basically works, but is a bit rough in the sense
