Portlet Standards

This is a topic researched by me for the literature survey of our final year group project.

Overview

Over the past few years, portals have evolved rapidly in the Internet space. They have helped businesses aggregate secure and personalized content and applications to the Web.Portlets used by portals function as pluggable user-interface components that provide a presentation layer to information systems.

In the early days of portal development, little emphasis was placed on component interoperability or reuse. Why? Because portlet APIs for development or customization at that time were limited to a single portal product only.

To overcome these problems, the Portlet Specification was started to provide interoperability between portlets and portals.

Portlet Specification defines the contract between a compliant portlet container and portlets. It defines a common Portlet API and infrastructure that provides facilities for personalization, presentation, and security. This standardization allows for portability of portlets between portal implementations.

Advantages

• Support multiple portal products. The compliant portlets can be deployed to all compliant portal frameworks without extensive engineering changes.

• Code re-usability.

• Creates a wider market opportunity for portal tools: IDE’s, test tools, performance measurement tools and reporting interfaces.

• Support all compliant portal servers without additional engineering and support costs.

Mainly there are two categories for portlet standards.

1. Java Portlet Specification (JSR168, JSR286)

2. WSRP

Comments

Convert an InputStream to XML

For that we can use DocumentBuilder class in java. By using the method parse(InputStream) ; A new DOM Document object will return. InputStream input; DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); DocumentBuilder parser = factory.newDocumentBuilder(); Document dc= parser.parse(input); In the above code segment,by using the created Document object,the corresponding XML file for the inputStream can be accessed. References: http://www.w3schools.com/dom/dom_intro.asp http:// download.oracle.com/javase/1.4.2/docs/api/javax/xml/parsers/DocumentBuilder.html

Concat two xml values with XSLT

The use-case described in this blog-post,is there's an WSO2 ESB node setup to proxy an incoming message to a particular back-end endpoint. Before delivering the message to the back-end endpoint,from the ESB node itself,this incoming message need to processed and change its inside xml payload format. For eg: Below is the incoming message <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"> <OwnerData> <Name>John Smith</Name> <openedDate>12/12/80</openedDate> <quality>good</quality> </OwnerData> <CinemaHallData> <rows>100</rows> <seats> <seat>50</seat> <seat>60</seat> </seats> </CinemaHallData> </CinemaHall> This message need to be changed as below; <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"...

Passing end-user details from client to real backend endpoint via JWT token

In real-world business system,WSO2 API Manager useful on exposing company APIs, in a secured and controlled manner with the features provided by APIManager as; OAuth support [To secure API invocations] Throttling support [To control API invocations] Monitoring support [To track API usage] More technically what happening is when a user sends a particular API request,it will goes to WSO2 APIManager node and from there,the request will route to the real implemented back-end endpoint of the particular API and get back the response and returned it to the API invoked user. There can be a use-case,that this back-end endpoint may expect the details of API invoked user as to pass those details to some internal company usage as; Additional authentication/authorization Track usage data from an internal system. So how to support above requirement from WSO2 AM. There comes the use of JSON Web Token[JWT] implementation done inside WSO2 AM. JWT is a means of representing claims to...

Open Space

Search This Blog