Don't worry, no offence taken. I feel for you: dental work does suck!
The one thing I wasn't sure about was the following piece in the web.xml:
| <listener>
| <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
| </listener>
|
Like I said, I didn't have this listener configured before and it worked just fine. Looking at the jee5 example of the latest build, this listener is now present and without it, the application would not deploy at all (at least that's what was happening yesterday). I must be going crazy because I just commented the listener out to try and include the stack trace of what happens when it isn't configured and and it still works! Now my question is, should it be there or not?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058177#4058177
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058177
If I have this in my components.xml
<component class="org.jboss.seam.web.MultipartFilter">
| <property name="maxRequestSize">1000000</property>
| </component>
then the filter just checks the Content-Length of the HTTP request and throws the exception before reading the HTTP content if the length is bigger that the maxRequestSize. So the file is not really uploaded to the server and doesn't consume any memory resources.
Whereas, with
<s:fileUpload ... fileSize="#{foo.fixedSize}" />
the filter reads the content and gives my backing bean the control to decide. I'd like to have the maxRequestSize behavior in this case as well. Is it doable? Is my understanding correct?
tazman
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058169#4058169
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058169