+1 for replacing the legacy portlet integration by your new xwiki-portlet modul, until we decide for a long term strategy re the container module.
We would need to fix the issues relative to URL in AJAX response (livetable, etc.) before 2.4 final. Could be interesting to create a distribution for this portlet integration. For example, based on http://www.jboss.org/gatein/portletcontainer.html. It could be used for running some integration tests as well. One last thing, and probably the most important, is that we need to think how the XWiki UI should be envisaged when running in portlet, in terms of menus, styles, configuration (shared settings), etc. We should open a separate design discussion on this topic. Jerome. > Hi devs, > > You can find here > http://dev.xwiki.org/xwiki/bin/view/Drafts/PortletIntegration a draft > regarding the portlet integration. > > We need to decide what's the best approach. For short term I think the > loosely-coupled integration solution is the best as it requires less > changes to the core. The current implementation is in > http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-portlet/ and I > propose to move it to platform/xwiki-portlet before 2.4M2. > > For long term, when we'll have the new model in place, we might consider > the tightly-coupled integration solution as it seems to be more clean > and it follows the component way. It won't be easy to implement though. > > WDYT? > > Thanks, > Marius > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
