|
From: William G. T. Jr. <wg...@ru...> - 2004-04-09 13:30:40
|
Ben Alex wrote: > Hi > > >>JSF and Portlet functionality don't have to be provided in >>one and the same release. I have been looking a bit into the >>portlet stuff and it doesn't same all that difficult. >> >>I think I'll experiment with it during the next couple of >>weeks. Major issue is the common supporting functionality >>(ContextLoader, WebAppCtx, >>Databinding) between our Web stuff and our future Portlet >>stuff (and probably also the JSF stuff). Revising the >>supporting functionality right now (or for 1.1) is not an option imo. >> >>I probably can't avoid having to copy-and-paste a lot of code >>while experimenting and since that's *not* something we want >>to have in a release, I'm afraid you're right :(. > > > Several people have previously mentioned portlets and JSF. We are trying to > decide whether to implement portlets in our next project, or just stick to > include files and/or something like Sitemesh, Tiles etc. > > Regarding portlets, there is the Pico-based Exo project > (http://exo.sourceforge.net/) and Pluto (http://jakarta.apache.org/pluto/). > Has anyone done any work on integrating portlets, JSF or projects such as > these into Spring? Would anyone be willing and have time to collaborate on > this? Rutgers is very interested in Spring support for the Portlet API in the form of a PortletDispatcher as it were. We run the uPortal[1] platform and the latest release embeds Pluto. We are just now embarking on dev cycle for new porlets that takes us thru september, if possible these new portlets would live behind a Spring PortletDispatcher. We have had some preliminary dicussions with Alef about what it might look like, and should be in a better positition to try out some ideas/code in a few weeks. later. Bill [1] http://www.uportal.org/ |