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

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...

TPP Journey through WSO2 Open Banking

Introduction 2018 is all set to be a game-changing year for European banking. The Revised Payment Services Directive (PSD2) has opened the door to new third party providers [TPPs] to connect with banks and manage finances of bank customers on behalf of them. The PSD2 regulation has mandated banks to expose their core-banking account data and payment services to authorized TPPs to consume. Thus as a bank it’s essential to have a solution which will securely expose their internal banking services to third party providers in a trusted manner. WSO2 Open Banking solution provides all required components to expose bank APIs in a well secured manner in order to become PSD2 compliant. This article explains about the importance of the TPP role in PSD2 domain, the requirements set that banks need to provide for TPPs by PSD2 regulations and how WSO2 Open Banking solution supports these requirements. From my last blog ,I have given an introduction for PSD2 and WSO2 Open Banking soluti...

How to rollback/commit processing messages from WSO2 ESB when enabled JMS transaction

This blog post describes the below use-case where WSO2 ESB 4.6.0 act as the intermediate channel in-between two JMS queues. The Use-case First messages will be de-queue to a proxy service deployed in WSO2 ESB from an queue in ActiveMQ message broker. Then inside ESB,the incoming messages will undergo with some message mediation flow and then the message will be send to another JMS queue deployed in JBoss server. Inside the ESB,following failures could be happen; a) Failures during message mediation process failure inside ESB [for example if you use dbreportmediator/lookup mediator inside mediation flow,some times failures can happen due to database connection failures] b) Message sending failure,due to endpoint is unavailability.[For example,the JBoss ...

Open Space

Search This Blog