> I think the basic idea was that, it's not I18Interceptor responsibility to create a session.
Technically it is not I18Interceptor who creates session, it is specific implementation of LocaleHandler - SessionLocaleHandler. If someone doesn't like what default LocaleHandler does, then another implementation can be used.
Typical application can have multiple packages with different interceptors stacks and actions can also have configured interceptors stacks. In order to ensure that the session is created all stacks must include createSession interceptor which is quit silly for basic configuration. I don't think adding additional flag will resolve configuration burden.
Is there any real world scenarios when someone wants to control when exactly session is created? There are stateless applications but then again they shouldn't use SessionLocaleHandler or I18Interceptor altogether.
> By the way, Aleksandr, did you mean that session creation by default fixes "WW-4943 opensymphony.xwork2.util.LocalizedTextUtil can't get i18n resources"
No. We've run into the problem I described above - first request with request_locale parameter doesn't store locale because there is no session yet.
--- Regards, Aleksandr --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
