More precise control over isolation of servlet context and session attributes

[GoogleCodeExporter]

Applies as of r4719

Currently, if an attribute is added to the ServletContext using the
ModuleAwareWrapperServletContext, then it is automatically visible to other
modules.

The strategies for this should be configurable:
- by default, an attribute saved in ServletContext should be saved using
the key which uses the module name as a prefix.
- if the attribute is saved using shared:name, then it should be saved
under the raw key, which allows it to be visible to other modules using the
raw name.

Original issue reported on code.google.com by philzoio...@googlemail.com on 26 Oct 2009 at 2:31

[GoogleCodeExporter]

Note that this should also apply to session and request attributes too.

Original comment by philzoio...@googlemail.com on 18 Nov 2009 at 9:10

• Changed title: More precise control over isolation of servlet context, request and session attributes

[GoogleCodeExporter]

Modified to only include context and session attributes.

Original comment by philzoio...@googlemail.com on 3 Dec 2009 at 2:54

• Changed title: More precise control over isolation of servlet context and session attributes

[GoogleCodeExporter]

Fixed with r4966

Note that this only applies when using ModuleProxyServlet or ModuleProxyFilter

Original comment by philzoio...@googlemail.com on 5 Dec 2009 at 7:23

• Changed state: Fixed