Scott/all, Following your concerns in the call about a demo portal taking too much time off other (Spec Lead) duties, I fully understand that. Being a Spec Lead for another JSR despite others helping, a large portion is done by myself and a few other fairly active EG members;-)
Plus I try to keep DeviceMap active and alive, especially hoping to get more community input, given we see at least a new mobile device every week or more these days. You mentioned the pre-packaged prototype was a Windows package. So, is it so far only known to work on Windows? To gather device data, it won't be necessary to use Pluto 3 yet anyway. Following https://portals.apache.org/pluto/v20/getting-started.html sounds sufficient, and we already got a working Tomcat 7 on Devicemap VM, so that should be no big deal. The main idea for using a portal is of course allowing users to log in and confirm some sort of disclaimer, that it's their device and not some copy of other information they provide us with. As V3 progresses, I could think of upgrading that and either on the DeviceMap VM or elsewhere, a demo of device-driven conditional dispatching would certainly be cool, too. Being just an Individual and with other responsibilities, I would not dare to take charge of an entire demo myself, but I'd be happy to help with it in any suitable Apache project. Regards, Werner On Fri, Nov 27, 2015 at 2:25 PM, Martin Scott Nicklous < scott.nickl...@de.ibm.com> wrote: > Hi, > > As you know, I've been working on the Portlet Specification V3 reference > implementation hosted at Apache Pluto in order to make it conform to the > portlet spec Draft #1. I I have much of the basis work needed to implement > the annotation support finished. I think this is a big milestone, so I > wanted to let you all know. The code is available in the Pluto repository > and I have prepared a predeployed package for Windows containing Pluto > along with some sample portlets and have posted it to the project download > site. > > I can demo this in the next EG meeting on Tuesday, if desired. > > New functionality compared to Pluto 2.1 (master branch): > > * Rewrote much of the portlet.xml reading code to prepare for > configuration through annotations > * Change the initialization to use dynamic servlet deployment for the > portlet servlets > * Use of maven-portlet-plugin to modify the web.xml file in a portlet war > is no longer needed > * The web.xml file in portlet archives is now optional > * Integrated the Portlet Specification v3.0 Draft 1 level of the Portlet > API > * Implemented the new state handling support > * RenderParameters, ActionParameters, ResourceParameters, etc. > * Implemented the portlet hub client-side support > * Implemented Partial Action processing > * Implemented PAGE_STATE attribute for the resource request for partial > action support > * Implemented header phase support according to the spec > * For V3 portlets with HeaderRequest and HeaderResponse > * For V3 portlets markup written to the output stream is added to the > document HEAD section > * For V2 portlets with RENDER_PART support > * Markup written to the output stream or added through addProperty(String, > Element) is validated > * Can only add tags that are allowed in the HEAD section > * Implemented PortletResponse#addProperties & PortletResponse#setProperties > * For V2 & V3 portlets HTTP headers and cookies can be set > * HTTP Headers are allowed / disallowed according to request > * Implemented ActionResponse#getRedirectURL() > * Implemented portlets to demo the new functionality > * Moved Pluto to Servlet API v3.1, must be deployed on Tomcat 8 > * Various bug fixes > * Added CDI support > * The appropriate CDI package is installed on Tomcat during Pluto > installation > > Next Steps: > * Add configuration through annotation > * Add bean portlet support > * Bring the Pluto tag library up to v3 level (actually, this is not yet > addressed in the spec, so I would need to do that, too) > > Windows package: > > https://java.net/projects/portletspec3/downloads/download/V3Prototype/V3Prototype-20151127.zip > > Source code If you've already cloned the Pluto git repo: > > git pull origin V3Prototype > git checkout V3Prototype > > Source code if you still need to clone Pluto: > > git clone https://git-wip-us.apache.org/repos/asf/portals-pluto.git > git checkout V3Prototype > > Let's see if I can get done by Christmas ... :-) > > Mit freundlichen Grüßen, / Kind regards, > Scott Nicklous > > WebSphere Portal Standardization Lead & Technology Consultant > Specification Lead, JSR 362 Portlet Specification 3.0 > > IBM Deutschland Research & Development GmbH / Vorsitzender des > Aufsichtsrats: Martina Koederitz / Geschäftsführung: Dirk Wittkopp > Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, > HRB 243294 > >
