Generally any portal implementation must be based on JSR 168 and JSR 286 standards and all portal must have implemented these specification to being as portlet technology based portal.
In each specification new features was introduced and those were implemented in the portals. Same way JSR 362 added few more new specification and improvements to the portals.
JSR 362 / Portlet 3.0
JSR 362 have added new features and improvements for portlet implementation. All JSR 286 specification already covered in JSR 362 besides it added few more new specifications and improvements
The following are the specifications
Support JEE 7 features in Portlets
Resources sharing among portlets
Better client side support
Improved the mobile devices support
Optimise Java Server Faces (JSF) support
Support for WSRP future specification
Web Socket Support
Support Open Social Standards
Improvements in Portlet Event based Communication
Resources sharing among portlets
Better client side support
Improved the mobile devices support
Optimise Java Server Faces (JSF) support
Support for WSRP future specification
Web Socket Support
Support Open Social Standards
Improvements in Portlet Event based Communication
Support JEE 7 features in Portlets
JEE 7 come up with many new features in each JSR specification. JSR 362 will covered the JEE 7 features.
Following is link will show you all features added in JEE 7
Resources sharing between portlets
Generally in portlet communication we can exchange data among the portlets not resources such as files, documents and images. JSR 362 implemented resource sharing between portlets such a way we can share resources between portlets.
To know more about what JSR 286 covered you can have look at Inter Portlet Communication.
Improved the mobile devices support
JSR 362 have brought some of improvements to support mobile clients so that portal look and feel will be good in mobile devices too.
Better client side support
As we discussed User Interface is major challenge in portlet technology so new specification bring some of new feature to improve client support. It’s like bootstrap support and html5 support.
Optimise Java Server Faces (JSF) support
Generally to work web framework in portals then web framework vendors need to provide portlet bridges so that web application lifecycle will be transformed to portlet lifecycle.
But as for specification portlet technology default support for Java Server Faces in the past specification and some of the things was improved in the new specification. So that we can easily use JSF framework based portlets in portals.
Liferay already have implemented and have given support to develop JSF based portlets and run into Liferay Portal. Now Liferay considered JSR 362 and they stared implementing these features in Liferay JSF implementation.
Support for WSRP future specification
Web Services for Remote Portlets (WSRP) is standers to share portlet with other portal platforms. Its presentation oriented web service so that we can directly display portlets in other portal platforms.
Assume if we have some portlet running in Liferay portal and other portlet in WebSphere portal. If we want to share Liferay portlets with WebSphere or WebSphere portlets with Liferay then WSRP will help you to share portlets among different portals rather than re-implements the same portlets in other platforms.
Generally through web services we can only share data among different platforms not presentation or user interface but WSRP will also share presentation along with data so that we don’t need to develop any presentation.
JSR 168 have supported WSRP 1.0 specification and JSR 286 have supported WSRP 2.0 specification. Now JSR 362 is supporting WSRP 3.0 specification.
Web Socket Support
Web Socket is protocol and it allows communication between client and servers with single TCP connection. Its possible to establish a continuous full-duplex connection stream between a client and a server. This will help in streaming and also if something updated in server it will automatically push to the client. JSR 362 will support this kind of communication and really its big asset to the portals and its portlets.
Example:
Support Open Social Standards
Open Social is strands which will give us to created web applications using HTML, CSS and Java Script. It’s easy to create dynamic application using open social standards and its consumed REST bases web services to create dynamic web application. We can easily build some widgets or portlet using these standards.
Liferay already have introduced in Liferay 6.2 release to created Open Social Widgets in Liferay portal.
Improvements in Portlet Event based Communication
Portlet communication can happened in different ways and one of the communication model is Event based. JSR 362 have improved some of the things in Event based communications.
Sources:
Author
0 comments:
Post a Comment