PS: https://issues.apache.org/jira/browse/TOMEE-1357
Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-22 10:02 GMT+02:00 Romain Manni-Bucau <[email protected]>: > Hi > > don't forget to say how you deploy to TomEE your app. If just dropping > the war in webapps/ it should work. > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-09-21 22:11 GMT+02:00 Andy Gumbrecht <[email protected]>: >> Hi Thorsten, >> >> What version are you using? Please create a JIRA here to help us track this >> issue: https://issues.apache.org/jira/browse/TOMEE >> >> Thanks for your time, >> >> Andy >> >> >> On 21/09/2014 18:04, Thorsten Meinl wrote: >>> >>> Hi, >>> >>> I used to disable session persistence in the web application's >>> META-INF/context.xml file by specifying "<Manager pathname='"" />'. This >>> works as expected in plain Tomcat but, TomEE doesn't seem to respect >>> this setting. Other values (e.g. parameters) from the webapp's >>> context.xml are used, but not the Manager. It's only possible to disable >>> session persistence via the server's global conf/context.xml. This us a >>> bit unfortunate because it affects all running web applications and some >>> may still want to use session persistence. Is this a bug or am I missing >>> something? >>> >>> Thanks, >>> >>> Thorsten >>> >> >> >> -- >> Andy Gumbrecht >> https://twitter.com/AndyGeeDe >> http://www.tomitribe.com >>
