Ahhhhh, big SORRY for version typo...
I meant that I used 5.3.7 (not 4.3.7), and I wanted to stay there, but
there was some java-8 related issue during boot, and I had to upgrade to
5.3.8 (release notes says some java -8 issue was fixed there).
I didn't want to upgrade , at least not for now because the web app is
huge, to newest 5.4.x version.
But I managed, with few errors, to start the 5.4.x version of my app,
just to check single page that uses Upload component, and it seems the
issue with uploading preserves.
Ugh, dunno whhat to look next...
-Vjeran
On 06/19/2018 06:49 PM, Ivano Luberti wrote:
Side questiono on this message: Tapestry 4.3.7 is not compatible with
Java 8 ?
Il 19/06/2018 18:28, Vjeran Marcinko ha scritto:
Hi,
I am upgrading my old Tapestry 4.3.7 app (java-7, standalone
Tomcat...) to newer tech stack (java 8, Spring Boot with embeddable
Tomcat deployed as single jar...). I wan't to leave tapestry untouched
as much as possible, so I just upgraded from 4.3.7 to 4.3.8 because of
Java-8 requirement.
And practically everything works perfectly except that my Upload
component stopped working. It doesn't raise any error, its just that
after form submit, my UploadedFile instance is always null.
I debugged a bit, and found out that within Tapestry's
MultipartDecoderImpl there is this part that should parse FileItems
from HTTP request, but it always parses empty list. I udnerstand that
here Taestry uses Apache Commons-FileUpload, but I have no idea what
has changed for this to stop working properly?
protected List<FileItem>parseRequest(HttpServletRequest request)
{
try {
return createFileUpload().parseRequest(request); }catch
(FileUploadException ex)
{
uploadException = ex; return Collections.emptyList(); }
}
Dunno if Spring Boot and its embeeded Tomcat are making some
difference here...
Any idea?
-Vjeran
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
