DateField is no more FormComponentPanel, but now extends DateTimeField and
just sets the time related components to invisible.
Should we do the same for the recently added TimeField ?
On Mon, Dec 20, 2010 at 8:51 PM, jdonners...@apache.org wrote:
Author: jdonnerstag
Date: Mon Dec 20 19:51:09
Hi Zilvinas, thank u for the test!
We actually have different issues. I described mine at
https://issues.apache.org/jira/browse/WICKET-3272
The tester setup the next request cycle just after process the request
triggered by the mocked AJAX event.
It differs from 1.4 where the request setup was
Hi Pedro,
Yeah those are different issues. I understand that in 1.5 its different how
tester works. I know how can i access those parameters through request.
The issue i have, is that if you do ajax call in the middle between setting
value to input and submiting from, FormTester loses that value
IMO it is not a bug, rather an improvement: set the form components value
as parameter in form submit request.
the scenario is:
- a new form is created
- a form components receive a new value in the first submit
- in the second submit the new value at the form component didn't get add as
an
In the 1.4 the executeAjaxEvent method do not create an request to be
processed as in the 1.5.
I prefer how it works in the 1.5, because when we don't use an AJAX request
to trigger the default request cycle we need some hack in the tester, like:
checkUsability. Perhaps we can even remove this
On Tue, Dec 21, 2010 at 5:04 PM, Pedro Santos pedros...@gmail.com wrote:
In the 1.4 the executeAjaxEvent method do not create an request to be
processed as in the 1.5.
I prefer how it works in the 1.5, because when we don't use an AJAX request
to trigger the default request cycle we need some
Hi,
With https://issues.apache.org/jira/browse/WICKET-3261 I added a new Maven
module to 1.5: wicket-core.
Its purpose is to create a .jar that contains the classes from wicket.jar,
wicket-util.jar and wicket-request.jar (aka uberjar, jarjar, ...).
We split wicket/ to three modules : wicket/,
+1 to rename current wicket into wicket-core
-igor
On Tue, Dec 21, 2010 at 6:53 PM, Martin Grigorov mgrigo...@apache.org wrote:
Hi,
With https://issues.apache.org/jira/browse/WICKET-3261 I added a new Maven
module to 1.5: wicket-core.
Its purpose is to create a .jar that contains the
