Hi group,
Consider the follow situation:
- A ModalWindow is shown using a AjaxFormSubmitBehavior on the onchange of
an inputfield. The ModalWindow has a informative message and an Ok button
for the user to click if the message is read and understood. Pretty much
comparable to a properly styled
- Wicket
complains that it cannot increase the page version after rendering.
On 7/21/10, Vincent Lussenburg vincent.lussenb...@gmail.com wrote:
I remember trying that, but getting slapped by wicket for trying to
change
the component tree after rendering.. Or am I missing something?
We'll
or textfields or anything but labels into
listitems they will not work.
-igor
On Mon, Jul 26, 2010 at 3:41 AM, Vincent Lussenburg
vincent.lussenb...@gmail.com wrote:
Hi Igor,
Excellent suggestion! It took some experimenting, but we managed to get it
to work.
add(new
I remember trying that, but getting slapped by wicket for trying to change the
component tree after rendering.. Or am I missing something?
We'll doublecheck it tomorrow.
Groet,
Vincent
On Jul 21, 2010, at 18:37, Igor Vaynberg igor.vaynb...@gmail.com wrote:
if the data is strictly read-only
Hi Kent,
Oh yeah, that's also a possibility. However, the constructor code
would still be executed here. So I'd still needs to records some mocks
for that.
Thanks for your reply!
Groet,
Vincent
On May 13, 2010, at 8:03, Kent Tong k...@cpttm.org.mo wrote:
Hi Vincent,
You can use a page
Hi all,
I'm sending this page to check if I've drawn the correct conclusions on
testing wicket pages in isolation.
The situation is as follows: we have a number of pages that work on the same
model object. The object is passed from page to page in page transitions. So
for example, when the
that a
pagerequesttarget with the correct page was set on the request cycle.
-igor
On Wed, May 12, 2010 at 1:06 AM, Vincent Lussenburg
vincent.lussenb...@gmail.com wrote:
Hi all,
I'm sending this page to check if I've drawn the correct
conclusions on
testing wicket pages in isolation.
The situation is as follows
Hi all,
I kindly request you to take a look at the following issue:
http://issues.apache.org/jira/browse/WICKET-2796
It's a small issue, but if you like the solution, I'll be happy to create a
patch for it. If not, you can go ahead and close it as a won't-fix ;-).
Kind regards,
Vincent.
