niedz., 6 sty 2019 o 21:10 Aleksandr Mashchenko <amashche...@apache.org> napisał(a): > 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.
Fair point, I think reverting to the previous behaviour is a good idea, what I mean by that is "if store == SESSION" let's create a session. As I'm going to drop 2.5.19 in case of the logging issue we can also revert this, Aleksandr do you want to prepare a PR as you have a test case at hand? Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
