Re: No container in actions after upgrading to 2.5.13

2017-09-14 Thread Yasser Zamani
Do last three exceptions occur in same time, in one action call (I think because of first word of their lines 73709, 73712 and 73716 and their same thread name "http-nio-8082-exec-9") ? If so, it means you want to evaluate Using version 2.5.13 on Tomcat 8.0.21. > > I’ve attached it to this mes

Re: Security vulnerability process for EOL versions

2017-09-14 Thread Lukasz Lenart
2017-09-14 12:05 GMT+02:00 Michael Smith : > A follow on question. > > When would we expect 2.3 to become EOL? No exact plans, probably we will switch to JDK7 as we have problems supporting 2.3.x on JDK6 (lack of tools) but this will be then 2.4.x still keeping focus on security updates. Regards

Re: Security vulnerability process for EOL versions

2017-09-14 Thread Michael Smith
A follow on question. When would we expect 2.3 to become EOL? Thx Mike On 14 September 2017 at 08:13, Lukasz Lenart wrote: > 2017-09-13 18:57 GMT+02:00 Lehmer, Jason : > > In cases where the Struts community is notified or discovers a security > vulnerability in a supported version, does the

Re: No container in actions after upgrading to 2.5.13

2017-09-14 Thread LAW Andy
> On 14 Sep 2017, at 09:48, Lukasz Lenart wrote: > > You are not the first person who complains about missing container ... > I wonder if we should add a fallback though. > >if (container == null) { >LOG.warn("Container is null, action was created manually? > Fallback to Acti

Re: No container in actions after upgrading to 2.5.13

2017-09-14 Thread Lukasz Lenart
You are not the first person who complains about missing container ... I wonder if we should add a fallback though. if (container == null) { LOG.warn("Container is null, action was created manually? Fallback to ActionContext"); container = ActionContext.getContext()

Re: Security vulnerability process for EOL versions

2017-09-14 Thread Lukasz Lenart
2017-09-13 18:57 GMT+02:00 Lehmer, Jason : > In cases where the Struts community is notified or discovers a security > vulnerability in a supported version, does the evaluation process include > identifying unsupported versions that may be impacted as well? I realize the > recommendation will li