[shane.bryzak]

"nathandennis" wrote:
thanks shane,
i was hoping i was that lost..

It seems like there wasn't a bug with fileUpload after all, I retested it again and no matter what I did it worked every time. Perhaps because it was late at night when I tried it the first time my brain was playing tricks on me :)

Anyway, could you please try it with the latest CVS version of Seam and let me know if you still have problems.

[evl123]

"evl123" wrote:
Hi Shane,
On the s:fileUpload, now I have an issue regarding the file size exceeding a configured limit. When that happens, an HTTP code 500 returns with the following message:
java.lang.RuntimeException: Multipart request is larger than allowed size

I could not find a way to catch this exception and customize it. I found this page (which mentions the same issue):
http://jira.jboss.com:8080/jira/browse/JBSEAM-1239?page=all&decorator=printable

However, I have no idea how to resolve this exception.

The following is my configuration in components.xml
<web:multipart-filter create-temp-files="true"
max-request-size="10000"
url-pattern="*.seam" />


I would appreciate any advice on how to handle this exception.

Thanks again,
landrew

So is this a known bug in jboss-seam-1.2.0 or is it a JBoss Server and JBoss Seam package compatibility issue (or something else)? I'm using jboss-4.0.5.GA and jboss-seam-1.2.0.PATCH1 packages.

Thanks for any thought on this issue..
- l

[evl123]

Hi Shane,
How do I handle s:fileUpload issue regarding the file size exceeding a configured limit? When that happens, the page breaks with HTTP code 500 returned with the following message:
java.lang.RuntimeException: Multipart request is larger than allowed size

I could not find a way to catch this exception.
This link mentions this issue but I don't see any solution yet:
http://jira.jboss.com:8080/jira/browse/JBSEAM-1239?page=all&decorator=printable

I'm using jboss-4.0.5.GA.
The following is my configuration in components.xml
<web:multipart-filter create-temp-files="true"
max-request-size="10000"
url-pattern="*.seam" />


I would appreciate any advice on how to handle this exception.

Thanks.

[shane.bryzak]

MultipartRequest now throws a FileUploadException instead of a RuntimeException, you can configure an exception handler for this in pages.xml.

[evl123]

MultipartRequest now throws a FileUploadException instead of a RuntimeException, you can configure an exception handler for this in pages.xml.

Shane,
I'm running JBoss-4.0.5.GA and using JBoss-Seam-1.2.0.PATCH1 which are compatible and are working ok - only issue is the Multipart Request Runtime Exception.

From the JIRA tracker, looks like this fix goes into Seam 1.3.0.ALPHA, and 1.3.0.ALPHA's readme file recommends install JBoss 4.2.0.GA which would need certain degree of adjustments to my workspace (e.g. jar files). I tried but saw a lot fo exceptions including faces-config.xml Digester parse error, etc.

My question is what versions of JBoss and Seam would you recommend to get this fix. And if I stay with JBoss-4.0.5.GA and JBoss-Seam-1.2.0.PATCH1, what jar files should I replace to get this fix without breaking the compatibilty.

Thank you.

[pmuir]

You can run 1.3ALPHA on JBoss AS 4.0.5 - take a look at the documentation (end of chapter 1). You can't get the fix on 1.2.0.PATCH1 without patching the source of Seam and recompiling.

[evl123]

"petemuir" wrote:
You can run 1.3ALPHA on JBoss AS 4.0.5 - take a look at the documentation (end of chapter 1). You can't get the fix on 1.2.0.PATCH1 without patching the source of Seam and recompiling.

Hi petemuir,
Thank you for good advice. I started to integrate the source files from 1.3ALPHA and compile and add more source as needed to get the workspace to compile. Suddenly at work, new projects came in and I've been so busy and didn't have a chance to get back to this POC project but I appreciate it. It makes sense to surgically integrate the fix and it would help me understand the flow better too. So, I'm not there yet to see the result but I'll update back to the Forum when I'm there.

Thanks again,
landrew