[ https://issues.apache.org/struts/browse/WW-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin McCann updated WW-2240: -------------------------------- Attachment: improvedLogging.patch Please at least wrap the log call so that the file upload interceptor can be used on most logging levels before 2.1.4. I'd commit the fix myself if I had svn access. I know this patch does not fix the root issue, but it's not a bad thing to do anyway for performance reasons. And more importantly, this is a pretty serious bug and a 2.1.1 release should include a fix at the very least for the logging issue which would at least provide a workaround of downgrading the log level for this interceptor. > FileUploadInterceptor causes null pointer exception > --------------------------------------------------- > > Key: WW-2240 > URL: https://issues.apache.org/struts/browse/WW-2240 > Project: Struts 2 > Issue Type: Bug > Components: Core Interceptors > Affects Versions: 2.1.0 > Reporter: Benjamin McCann > Fix For: 2.1.4 > > Attachments: improvedLogging.patch, null context.jpg > > > Using struts2-core-2.1.0-SNAPSHOT-20071003.jar, I received the following: > java.lang.NullPointerException > at > org.apache.struts2.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:277) > at > com.opensymphony.xwork2.DefaultActionInvocation$1.doProfiling(DefaultActionInvocation.java:229) > at > com.opensymphony.xwork2.DefaultActionInvocation$1.doProfiling(DefaultActionInvocation.java:228) > at > com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455) > at > com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:226) > My action was able to access the File, so it must have been something in the > cleanup. My action was very similar to the one found in this tutorial > http://www.roseindia.net/struts/struts2/struts-2-file-upload.shtml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.