Christian Haul wrote:
....
Ok, quoting the docs for request attributes for example:
Attribute names should follow the same conventions as package names. Names beginning with java.*, javax.*, and com.sun.*, are reserved for use by Sun Microsystems.
I had missed that. Observe however that there is no corresponding advice for session attributes. Now, while I think it is a very good idea to use name spaces for request attributes that are used "internally" in a webapp, e.g. within components, I think it is different for "user level" use of request attributes. With user level I mean things that you do in sitemaps, flowscripts, xsp etc. Here, IMHO, it is more natural to have attributes as global variables, without name space, and add name spaces if you want to create an isolated context. Using a default name space for attributes that are set from an output module creates a quite artificial context IMHO.
Also, IIRC, [Request|Session]AttributeOutputModule, are the only components in Cocoon, that use this kind of name spaces. The corresponding input modules, the XSP languages for attribute handling, FOM and maybe other components don't use any name spaces. IMO, following the principle of least suprise, the Cocoon components should have a consistent behaviour.
I am for consistency. Let's change default.
Vadim
