Igor, it is not important how well works your example. Multipart form submit
initiated by wicket-ajax.js code is not treated as ajax request in Wicket
java code. The consequence is that I can't do anything a bit complex than
silly simple example.

What I would like to know is when it is supposed to be fixed. If I can help
you with that let me know. I suppose it could have been done by iterations -
I send you a rough patch then you point me what should be improved. I don't
have much time for now but from the other hand since it is some kind of
blocker for my investigations it is worth devoting some time for that.


igor.vaynberg wrote:
> 
> On Tue, Oct 20, 2009 at 4:06 PM, Vladimir K <[email protected]> wrote:
>>
>> The list of unassigned and unplanned issues is pretty big and contains
>> many
>> minor and irrelevant issues. I don't watch the whole list. Who does?
> 
> the committers do.
> 
>> I believe ajax file upload feature being the part of the 1.4.1 announce
>> and
>> still being out of order even for simple cases deserves fixing in 1.4.3,
> 
> works fine when i deploy 1.4.3 examples war and try it in ajax/file
> upload examples.
> 
>> especially taking into account the fact that the root cause is known and
>> rough patch was provided. I didn't get the patch in time for 1.4.2. Ok.
>> Now
>> it is 1.4.3. What would be the reason?
> 
> the reason is that no one has had time to look into it. as you said,
> you provided a rough patch. i looked at it and it needs more
> work/thinking. i havent had the time yet. neither, i guess, had any
> other committers.
> 
> our releases are not feature-boxed. when i see about 20 fixes in i
> build a release, doesnt matter what the fixes are.
> 
> -igor
> 
>>
>>
>> igor.vaynberg wrote:
>>>
>>> a list of unclosed issues can be found in our jira.
>>>
>>> -igor
>>>
>>> On Tue, Oct 20, 2009 at 1:36 PM, Vladimir K <[email protected]> wrote:
>>>>
>>>> File upload still does not work in ajax mode. UploadProgressBar does
>>>> not
>>>> work
>>>> with Firefox.
>>>> Are those considered as known issues? I think the release (even minor)
>>>> should list known problems.
>>>>
>>>>
>>>> igor.vaynberg wrote:
>>>>>
>>>>> this vote is to release wicket 1.4.3
>>>>>
>>>>> branch: https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.3/
>>>>> artifacts: http://people.apache.org/~ivaynberg/wicket-1.4.3/
>>>>> changelog:
>>>>> https://issues.apache.org/jira/browse/WICKET/fixforversion/12314250
>>>>> (and below)
>>>>>
>>>>> the vote ends thursday 1am gmt-8
>>>>>
>>>>> thank you.
>>>>>
>>>>> -igor
>>>>> ps. artifacts are being uploaded into people.apache as we speak so
>>>>> please give it a half hour before looking.
>>>>>
>>>>> -----------------------------------------------------------
>>>>>
>>>>> Release Notes - Wicket - Version 1.4.3
>>>>>
>>>>> ** Bug
>>>>>     * [WICKET-2348] - always insert encoding in http response header
>>>>>     * [WICKET-2436] - invalid DataTable markup breaks table layout
>>>>>     * [WICKET-2497] - AutoComplete textfield ignores "visible"
>>>>> property within hierarchy.
>>>>>     * [WICKET-2501] - BaseWicketTester clickLink calls onBeginRequest
>>>>> two
>>>>> times.
>>>>>     * [WICKET-2505] - Button.onSubmit javadoc is misleading
>>>>>     * [WICKET-2506] - Regression: "Could not find child with id: <ID>
>>>>> in the wicket:enclosure" for non-component tag
>>>>>     * [WICKET-2507] - Inconsistent resource path using <wicket:link>
>>>>> and HeaderContributor after second request
>>>>>     * [WICKET-2508] - NullPointerException in
>>>>> BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:96)
>>>>>     * [WICKET-2513] - wicket:enclosure does not work if child is a
>>>>> container and not a component (regression from 1.4.1)
>>>>>     * [WICKET-2516] - Javadoc for Component.getMarkupId is incorrect
>>>>>     * [WICKET-2518] - Application_bg.properties property file is
>>>>> incorrectly encoded
>>>>>     * [WICKET-2520] - Use of Object instead of generic T in
>>>>> StringAutoCompleteRenderer
>>>>>     * [WICKET-2522] - Easy fix suggestion: In BaseWicketTester
>>>>> 'IFormSubmitting' component should be the submitting component, not
>>>>> just a 'Button'
>>>>>     * [WICKET-2525] - DatePicker consume too much memory
>>>>>     * [WICKET-2527] - wicket:enclosure child attribute search path has
>>>>> changed
>>>>>     * [WICKET-2528] - CheckBoxMultipleChoice ignores isDisabled()
>>>>> checks
>>>>>     * [WICKET-2530] - Class not found when using OSGI class loader
>>>>>
>>>>> ** Improvement
>>>>>     * [WICKET-2344] - Performance improvement: more efficient
>>>>> AnnotProxyFieldValueFactory cache
>>>>>     * [WICKET-2459] - Add new German Wicket Book
>>>>>     * [WICKET-2511] - Upgrade to SLF4J version 1.5.8
>>>>>     * [WICKET-2524] - Configurable Throttle delay for
>>>>> AutoCompleteBehavior
>>>>>
>>>>> ** Wish
>>>>>     * [WICKET-2468] - AjaxLazyLoadPanel do not respect especific
>>>>> projects components configuration
>>>>>     * [WICKET-2515] - ModalWindow javadoc improvent
>>>>>
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/-vote--release-wicket-1.4.3-tp25954072p25982100.html
>>>> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/-vote--release-wicket-1.4.3-tp25954072p25984016.html
>> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-vote--release-wicket-1.4.3-tp25954072p26036424.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.

Reply via email to