Hi Mike,
Am 26.06.2011 05:06, schrieb Michael O'Cleirigh:
Hi Harald,
Thanks for taking the time to implement your solution to the OSGi problem.
If you could create a patch (or fork and then pull request; or commit
directly) into the
Thanks Igor for your solution.
However, cannot figure out /why/ i can't use a button.
Let me explain a little about the mechanics of the page (code is at the
bottom). I can use it to edit data of an existing User (pagestate=EDIT) or
create a new one (pagestate=NEW). On entry of the page i check
Hi again
I found a solution - just add the
org.apache.wicket.extensions.wizard.FinishButton.step.did.not.complete to
your message file with what ever message you want.
I still don't understand why the wizard must error this message anyway?
Rebecca
--
View this message in context:
You can user a button with default form processing set to false, but you
still have to call form.clearinput() so that form components pull their
values from the model instead of using the values with which the form was
submitted. However, since you are dismissing the submitted values anyways it
Small bugfix update to version 1.0.1 released
-Fixed: StackOverflowError at WicketClassHierarchy.addRecursive [Defect 69]
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ANN-Plugin-WicketForge-1-0-0-available-for-IDEA-9-tp3608246p3626374.html
Sent from the Users
in that case you have a couple of options
a) in page's onbeforerender traverse all children with a special
visitor that figures this out and controls the visibility of the
header
b) control the header's visibility with javascript
c) put the header as the last element on the page and control its
I am using a dated version of wicket. I don't know if this is fixed but
I wanted to override the functionality in the modal.js from
wicket-extensions.
Basically, I need to remove the inner form that is created by the
javascript. Some of the browsers we are using, the user cannot submit
the
Related bug:
https://issues.apache.org/jira/browse/WICKET-3146
From: Brown, Berlin [GCG-PFS]
Sent: Sunday, June 26, 2011 8:23 PM
To: 'users@wicket.apache.org'
Subject: Override modal.js functionality because of issue with form
inside form
I am using a dated
Hi Brown, submit a form inside a modal window should be fine, just
make sure you have an outer form higher in hierarchy. Nested forms
inside a modal window works nice even in old versions. It is important
because it prevents invalid markup like form tag inside form tag.
About improvements in modal
