RL054 Scott Nicklous's guest appearances

RL054 Scott Nicklous

Radio Liferay

Michael Young

Juan Gonzalez

Brian Chan

Dennis Ju

Jorge Ferrer

Kristoffer Onias

Victor Ware

James Falkner

Neil Griffin

Raymond Augé

Jens Bruhn

Thomas Schweiger

Bryan Ho

Stian Sigvartsen

Brett Swaim

OwlTail

	In this episode, recorded at Liferay's Devcon 2015 in Darmstadt/Germany, I'm talking to Scott Nicklous and Neil Griffin. Scott is the specification lead for JSR-362 - otherwise known as the Portlet Specification 3.0 - and Neil serves as Liferay's representative on the expert group. 	Here are some of the topics that we talked about:   JSR 362 page with all the latest and current information (spec, prototype implementation and javadoc) 		The expert group 		JSR 286 portlets will run unchanged on JSR 362 (runtime and compiletime compatibility) 		My repeat favourite statement about frameworks in the web world. 		JSR 362 and its impact on UI, there's a Client-Side standard (on ECMA script) for the first time in the portlet spec 		The big question: When will it be done? (Some time 2016) 		Early Draft Review Spec available, ~80-90% of content is expected to be there (That's the statement from Devcon, in October 2015) 		Reference Implementation (to prove that the spec can be implemented) and TCK still missing (again, October 2015) 		Reference Implementation and TCK will be implemented under the Apache Pluto project, help required 		New Features include Bean-Portlet-Approach (portlet methods specified through Annotations in any Managed Bean), portlet.xml file no longer required if Annotations used 		specifies a JS API despite being a JSR, which covers traditionally only Java 		Dependency to JavaEE: Minimum is JavaEE 7, e.g. Servlet 3.1 etc. 		Portlet Spec is not part of the JavaEE, but extends some of its elements. 		CDI  JSR 378: Portlet 3.0 bridge for JSF (where Neil is the spec lead), being built in parallel with JSR-362 		Multiplatform Support, Websocket, Devices 		The E-Mail Archive of the specification process is public - contribution and comments are very welcome

In this episode, recorded at Liferay's Devcon 2015 in Darmstadt/Germany, I'm talking to <a href="https://www.xing.com/profile/MartinScott_Nicklous" rel="nofollow" target="_blank">Scott Nicklous</a> and <a href="https://www.liferay.com/web/neil.griffin" rel="nofollow" target="_blank">Neil Griffin</a>. Scott is the specification lead for JSR-362 - otherwise known as the Portlet Specification 3.0 - and Neil serves as Liferay's representative on the expert group. 	Here are some of the topics that we talked about: <ul> <li> <a href="https://www.jcp.org/en/jsr/detail?id=362" rel="nofollow" target="_blank">JSR 362 page</a> with all the latest and current information (<a href="https://java.net/projects/portletspec3" rel="nofollow" target="_blank">spec</a>, <a href="https://java.net/projects/portletspec3/downloads/directory/V3Prototype" rel="nofollow" target="_blank">prototype implementation</a> and <a href="http://msnicklous.github.io/portletspec3/apidocs/index.html" rel="nofollow" target="_blank">javadoc</a>)</li> <li> 		The expert group</li> <li> 		JSR 286 portlets will run unchanged on JSR 362 (runtime and compiletime compatibility)</li> <li> 		My repeat <a href="http://geek-and-poke.com/geekandpoke/2014/11/8/frameworks" rel="nofollow" target="_blank">favourite statement about frameworks</a> in the web world.</li> <li> 		JSR 362 and its impact on UI, there's a Client-Side standard (on ECMA script) for the first time in the portlet spec</li> <li> 		The big question: When will it be done? (Some time 2016)</li> <li> 		Early Draft Review Spec available, ~80-90% of content is expected to be there (That's the statement from Devcon, in October 2015)</li> <li> 		Reference Implementation (to prove that the spec can be implemented) and TCK still missing (again, October 2015)</li> <li> 		Reference Implementation and TCK will be implemented under the Apache Pluto project, help required</li> <li> 		New Features include Bean-Portlet-Approach (portlet methods specified through Annotations in any Managed Bean), portlet.xml file no longer required if Annotations used</li> <li> 		specifies a JS API despite being a JSR, which covers traditionally only Java</li> <li> 		Dependency to JavaEE: Minimum is JavaEE 7, e.g. Servlet 3.1 etc.</li> <li> 		Portlet Spec is not part of the JavaEE, but extends some of its elements.</li> <li> 		CDI</li> <li> <a href="https://www.jcp.org/en/jsr/detail?id=378" rel="nofollow" target="_blank">JSR 378</a>: Portlet 3.0 bridge for JSF (where Neil is the spec lead), being built in parallel with JSR-362</li> <li> 		Multiplatform Support, Websocket, Devices</li> <li> 		The E-Mail Archive of the specification process <a href="https://java.net/projects/portletspec3/lists" rel="nofollow" target="_blank">is public</a> - contribution and comments are very welcome</li></ul>

RL054 Scott Nicklous and Neil Griffin on JSR 362 - Portlet 3.0