File Upload Failure in DWR 3.0 M1

[Thomas Lopatic]

Hi all,

Let me just add to Sven's mail. I am able to reproduce the reported issue
with Firefox 2.0.0.14 on Linux. When I dump the POST request issued by DWR
then "batchId", "c0-id", and "callCount" are empty but everything else
looks OK.

It seems that any request parameter that consists of a single character or
digit does not get transmitted. Instead, an empty string is sent to the
server. I was able to confirm this by setting all parameters to "x".

When looking at the form that DWR creates, the DOM nodes of the hidden
input fields with single-character values look different from the other
hidden input fields. The former have an additional "#text" node under the
"value" attribute node.

The Mozilla documentation recommends not to use setAttribute() with
"value" attributes:

  http://developer.mozilla.org/en/docs/DOM:element.setAttribute

So, I tried changing the following in engine.js

  formInput.setAttribute("value", value);

to

  formInput.value = value;

as recommended by the Mozilla documentation, but this did not change
anything.

Weird.

(Sorry for messing up the threading. I just joined the mailing list.)

Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Thomas Lopatic]

Hi all,

Heehee, after having compiled my own version of Firefox 2.0.0.14 to debug
this further, it turns out that Firefox works perfectly, but my method of
network-dumping the POST request from the client to the server simply
hides single-character parameter values. (I was using "strings" on
"tcpdump" output and forgot that "strings" by default only displays
strings with a minimal length of four characters.)

So, forget my last mail about the single-character value hocus-pocus in
form fields. The world has just become a slightly more logical place
again. :-)

I've just checked out DWR from CVS and will start doing a bit of
server-side debugging now.

Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Thomas Lopatic]

Hi all,

Problem solved. We have a multipart resolver configured in our Spring
configuration. So, we have a bean named "multipartResolver", which makes
Spring's dispatcher servlet parse incoming multipart requests and wrap
them into MultipartHttpServletRequests. This seems to break the DWR
controller's multipart processing when using Spring integration. I've
verified this with today's CVS HEAD and it seems to still be an issue
there.

Removing the multipart resolver from our Spring configuration fixes this.

Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[XMaNIaC]

I've experienced that behavior before. Yes, with a multipartResolver and Spring MVC and DWR controller things won't work. I even filed an issue back in the day in Spring Jira..

On Wed, Apr 23, 2008 at 4:59 PM, Thomas Lopatic <thomas@...> wrote:

Hi all,

Problem solved. We have a multipart resolver configured in our Spring
configuration. So, we have a bean named "multipartResolver", which makes
Spring's dispatcher servlet parse incoming multipart requests and wrap
them into MultipartHttpServletRequests. This seems to break the DWR
controller's multipart processing when using Spring integration. I've
verified this with today's CVS HEAD and it seems to still be an issue
there.

Removing the multipart resolver from our Spring configuration fixes this.

Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[hansamann]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Thanx a lot, we discovered after many many hours that it was the Spring MultiPart resolver that stopped DWR from working as expcected. So this currently means we can only do file uploads with DWR then, which is for now fine but there coould be an issue in the future... Will DWR eventually support working in a configuration that includes teh Spring MultiPartResolver?

Cheers
Sven

 

---
Sven Haiges
Y! Messenger / Skype: hansamann

----- Original Message ----
From: Jose Noheda <jose.noheda@...>
To: users@...
Sent: Wednesday, April 23, 2008 12:03:14 PM
Subject: Re: [dwr-user] File Upload Failure in DWR 3.0 M1

I've experienced that behavior before. Yes, with a multipartResolver and Spring MVC and DWR controller things won't work. I even filed an issue back in the day in Spring Jira..

On Wed, Apr 23, 2008 at 4:59 PM, Thomas Lopatic <thomas@...> wrote:

Hi all,

Problem solved. We have a multipart resolver configured in our Spring
configuration. So, we have a bean named "multipartResolver", which makes
Spring's dispatcher servlet parse incoming multipart requests and wrap
them into MultipartHttpServletRequests. This seems to break the DWR
controller's multipart processing when using Spring integration. I've
verified this with today's CVS HEAD and it seems to still be an issue
there.

Removing the multipart resolver from our Spring configuration fixes this.

Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[XMaNIaC]

It's Spring fault really. If you declare a MultipartResolver it intercepts all calls. But if you need both just add another dispatcher servlet and use the multipart resolver in one and dwr controller in the other.

On Wed, Apr 23, 2008 at 11:10 PM, Sven Haiges <hansamann@...> wrote:

Thanx a lot, we discovered after many many hours that it was the Spring MultiPart resolver that stopped DWR from working as expcected. So this currently means we can only do file uploads with DWR then, which is for now fine but there coould be an issue in the future... Will DWR eventually support working in a configuration that includes teh Spring MultiPartResolver?

Cheers
Sven

 

---
Sven Haiges
Y! Messenger / Skype: hansamann

----- Original Message ----
From: Jose Noheda <jose.noheda@...>
To: users@...
Sent: Wednesday, April 23, 2008 12:03:14 PM
Subject: Re: [dwr-user] File Upload Failure in DWR 3.0 M1

I've experienced that behavior before. Yes, with a multipartResolver and Spring MVC and DWR controller things won't work. I even filed an issue back in the day in Spring Jira..

On Wed, Apr 23, 2008 at 4:59 PM, Thomas Lopatic <thomas@...> wrote:

Hi all,

Problem solved. We have a multipart resolver configured in our Spring
configuration. So, we have a bean named "multipartResolver", which makes
Spring's dispatcher servlet parse incoming multipart requests and wrap
them into MultipartHttpServletRequests. This seems to break the DWR
controller's multipart processing when using Spring integration. I've
verified this with today's CVS HEAD and it seems to still be an issue
there.

Removing the multipart resolver from our Spring configuration fixes this.

Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...