Re: [S2] Struts 2.0.2 Build - ON HOLD

[Musachy Barroso]

Yeah that one. The multiple(list) and multiple(array) are working, I 
hadn't tried'em before. The tests pass, that what the first thing I 
tried. I'll double-check to see if I figure it out.

musachy
Don Brown wrote:
Nope, and I'm able to successfully upload a file on the single, 
multiple (array), and multiple (list).  To be clear, this page has the 
file upload tests that are failing?

http://localhost:8080/struts2-showcase/fileupload/

Don

Musachy Barroso wrote:
Yeap, I always get "File cannot be empty" (validation upload.lenght() 
> 0 failing) message. Do you have any uncommitted changes?

musachy

Don Brown wrote:
Actually, the showcase example is working for me now.  Do you still 
see a problem?

Don

Musachy Barroso wrote:
setFileSizeMax(long) is available in fileupload-commons 1.2. No 
idea why their javadoc link is pointing to the current javadocs 
instead of the last release (1.1.1).  This looks like a problem in 
1.1.1.

musachy

Musachy Barroso wrote:
The problem with the fileupload examples is that Don added this line:

upload.setSizeMax(maxSize);

to JakartaMultiPartRequest, the thing is that size is the 
threshold for the DeferredFileOutputStream for the files, not the 
actual limit of the file size, so the files never get written and 
the validation for the file size fails. Now here's where I got 
confused, as per:

http://jakarta.apache.org/commons/fileupload/apidocs/org/apache/commons/fileupload/FileUploadBase.html#setFileSizeMax(long) 


setFileSizeMax, is what should be used to limit the size of the 
files, which I think was Don's intention, but that method is not 
in the class....

musachy

Musachy Barroso wrote:
The tokens examples are failing because the "doInput" is never 
being called in "TokenAction", instead "input" is being called on 
ActionSupport, that's why the values are not on the session, 
hence the NullPointerException. How does this "doX" method 
discovery work? I can't find it on the docs.

musachy

Ted Husted wrote:
We're making progress. There were already problems with the 2.0.1
Showcase, a few of which we fixed, but we've also added several new
problems, namely

Continuation - continuations/guess.action
* pause doesn't pause and the example runs through all the 
guesses on
the first execution

Prefix example
* redirect-action throws a null pointer exception

UI Tag Input Example (both) - tags/ui/example!input.action
* birthday field missing and not linked to control
* color blank, picture blank

If example (freemarker)
* freemarker version doesn't wrap #26 through #33, they run 
together
as a paragraph
* (In 2.0.1, both versions ran everything together.)

Person Manager
* Create returns: No result defined for action
org.apache.struts2.showcase.person.NewPersonAction and result input
* List returns: No result defined for action
org.apache.struts2.showcase.person.ListPeopleAction and result 
success

validation/quizAjax!input.action
* Validation messages "stack up" on resubmit
* Submit button is at top left rather than bottom right

Store across request using MessageStoreInterceptor (Example)
* If provide an age, but not a name, the system returns for the 
name,
but clears the age.
* The validation messages appear at the top and next to the field,
which is confusing.

Hangman
* Ajax, Selected letters not displayed.

This is in addition to five problems remaining from the 2.0.1, and
several "quirks".

Since we seem to be losing ground, it doesn't seem appropriate 
to tag
another build until we have at least stabalized our own Showcase.
Right now, all the problems are being tracked in

* https://issues.apache.org/struts/browse/WW-1538

I'm tied up until Monday evening. If anyone has a chance to look at
these, please dive in.

-Ted.

--------------------------------------------------------------------- 

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--------------------------------------------------------------------- 

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]