GateIn Portal Specifications

This is the place to keep references to all GateIn Portal technical specifications. Each new project feature should have one created.

GateIn 4.0

The 4.0 version is currently in development will provide for support for low latency, stateless design, parallel rendering, pluggable datastores and Portlet 3.0.

• Live demo: http://gatein-4.0.0-snapshot.acceptance4.exoplatform.org/portal/
• Implementation details: https://github.com/gatein/gatein-portal/blob/4.0.0/portal/README.md
• GitHub repository : https://github.com/gatein/gatein-portal/tree/4.0.0
• Specification:4.0 Specification

you can follow, contribute to the development or provide feedback.

GateIn 3.x

Specifications not confirmed to be delivered for any specific version yet.

• GateIn GIT Migration and Usage
• GateIn Mobile Specifications
  • GateIn Mobile Detection and Redirection
  • GateIn Mobile Redirection and Mirroring
  • GateIn Mobile Manual Redirection Selection
  • GateIn Mobile Look and Feel
  • GateIn Mobile Portlet Development
• GateIn Public Java API Specifications
  • GateIn Java API for Navigation
  • GateIn Java API for Portal Objects
  • GateIn Java API for Application Registry
  • GateIn Java API for Organization (IDM)
  • GateIn Java API for Security
• GateIn Public REST API Specification
  • GateIn REST API for Portal Objects
  • GateIn REST API for Application Registry
  • GateIn REST API for Organization (IDM)
  • GateIn REST API for Security
• GateIn Management UI Specifications
  • GateIn Organization Management UI
• GateIn Security Requirments
• GateIn Client Side
  • Resource Controller
  • Javascript Loader
  • Built-in JQuery
• Accessibility on GateIn
• GateIn Authentication Proposal
• Improved rendering engine
• CDI Support and Portlet specific scopes
• Enable/Disable users

GateIn 3.3

• GateIn GIT Migration and Usage
• GateIn and SAML2 integration for SSO authentication
• Resource Controller
• Built-in JQuery
• Accessibility on GateIn

GateIn 3.4

• GateIn Java API for Navigation
• GateIn REST API for Navigation
• Gatein Mobile Detection and Redirection
• Gatein Mobile Redirection and Mirroring
• GateIn Mobile Manual Redirection Selection

GateIn 3.5

• GateIn Java API for Portal Objects
• GateIn Java API for Application Registry
• GateIn REST API for Portal Objects
• GateIn REST API for Application Registry

Other documents

Documents that are assigned to proper version yet, need to be reworked into proper format or we just want to keep track

• GateIn REST API

Specification Template

Elements that each specification should contain at least (can contain more):

• Status
  • the current status: free form status like work in progress, implemented, etc..
• Owner
  • who is responsible for editing document and updating it with feedback
• Introduction / Description / Use case
  • describe the problem to solve and the goals. It can also be very short example or description of how the feature would be used (by developer or end user)
• Solution
  • the solution to solve the problem with an high level view
• Specification
  • what should be done to solve the problem, can mix functional and technical steps, free form content
• References
  • blogs, docs, screencasts and etc.