There are some usecases in which one needs such an access, for me the most important one is sharing information across the context.
For example, if one decides to use the same hivemind registry tapestry uses (and not spring or another IoC container) for some front-end services, and want's to share those services in the context.
I would like to enhance this feature request and ask to externalize all state obejct access to static methods:
e.g, in the session state manager, add:
public static Object getStateObject( HttpSession session , String tapestryServletName, String stateName );
or in the context state manager, add:
public static Object getStateObject( ServletContext ctx, String tapestryServletName , String stateName );
or in case of registry:
public static Registry getHivemindRegistry( ServletContext ctx, String tapestryServletName );
BTW, I don't think static-storing of the registry is possible due to clustering issues, we must always use the ServletContext.
Currently, it is alsa possible to access the registry: copy the key tapestry uses to store the registry in the context, add the servlet name, and peek it - but this is not very "nice"...