If you're able to dump a stack trace for the log warning using the
debugger I can probably check further.
But if I had to guess (and I may very well be wrong here) you're using
one of the default interceptor stacks that includes both the old and
new file upload interceptors and you've also got s:file tags using the
name 'uploadedFiles'. If this is the case, the old file upload
interceptor will attempt injection using OGNL. The easiest way to
suppress the warning is your current workaround of changing the field
name, or change the name on your tag(s).
On Sun, Nov 10, 2024 at 8:41 PM Greg Huber <gregh3...@gmail.com> wrote:
>
> I just upgraded to the UploadedFilesAware version and now I see this
> message in my logs
>
> WARN com.opensymphony.xwork2.ognl.SecurityMemberAccess
> SecurityMemberAccess:isAccessible - Access to non-public [private
> java.util.List my.MyUpload.uploadedFiles] is blocked!
>
> Every thing is working ok.
>
> In MyUpload I have declared this:
>
> private List<UploadedFile> uploadedFiles = null;
>
> There is no reference I can find outside the class that uses this
> variable. There is no setter/getter either.
>
> As a test I renamed it in the class:
>
> private List<UploadedFile> uploadedFilesz = null;
>
> which should make no difference as I implement the withUploadedFile method:
>
> public void withUploadedFiles(List<UploadedFile> uploadedFiles) {
>
> this.uploadedFilesz = uploadedFiles;
>
> }
>
> The message goes away. So I have to not use the variable name
> uploadedFiles in my class ???
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
