Differences between revisions 1 and 2
Revision 1 as of 2014-03-07 22:58:44
Size: 1701
Editor: DavidTaylor
Comment:
Revision 2 as of 2014-04-07 20:51:51
Size: 1683
Editor: Woonsan Ko
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
  - Reverse proxy module to be runnable in both portlet env and servlet (non-portlet) env
  - Easier and more flexible content rewriting module
  - More intuitive reverse proxy mapping configuration
  - More componentized module structure and usage of an IoC container
  - More extensible SSO integration support
  - Other possible extensibility (e.g, to support custom ESI processing component)
  * Reverse proxy module to be runnable in both portlet env and servlet (non-portlet) env
  * Easier and more flexible content rewriting module
  * More intuitive reverse proxy mapping configuration
  * More componentized module structure and usage of an IoC container
  * More extensible SSO integration support
  * Other possible extensibility (e.g, to allow to inject a custom ESI processing component)
Line 12: Line 11:
  - 2.0 may break backward compatibility in both code and configuration
  * 2.0 may break backward compatibility in both code and configuration
Line 15: Line 13:
  3.1. Branching apa-webcontent-1.x and use trunk for 2.x.
  3.2. Maven project restructuring
    - content-rewriter : content rewriting module decoupled with
 portlet-api
    -
reverse-proxy : reverse proxy module decoupled with portlet-api
    - portlets : portlet classes
    - war : (portlet) web application
  3.3. Change package name structure (org.apache.portals.application.webcontent2.**)
  3.4. Componentizing reverse proxy module
    - use spring framework or anything else as dependency injection?
  3.5. Improve reverse proxy mapping configuration
    - consider using YAML instead of properties file
  3.6. Designing Content Rewriter module and evaluating 3rd party solutions (e.g, htmlcleaner)
  3.7. Implementing Content Rewriter module
with componentization
  3.8. Evaluating open (de facto) SSO standards/technologies to possibly integrate
  3.9. Provide external SSO integration API with an example
  3.10. Considering other possible
extensibility
  1. Branching apa-webcontent-1.x and use trunk for 2.x.
  2. Maven project restructuring
    * content-rewriter : content rewriting module decoupled with portlet-api
    *
reverse-proxy : reverse proxy module decoupled with portlet-api
    * portlets : portlet classes
    * war : (portlet) web application
  3. Change package name structure (org.apache.portals.application.webcontent2.**)
  4. Componentizing reverse proxy module
    * use spring framework or anything else as dependency injection?
  5. Improve reverse proxy mapping configuration
    * consider using YAML instead of properties file
  6. Designing Content Rewriter module and evaluating 3rd party solutions (e.g, htmlcleaner)
  7. Implement
ing Content Rewriter module with componentization
  8. Evaluating open (de facto) SSO standards/technologies to possibly integrate
  9. Provide external SSO integration API with an example
  10. Considering other possible extensibility

Apache Portals Web Content Application 2.x Proposal

1. Objectives

  • Reverse proxy module to be runnable in both portlet env and servlet (non-portlet) env
  • Easier and more flexible content rewriting module
  • More intuitive reverse proxy mapping configuration
  • More componentized module structure and usage of an IoC container
  • More extensible SSO integration support
  • Other possible extensibility (e.g, to allow to inject a custom ESI processing component)

2. Assumptions

  • 2.0 may break backward compatibility in both code and configuration

3. Tasks

  1. Branching apa-webcontent-1.x and use trunk for 2.x.
  2. Maven project restructuring
    • content-rewriter : content rewriting module decoupled with portlet-api
    • reverse-proxy : reverse proxy module decoupled with portlet-api
    • portlets : portlet classes
    • war : (portlet) web application
  3. Change package name structure (org.apache.portals.application.webcontent2.**)
  4. Componentizing reverse proxy module
    • use spring framework or anything else as dependency injection?
  5. Improve reverse proxy mapping configuration
    • consider using YAML instead of properties file
  6. Designing Content Rewriter module and evaluating 3rd party solutions (e.g, htmlcleaner)
  7. Implementing Content Rewriter module with componentization
  8. Evaluating open (de facto) SSO standards/technologies to possibly integrate
  9. Provide external SSO integration API with an example
  10. Considering other possible extensibility

4. Possible candidate plans

  • 2.0 (Task 3.1 to 3.5)
  • 2.1 (Task 3.6 to 3.7)
  • 2.2 (Task 3.8 to 3.9)
  • 2.3 (Task 3.10 ~ )

Applications/WebContentProposal (last edited 2014-06-30 22:14:56 by Woonsan Ko)