You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devicemap.apache.org by Werner Keil <we...@gmail.com> on 2015/10/14 11:47:22 UTC

Portlet 3 EDR 1 with planned device support

Dear all,

JSR 362, Portlet 3.0 just filed its first EDR:
https://jcp.org/aboutJava/communityprocess/edr/jsr362/index.html

Especially Chapter 5 - Conditional Dispatching explains how implementing
containers may use this new feature to redirect visitors of the portal to
the appropriate sections, either based on their language, personal
preferences or the device they use to browse it.

We had a good discussion in the EG yesterday about the sense of e.g. the
proposed annotations. Java EE has a trend to prefer annotations over files
like properties, XML, etc. but especially changing device information
(regardless of whether you may use DeviceMap or any other solution) can
make this simple approach of only applying a regular expression to the UA
string cumbersome.

We came to a common understanding, the actual UA string was extremely
useful to provide in a standardized way. Servlet containers do so via a
Request Header (just look at all DeviceMap examples) but for Portlet
containers exposing this is not mandatory. Either directly or if necessary
via other existing API (like the CC/PP profile) one should get the UA
string. And at least the Portlet 3 RI (Apache Pluto) is pretty certain to
feed it into an appropriate DeviceMap Java component for improved device
recognition.

On the DeviceMap side it may not require much to do. Examples on how to use
it are likely going to be directly in the Portals project, but let's see
how this evolves.

Have a look at the EDR if you or your company is interested in Portlets or
uses an Enterprise Portal.

Werner