As you write ListChoice are no longer invoked. The ajax event are called afaik
after all updates of model has occurred. I actually changed my coding style
after this and began using abstract models, its actually much easyer coding
this way, and all of your components will be ajax prepaered...:)
No true:)
Why cant you use ID's?
IT is true that forexample dropdown options are created on a specific pattern
but it's somewhat easy to create some javascript which adapts that pattern. We
use a lot of onchange some which are added in the html at some which are added
with the attribute
With Listchoiec are no longer invoked, I meant listchoice.onchange.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nino Wael
Sent: 8. december 2006 12:51
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Help with
Nino Wael wrote:
input id=wordbutton disabled=disabled
type=submit value=Generer rapport wicket:id=wordbutton
onclick=showContent('uglyfix');showContent('uniquename'); /
How can you run this example with wicket?? It escapes qoutes in a
strange wa so you
Hmm, it is actually working, and I do agree that you write wouldn't work...
This is the output on the html generated by wicket:
input value=Generer rapport type=submit disabled=disabled
onclick=showContent('uglyfix');showContent('uniquename'); name=wordbutton
id=wordbutton/
Except if he is using trunk from wicket-1.x, but there can still be demons.
Martijn
On 12/8/06, Erik van Oosten [EMAIL PROTECTED] wrote:
Hello Yuri,
Which version of Wicket are you using?
If it is not Wicket 2.0, you should replace WicketFilter with WicketServlet.
Regards,
Erik.
Hello,
I am trying to use the AjaxFormValidatingBehavior like this:
AjaxFormValidatingBehavior.addToAllFormComponents(form, onchange);
but unexpectedly the form is also submitted (and not just validated). Is
this intentional, a bug, or am I missing something? Is there a workaround?
I am using
That did it. Thanks for the help.
igor.vaynberg wrote:
well in that case just do
new AjaxPagingNavigator() { onajaxevent(target) {
target.add(dataviewparent);
}}
-igor
--
View this message in context:
http://www.nabble.com/DataView-and-Ajax-tf2771602.html#a7759052
Sent from
Hello,
I found a solution. The following code is actually all that was needed:
public class AjaxFormValidatingBehavior extends
*/AjaxFormComponentUpdatingBehavior /*{
private final Component feedbackPanel;
public AjaxFormValidatingBehavior(String event, Component
feedbackPanel) {
On 12/8/06, Johan Compagner [EMAIL PROTECTED] wrote:
shouldn't we extend from IDetachable in 1.3?
i dont see a problem with that
-igor
johan
On 12/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
i guess if you are certain the size never changes this works ok
-igor
On 12/7/06,
Hi,
im currently wondering why the PagingNavigator allways issue a session ? (im
on wicket 2.0)
I mean if i create a mainpage and link to 2 subpages all is fine and no
session used. If i embed a PagingNavigator into any page a session will be
created on the moment i access that page, however I
If you're not using 2.0 or 1.3 you have to use WicketServlet (as the
others said). Otherwise, you're having class path troubles and you
have to look at how you set up JBoss.
Eelco
On 12/8/06, Lost Still Lost [EMAIL PROTECTED] wrote:
Hello,
I am working on a rather simple example of a
the question is is this really necessary because we have already code that
does the detach:
Note that if the IDataProvider implementation implements [EMAIL PROTECTED]
IDetachable}
* interface, the [EMAIL PROTECTED] IDetachable#detach()} method will be called
at the
end
* of request.
So if
well the thing here is expressiveness. the way it is right now was done to
avoid api breaks.
but if you look at the idataprovider - how do you know that you can make the
impl also implement idetachable and that will work? same can be said for
models, why have IModel extend IDetachable? it is so
14 matches
Mail list logo
