jsr340-experts@servlet-spec.java.net

[jsr340-experts] Multi-tenancy and web container

From: Rajiv Mordani <rajiv.mordani_at_oracle.com>
Date: Fri, 11 Nov 2011 18:33:26 -0800

As part of Java EE 7 one of the areas of focus is - multi-tenancy / PaaS
style deployments of applications. As I have sent previously to the EG
the current proposal for Java EE Platform as for PaaS as it stands today
is described at [1].

I would like to start the discussion around the requirements for what it
means for the Web Container. In particular for the multi-tenancy aspect
in a PaaS environment, what are the customizations that each tenant can
provide and how they will be reflected in the spec. Some initial
thoughts that I had are listed below -

  * URL mapping
  * init-params
  * Customization of resources to be loaded per tenant - style sheets,
    jsps, error pages etc
  * Customized DataSources and other resource-refs per tenant
  * session related configuration (timeout, tracking mode, isHttpOnly,
    security setting etc)
  * security roles constraints per tenant (should we allow every tenant
    to change this for the application)
  * keystores, certs for an application (can we even do this per tenant)

What else am I missing here?

[1] http://java.net/downloads/javaee-spec/PaaS.pdf

- Rajiv