You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by smallufo <sm...@gmail.com> on 2014/07/05 11:42:27 UTC
[6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
I have a LoginModal which pops up a modal with username / password for user
to login.
It works before wicket 6.
After upgrading to wicket 6 , it's not working anymore.
Can someone check where goes wrong ?
Here is the LoginModal code :
http://pastebin.com/hNTMs3A7
And here is the LoginPage code :
http://pastebin.com/aDDxuZmx
In wicket 1.5 , it generate the following code :
<input type="submit" name=":submit" id="*id98*" value="submit">
<input type="button" name="cancel" id="*id99*" value="cancel">
And I search "id98" , "id99" , I can see them 'hooked' into wicket by
Wicket.Event.add(window, "domready", function(event) {
Wicket.Ajax.ajax({"sc":":submit","c":"id98","u":"./page?19-1.IBehaviorListener.0-form-submit","e":"click","f":"id97","m":"POST"});;
Wicket.Ajax.ajax({"sc":"cancel","c":"id99","u":"./page?19-1.IBehaviorListener.0-form-cancel","e":"click","f":"id97","m":"POST"});;
But after upgrading to wicket 6 (well , with wicket-bootstrap ) , it
generates :
<input type="submit" class="btn btn-default" name=":submit" id="*submitdc*"
value="submit">
<input type="button" class="btn btn-default" name="cancel" id="*canceldd*"
value="cancel">
But I cannot find another "submitdc" or "canceldd" string in the source
code.
So , no matter 'submit' or 'cancel' , the console prints nothing ( I put
some logging in the onSubmit , .
Wicket AJAX Debug console didn't show anything.
What may go wrong here ?
Thanks.
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by smallufo <sm...@gmail.com>.
2014-07-05 18:53 GMT+08:00 Francois Meillet <fr...@gmail.com>:
>
> Have you set a breakpoint in the onSubmit method of your ajax submit
> button ?
>
> François
>
No , I didn't set any breakpoints (in fact , I don't know such feature).
The code is just like that.
The two onSubmit()s are not hooked / triggered.
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by Francois Meillet <fr...@gmail.com>.
On Wicket 7.02 it works.
With wicket-bootstrap dependencies.
Have you set a breakpoint in the onSubmit method of your ajax submit button ?
François
François Meillet
Formation Wicket - Développement Wicket
Le 5 juil. 2014 à 11:42, smallufo <sm...@gmail.com> a écrit :
> I have a LoginModal which pops up a modal with username / password for user
> to login.
> It works before wicket 6.
> After upgrading to wicket 6 , it's not working anymore.
>
> Can someone check where goes wrong ?
>
> Here is the LoginModal code :
> http://pastebin.com/hNTMs3A7
>
> And here is the LoginPage code :
> http://pastebin.com/aDDxuZmx
>
> In wicket 1.5 , it generate the following code :
> <input type="submit" name=":submit" id="*id98*" value="submit">
> <input type="button" name="cancel" id="*id99*" value="cancel">
> And I search "id98" , "id99" , I can see them 'hooked' into wicket by
>
> Wicket.Event.add(window, "domready", function(event) {
> Wicket.Ajax.ajax({"sc":":submit","c":"id98","u":"./page?19-1.IBehaviorListener.0-form-submit","e":"click","f":"id97","m":"POST"});;
> Wicket.Ajax.ajax({"sc":"cancel","c":"id99","u":"./page?19-1.IBehaviorListener.0-form-cancel","e":"click","f":"id97","m":"POST"});;
>
> But after upgrading to wicket 6 (well , with wicket-bootstrap ) , it
> generates :
> <input type="submit" class="btn btn-default" name=":submit" id="*submitdc*"
> value="submit">
> <input type="button" class="btn btn-default" name="cancel" id="*canceldd*"
> value="cancel">
>
> But I cannot find another "submitdc" or "canceldd" string in the source
> code.
>
> So , no matter 'submit' or 'cancel' , the console prints nothing ( I put
> some logging in the onSubmit , .
> Wicket AJAX Debug console didn't show anything.
>
> What may go wrong here ?
> Thanks.
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by Martin Grigorov <mg...@apache.org>.
Sorry, but I have no time to create a demo application for every user with
a problem.
The user should help us a bit too!
Please create a full demo app and explain the steps to reproduce.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 3:32 PM, smallufo <sm...@gmail.com> wrote:
> Sorry , because the server receives no event.
> There is no debug output.
>
> I think it is easy to replicate the error.
> just fork bootstrap-samples :
>
>
> https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples
>
> and add
> LoginModal code :
> http://pastebin.com/0qGUFvXP
>
>
> And the LoginPage code :
> http://pastebin.com/aDDxuZmx
>
> The server will receive no event (fired in the LoginPage) .
>
>
>
> 2014-07-08 18:45 GMT+08:00 Martin Grigorov <mg...@apache.org>:
>
> > Then you will have to debug what happens ...
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> >
> > On Tue, Jul 8, 2014 at 1:28 PM, smallufo <sm...@gmail.com> wrote:
> >
> > > Yes , I am using 6.16.0
> > >
> > > <properties>
> > > <wicket.version>6.16.0</wicket.version>
> > > <wicket-bootstrap.version>0.9.4</wicket-bootstrap.version>
> > > <yuicompressor.version>2.4.7</yuicompressor.version>
> > > </properties>
> > >
> > >
> > > 2014-07-08 14:56 GMT+08:00 Martin Grigorov <mg...@apache.org>:
> > >
> > > > I believe https://issues.apache.org/jira/browse/WICKET-5585 is
> > related.
> > > > Do you use Wicket 6.16.0 ?
> > > >
> > > > Martin Grigorov
> > > > Wicket Training and Consulting
> > > > https://twitter.com/mtgrigorov
> > > >
> > > >
> > > > On Tue, Jul 8, 2014 at 4:00 AM, smallufo <sm...@gmail.com> wrote:
> > > >
> > > > > sorry , There is no stack trace.
> > > > > Because it triggers nothing , the server doesn't receive anything.
> > > > >
> > > > >
> > > > >
> > > > > 2014-07-07 14:21 GMT+08:00 Michael Haitz <mi...@1und1.de>:
> > > > >
> > > > > > please provide the full stacktrace.
> > > > > >
> > > > > > cheers,
> > > > > > Michael
> > > > > >
> > > > > > Am 06.07.2014 um 05:44 schrieb smallufo <sm...@gmail.com>:
> > > > > >
> > > > > > > It seems working now.
> > > > > > > But such removal also make theme-switching not working :
> > > > > > >
> > > > > > > If I enable the ThemeProvider :
> > > > > > >
> > > > > > > final ThemeProvider themeProvider = new
> > > > > > > BootswatchThemeProvider(BootswatchTheme.Flatly);
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> settings.setJsResourceFilterName("footer-container").setThemeProvider(themeProvider);
> > > > > > >
> > > > > > > without "footer-container" in the BasePage
> > > > > > >
> > > > > > > wicket-bootstrap will throw
> > > > > > >
> > > > > > > WicketRuntimeException: theme does not exists: bootstrap
> > > > > > >
> > > > > > > at
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> de.agilecoders.wicket.themes.settings.BootswatchThemeProvider.byName(BootswatchThemeProvider.java:49)
> > > > > > >
> > > > > > >
> > > > > > > So I could only use the native bootstrap theme now.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 2014-07-06 11:30 GMT+08:00 smallufo <sm...@gmail.com>:
> > > > > > >
> > > > > > >> I found where goes wrong ,
> > > > > > >> it's RenderJavaScriptToFooterHeaderResponseDecorator that
> causes
> > > the
> > > > > > >> problem.
> > > > > > >>
> > > > > > >> I am not familiar with wicket-bootstrap , so I mimicked
> > > > > wicket-bootstrap
> > > > > > >> sample's architecture :
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples/src/main/java/de/agilecoders/wicket/samples
> > > > > > >>
> > > > > > >> This is my 'not' working architecture :
> > > > > > >> http://pastebin.com/vB3Ek2t9
> > > > > > >>
> > > > > > >> After removing
> RenderJavaScriptToFooterHeaderResponseDecorator ,
> > > > > > >> footer-container , it works fine.
> > > > > > >>
> > > > > > >> http://pastebin.com/kAehvaRr
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> 2014-07-05 21:10 GMT+08:00 Francois Meillet <
> > > > > francois.meillet@gmail.com
> > > > > > >:
> > > > > > >>
> > > > > > >> Run your app in debug mode and set some breakpoint.
> > > > > > >>>
> > > > > > >>> eclipse
> > > > > > >>>
> > > > > > >>>
> > > > > >
> > > > >
> > > >
> > >
> >
> http://www.eclipse.org/jetty/documentation/current/debugging-with-intellij.html
> > > > > > >>>
> http://www.vogella.com/tutorials/EclipseDebugging/article.html
> > > > > > >>>
> > > > > > >>>
> > > > > >
> > > > >
> > > >
> > >
> >
> http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Frun-debug%2Fref-run_debug.htm
> > > > > > >>>
> > > > > > >>> intellij
> > > > > > >>>
> > > > http://www.jetbrains.com/idea/webhelp/run-debug-configurations.html
> > > > > > >>>
> > > > > > >>>
> > > > > >
> > > > >
> > > >
> > >
> >
> http://www.jetbrains.com/idea/webhelp/creating-and-editing-run-debug-configurations.html
> > > > > > >>>
> > > > > > >>> François Meillet
> > > > > > >>> Formation Wicket - Développement Wicket
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> Le 5 juil. 2014 à 14:56, smallufo <sm...@gmail.com> a
> > écrit :
> > > > > > >>>
> > > > > > >>>> 2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
> > > > > > >>>>
> > > > > > >>>>>
> > > > > > >>>>> But i still find another "id6c" or "id6d" in the source
> > code.
> > > > > > >>>>>
> > > > > > >>>>
> > > > > > >>>> sorry typo :
> > > > > > >>>>
> > > > > > >>>> But i still *cannot* find another "id6c" or "id6d" in the
> > > source
> > > > > > code.
> > > > > > >>>
> > > > > > >>>
> > > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by smallufo <sm...@gmail.com>.
Sorry , because the server receives no event.
There is no debug output.
I think it is easy to replicate the error.
just fork bootstrap-samples :
https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples
and add
LoginModal code :
http://pastebin.com/0qGUFvXP
And the LoginPage code :
http://pastebin.com/aDDxuZmx
The server will receive no event (fired in the LoginPage) .
2014-07-08 18:45 GMT+08:00 Martin Grigorov <mg...@apache.org>:
> Then you will have to debug what happens ...
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
>
> On Tue, Jul 8, 2014 at 1:28 PM, smallufo <sm...@gmail.com> wrote:
>
> > Yes , I am using 6.16.0
> >
> > <properties>
> > <wicket.version>6.16.0</wicket.version>
> > <wicket-bootstrap.version>0.9.4</wicket-bootstrap.version>
> > <yuicompressor.version>2.4.7</yuicompressor.version>
> > </properties>
> >
> >
> > 2014-07-08 14:56 GMT+08:00 Martin Grigorov <mg...@apache.org>:
> >
> > > I believe https://issues.apache.org/jira/browse/WICKET-5585 is
> related.
> > > Do you use Wicket 6.16.0 ?
> > >
> > > Martin Grigorov
> > > Wicket Training and Consulting
> > > https://twitter.com/mtgrigorov
> > >
> > >
> > > On Tue, Jul 8, 2014 at 4:00 AM, smallufo <sm...@gmail.com> wrote:
> > >
> > > > sorry , There is no stack trace.
> > > > Because it triggers nothing , the server doesn't receive anything.
> > > >
> > > >
> > > >
> > > > 2014-07-07 14:21 GMT+08:00 Michael Haitz <mi...@1und1.de>:
> > > >
> > > > > please provide the full stacktrace.
> > > > >
> > > > > cheers,
> > > > > Michael
> > > > >
> > > > > Am 06.07.2014 um 05:44 schrieb smallufo <sm...@gmail.com>:
> > > > >
> > > > > > It seems working now.
> > > > > > But such removal also make theme-switching not working :
> > > > > >
> > > > > > If I enable the ThemeProvider :
> > > > > >
> > > > > > final ThemeProvider themeProvider = new
> > > > > > BootswatchThemeProvider(BootswatchTheme.Flatly);
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> settings.setJsResourceFilterName("footer-container").setThemeProvider(themeProvider);
> > > > > >
> > > > > > without "footer-container" in the BasePage
> > > > > >
> > > > > > wicket-bootstrap will throw
> > > > > >
> > > > > > WicketRuntimeException: theme does not exists: bootstrap
> > > > > >
> > > > > > at
> > > > > >
> > > > >
> > > >
> > >
> >
> de.agilecoders.wicket.themes.settings.BootswatchThemeProvider.byName(BootswatchThemeProvider.java:49)
> > > > > >
> > > > > >
> > > > > > So I could only use the native bootstrap theme now.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > 2014-07-06 11:30 GMT+08:00 smallufo <sm...@gmail.com>:
> > > > > >
> > > > > >> I found where goes wrong ,
> > > > > >> it's RenderJavaScriptToFooterHeaderResponseDecorator that causes
> > the
> > > > > >> problem.
> > > > > >>
> > > > > >> I am not familiar with wicket-bootstrap , so I mimicked
> > > > wicket-bootstrap
> > > > > >> sample's architecture :
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples/src/main/java/de/agilecoders/wicket/samples
> > > > > >>
> > > > > >> This is my 'not' working architecture :
> > > > > >> http://pastebin.com/vB3Ek2t9
> > > > > >>
> > > > > >> After removing RenderJavaScriptToFooterHeaderResponseDecorator ,
> > > > > >> footer-container , it works fine.
> > > > > >>
> > > > > >> http://pastebin.com/kAehvaRr
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> 2014-07-05 21:10 GMT+08:00 Francois Meillet <
> > > > francois.meillet@gmail.com
> > > > > >:
> > > > > >>
> > > > > >> Run your app in debug mode and set some breakpoint.
> > > > > >>>
> > > > > >>> eclipse
> > > > > >>>
> > > > > >>>
> > > > >
> > > >
> > >
> >
> http://www.eclipse.org/jetty/documentation/current/debugging-with-intellij.html
> > > > > >>> http://www.vogella.com/tutorials/EclipseDebugging/article.html
> > > > > >>>
> > > > > >>>
> > > > >
> > > >
> > >
> >
> http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Frun-debug%2Fref-run_debug.htm
> > > > > >>>
> > > > > >>> intellij
> > > > > >>>
> > > http://www.jetbrains.com/idea/webhelp/run-debug-configurations.html
> > > > > >>>
> > > > > >>>
> > > > >
> > > >
> > >
> >
> http://www.jetbrains.com/idea/webhelp/creating-and-editing-run-debug-configurations.html
> > > > > >>>
> > > > > >>> François Meillet
> > > > > >>> Formation Wicket - Développement Wicket
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>> Le 5 juil. 2014 à 14:56, smallufo <sm...@gmail.com> a
> écrit :
> > > > > >>>
> > > > > >>>> 2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
> > > > > >>>>
> > > > > >>>>>
> > > > > >>>>> But i still find another "id6c" or "id6d" in the source
> code.
> > > > > >>>>>
> > > > > >>>>
> > > > > >>>> sorry typo :
> > > > > >>>>
> > > > > >>>> But i still *cannot* find another "id6c" or "id6d" in the
> > source
> > > > > code.
> > > > > >>>
> > > > > >>>
> > > > > >>
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by Martin Grigorov <mg...@apache.org>.
Then you will have to debug what happens ...
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 1:28 PM, smallufo <sm...@gmail.com> wrote:
> Yes , I am using 6.16.0
>
> <properties>
> <wicket.version>6.16.0</wicket.version>
> <wicket-bootstrap.version>0.9.4</wicket-bootstrap.version>
> <yuicompressor.version>2.4.7</yuicompressor.version>
> </properties>
>
>
> 2014-07-08 14:56 GMT+08:00 Martin Grigorov <mg...@apache.org>:
>
> > I believe https://issues.apache.org/jira/browse/WICKET-5585 is related.
> > Do you use Wicket 6.16.0 ?
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> >
> > On Tue, Jul 8, 2014 at 4:00 AM, smallufo <sm...@gmail.com> wrote:
> >
> > > sorry , There is no stack trace.
> > > Because it triggers nothing , the server doesn't receive anything.
> > >
> > >
> > >
> > > 2014-07-07 14:21 GMT+08:00 Michael Haitz <mi...@1und1.de>:
> > >
> > > > please provide the full stacktrace.
> > > >
> > > > cheers,
> > > > Michael
> > > >
> > > > Am 06.07.2014 um 05:44 schrieb smallufo <sm...@gmail.com>:
> > > >
> > > > > It seems working now.
> > > > > But such removal also make theme-switching not working :
> > > > >
> > > > > If I enable the ThemeProvider :
> > > > >
> > > > > final ThemeProvider themeProvider = new
> > > > > BootswatchThemeProvider(BootswatchTheme.Flatly);
> > > > >
> > > > >
> > > >
> > >
> >
> settings.setJsResourceFilterName("footer-container").setThemeProvider(themeProvider);
> > > > >
> > > > > without "footer-container" in the BasePage
> > > > >
> > > > > wicket-bootstrap will throw
> > > > >
> > > > > WicketRuntimeException: theme does not exists: bootstrap
> > > > >
> > > > > at
> > > > >
> > > >
> > >
> >
> de.agilecoders.wicket.themes.settings.BootswatchThemeProvider.byName(BootswatchThemeProvider.java:49)
> > > > >
> > > > >
> > > > > So I could only use the native bootstrap theme now.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > 2014-07-06 11:30 GMT+08:00 smallufo <sm...@gmail.com>:
> > > > >
> > > > >> I found where goes wrong ,
> > > > >> it's RenderJavaScriptToFooterHeaderResponseDecorator that causes
> the
> > > > >> problem.
> > > > >>
> > > > >> I am not familiar with wicket-bootstrap , so I mimicked
> > > wicket-bootstrap
> > > > >> sample's architecture :
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples/src/main/java/de/agilecoders/wicket/samples
> > > > >>
> > > > >> This is my 'not' working architecture :
> > > > >> http://pastebin.com/vB3Ek2t9
> > > > >>
> > > > >> After removing RenderJavaScriptToFooterHeaderResponseDecorator ,
> > > > >> footer-container , it works fine.
> > > > >>
> > > > >> http://pastebin.com/kAehvaRr
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> 2014-07-05 21:10 GMT+08:00 Francois Meillet <
> > > francois.meillet@gmail.com
> > > > >:
> > > > >>
> > > > >> Run your app in debug mode and set some breakpoint.
> > > > >>>
> > > > >>> eclipse
> > > > >>>
> > > > >>>
> > > >
> > >
> >
> http://www.eclipse.org/jetty/documentation/current/debugging-with-intellij.html
> > > > >>> http://www.vogella.com/tutorials/EclipseDebugging/article.html
> > > > >>>
> > > > >>>
> > > >
> > >
> >
> http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Frun-debug%2Fref-run_debug.htm
> > > > >>>
> > > > >>> intellij
> > > > >>>
> > http://www.jetbrains.com/idea/webhelp/run-debug-configurations.html
> > > > >>>
> > > > >>>
> > > >
> > >
> >
> http://www.jetbrains.com/idea/webhelp/creating-and-editing-run-debug-configurations.html
> > > > >>>
> > > > >>> François Meillet
> > > > >>> Formation Wicket - Développement Wicket
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> Le 5 juil. 2014 à 14:56, smallufo <sm...@gmail.com> a écrit :
> > > > >>>
> > > > >>>> 2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
> > > > >>>>
> > > > >>>>>
> > > > >>>>> But i still find another "id6c" or "id6d" in the source code.
> > > > >>>>>
> > > > >>>>
> > > > >>>> sorry typo :
> > > > >>>>
> > > > >>>> But i still *cannot* find another "id6c" or "id6d" in the
> source
> > > > code.
> > > > >>>
> > > > >>>
> > > > >>
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> >
>
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by smallufo <sm...@gmail.com>.
Yes , I am using 6.16.0
<properties>
<wicket.version>6.16.0</wicket.version>
<wicket-bootstrap.version>0.9.4</wicket-bootstrap.version>
<yuicompressor.version>2.4.7</yuicompressor.version>
</properties>
2014-07-08 14:56 GMT+08:00 Martin Grigorov <mg...@apache.org>:
> I believe https://issues.apache.org/jira/browse/WICKET-5585 is related.
> Do you use Wicket 6.16.0 ?
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
>
> On Tue, Jul 8, 2014 at 4:00 AM, smallufo <sm...@gmail.com> wrote:
>
> > sorry , There is no stack trace.
> > Because it triggers nothing , the server doesn't receive anything.
> >
> >
> >
> > 2014-07-07 14:21 GMT+08:00 Michael Haitz <mi...@1und1.de>:
> >
> > > please provide the full stacktrace.
> > >
> > > cheers,
> > > Michael
> > >
> > > Am 06.07.2014 um 05:44 schrieb smallufo <sm...@gmail.com>:
> > >
> > > > It seems working now.
> > > > But such removal also make theme-switching not working :
> > > >
> > > > If I enable the ThemeProvider :
> > > >
> > > > final ThemeProvider themeProvider = new
> > > > BootswatchThemeProvider(BootswatchTheme.Flatly);
> > > >
> > > >
> > >
> >
> settings.setJsResourceFilterName("footer-container").setThemeProvider(themeProvider);
> > > >
> > > > without "footer-container" in the BasePage
> > > >
> > > > wicket-bootstrap will throw
> > > >
> > > > WicketRuntimeException: theme does not exists: bootstrap
> > > >
> > > > at
> > > >
> > >
> >
> de.agilecoders.wicket.themes.settings.BootswatchThemeProvider.byName(BootswatchThemeProvider.java:49)
> > > >
> > > >
> > > > So I could only use the native bootstrap theme now.
> > > >
> > > >
> > > >
> > > >
> > > > 2014-07-06 11:30 GMT+08:00 smallufo <sm...@gmail.com>:
> > > >
> > > >> I found where goes wrong ,
> > > >> it's RenderJavaScriptToFooterHeaderResponseDecorator that causes the
> > > >> problem.
> > > >>
> > > >> I am not familiar with wicket-bootstrap , so I mimicked
> > wicket-bootstrap
> > > >> sample's architecture :
> > > >>
> > > >>
> > >
> >
> https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples/src/main/java/de/agilecoders/wicket/samples
> > > >>
> > > >> This is my 'not' working architecture :
> > > >> http://pastebin.com/vB3Ek2t9
> > > >>
> > > >> After removing RenderJavaScriptToFooterHeaderResponseDecorator ,
> > > >> footer-container , it works fine.
> > > >>
> > > >> http://pastebin.com/kAehvaRr
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> 2014-07-05 21:10 GMT+08:00 Francois Meillet <
> > francois.meillet@gmail.com
> > > >:
> > > >>
> > > >> Run your app in debug mode and set some breakpoint.
> > > >>>
> > > >>> eclipse
> > > >>>
> > > >>>
> > >
> >
> http://www.eclipse.org/jetty/documentation/current/debugging-with-intellij.html
> > > >>> http://www.vogella.com/tutorials/EclipseDebugging/article.html
> > > >>>
> > > >>>
> > >
> >
> http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Frun-debug%2Fref-run_debug.htm
> > > >>>
> > > >>> intellij
> > > >>>
> http://www.jetbrains.com/idea/webhelp/run-debug-configurations.html
> > > >>>
> > > >>>
> > >
> >
> http://www.jetbrains.com/idea/webhelp/creating-and-editing-run-debug-configurations.html
> > > >>>
> > > >>> François Meillet
> > > >>> Formation Wicket - Développement Wicket
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>> Le 5 juil. 2014 à 14:56, smallufo <sm...@gmail.com> a écrit :
> > > >>>
> > > >>>> 2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
> > > >>>>
> > > >>>>>
> > > >>>>> But i still find another "id6c" or "id6d" in the source code.
> > > >>>>>
> > > >>>>
> > > >>>> sorry typo :
> > > >>>>
> > > >>>> But i still *cannot* find another "id6c" or "id6d" in the source
> > > code.
> > > >>>
> > > >>>
> > > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by Martin Grigorov <mg...@apache.org>.
I believe https://issues.apache.org/jira/browse/WICKET-5585 is related.
Do you use Wicket 6.16.0 ?
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 4:00 AM, smallufo <sm...@gmail.com> wrote:
> sorry , There is no stack trace.
> Because it triggers nothing , the server doesn't receive anything.
>
>
>
> 2014-07-07 14:21 GMT+08:00 Michael Haitz <mi...@1und1.de>:
>
> > please provide the full stacktrace.
> >
> > cheers,
> > Michael
> >
> > Am 06.07.2014 um 05:44 schrieb smallufo <sm...@gmail.com>:
> >
> > > It seems working now.
> > > But such removal also make theme-switching not working :
> > >
> > > If I enable the ThemeProvider :
> > >
> > > final ThemeProvider themeProvider = new
> > > BootswatchThemeProvider(BootswatchTheme.Flatly);
> > >
> > >
> >
> settings.setJsResourceFilterName("footer-container").setThemeProvider(themeProvider);
> > >
> > > without "footer-container" in the BasePage
> > >
> > > wicket-bootstrap will throw
> > >
> > > WicketRuntimeException: theme does not exists: bootstrap
> > >
> > > at
> > >
> >
> de.agilecoders.wicket.themes.settings.BootswatchThemeProvider.byName(BootswatchThemeProvider.java:49)
> > >
> > >
> > > So I could only use the native bootstrap theme now.
> > >
> > >
> > >
> > >
> > > 2014-07-06 11:30 GMT+08:00 smallufo <sm...@gmail.com>:
> > >
> > >> I found where goes wrong ,
> > >> it's RenderJavaScriptToFooterHeaderResponseDecorator that causes the
> > >> problem.
> > >>
> > >> I am not familiar with wicket-bootstrap , so I mimicked
> wicket-bootstrap
> > >> sample's architecture :
> > >>
> > >>
> >
> https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples/src/main/java/de/agilecoders/wicket/samples
> > >>
> > >> This is my 'not' working architecture :
> > >> http://pastebin.com/vB3Ek2t9
> > >>
> > >> After removing RenderJavaScriptToFooterHeaderResponseDecorator ,
> > >> footer-container , it works fine.
> > >>
> > >> http://pastebin.com/kAehvaRr
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> 2014-07-05 21:10 GMT+08:00 Francois Meillet <
> francois.meillet@gmail.com
> > >:
> > >>
> > >> Run your app in debug mode and set some breakpoint.
> > >>>
> > >>> eclipse
> > >>>
> > >>>
> >
> http://www.eclipse.org/jetty/documentation/current/debugging-with-intellij.html
> > >>> http://www.vogella.com/tutorials/EclipseDebugging/article.html
> > >>>
> > >>>
> >
> http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Frun-debug%2Fref-run_debug.htm
> > >>>
> > >>> intellij
> > >>> http://www.jetbrains.com/idea/webhelp/run-debug-configurations.html
> > >>>
> > >>>
> >
> http://www.jetbrains.com/idea/webhelp/creating-and-editing-run-debug-configurations.html
> > >>>
> > >>> François Meillet
> > >>> Formation Wicket - Développement Wicket
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> Le 5 juil. 2014 à 14:56, smallufo <sm...@gmail.com> a écrit :
> > >>>
> > >>>> 2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
> > >>>>
> > >>>>>
> > >>>>> But i still find another "id6c" or "id6d" in the source code.
> > >>>>>
> > >>>>
> > >>>> sorry typo :
> > >>>>
> > >>>> But i still *cannot* find another "id6c" or "id6d" in the source
> > code.
> > >>>
> > >>>
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by smallufo <sm...@gmail.com>.
sorry , There is no stack trace.
Because it triggers nothing , the server doesn't receive anything.
2014-07-07 14:21 GMT+08:00 Michael Haitz <mi...@1und1.de>:
> please provide the full stacktrace.
>
> cheers,
> Michael
>
> Am 06.07.2014 um 05:44 schrieb smallufo <sm...@gmail.com>:
>
> > It seems working now.
> > But such removal also make theme-switching not working :
> >
> > If I enable the ThemeProvider :
> >
> > final ThemeProvider themeProvider = new
> > BootswatchThemeProvider(BootswatchTheme.Flatly);
> >
> >
> settings.setJsResourceFilterName("footer-container").setThemeProvider(themeProvider);
> >
> > without "footer-container" in the BasePage
> >
> > wicket-bootstrap will throw
> >
> > WicketRuntimeException: theme does not exists: bootstrap
> >
> > at
> >
> de.agilecoders.wicket.themes.settings.BootswatchThemeProvider.byName(BootswatchThemeProvider.java:49)
> >
> >
> > So I could only use the native bootstrap theme now.
> >
> >
> >
> >
> > 2014-07-06 11:30 GMT+08:00 smallufo <sm...@gmail.com>:
> >
> >> I found where goes wrong ,
> >> it's RenderJavaScriptToFooterHeaderResponseDecorator that causes the
> >> problem.
> >>
> >> I am not familiar with wicket-bootstrap , so I mimicked wicket-bootstrap
> >> sample's architecture :
> >>
> >>
> https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples/src/main/java/de/agilecoders/wicket/samples
> >>
> >> This is my 'not' working architecture :
> >> http://pastebin.com/vB3Ek2t9
> >>
> >> After removing RenderJavaScriptToFooterHeaderResponseDecorator ,
> >> footer-container , it works fine.
> >>
> >> http://pastebin.com/kAehvaRr
> >>
> >>
> >>
> >>
> >>
> >> 2014-07-05 21:10 GMT+08:00 Francois Meillet <francois.meillet@gmail.com
> >:
> >>
> >> Run your app in debug mode and set some breakpoint.
> >>>
> >>> eclipse
> >>>
> >>>
> http://www.eclipse.org/jetty/documentation/current/debugging-with-intellij.html
> >>> http://www.vogella.com/tutorials/EclipseDebugging/article.html
> >>>
> >>>
> http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Frun-debug%2Fref-run_debug.htm
> >>>
> >>> intellij
> >>> http://www.jetbrains.com/idea/webhelp/run-debug-configurations.html
> >>>
> >>>
> http://www.jetbrains.com/idea/webhelp/creating-and-editing-run-debug-configurations.html
> >>>
> >>> François Meillet
> >>> Formation Wicket - Développement Wicket
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Le 5 juil. 2014 à 14:56, smallufo <sm...@gmail.com> a écrit :
> >>>
> >>>> 2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
> >>>>
> >>>>>
> >>>>> But i still find another "id6c" or "id6d" in the source code.
> >>>>>
> >>>>
> >>>> sorry typo :
> >>>>
> >>>> But i still *cannot* find another "id6c" or "id6d" in the source
> code.
> >>>
> >>>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: [6.16] AjaxButton.onSubmit not working after upgrading to
wicket 6
Posted by Michael Haitz <mi...@1und1.de>.
please provide the full stacktrace.
cheers,
Michael
Am 06.07.2014 um 05:44 schrieb smallufo <sm...@gmail.com>:
> It seems working now.
> But such removal also make theme-switching not working :
>
> If I enable the ThemeProvider :
>
> final ThemeProvider themeProvider = new
> BootswatchThemeProvider(BootswatchTheme.Flatly);
>
> settings.setJsResourceFilterName("footer-container").setThemeProvider(themeProvider);
>
> without "footer-container" in the BasePage
>
> wicket-bootstrap will throw
>
> WicketRuntimeException: theme does not exists: bootstrap
>
> at
> de.agilecoders.wicket.themes.settings.BootswatchThemeProvider.byName(BootswatchThemeProvider.java:49)
>
>
> So I could only use the native bootstrap theme now.
>
>
>
>
> 2014-07-06 11:30 GMT+08:00 smallufo <sm...@gmail.com>:
>
>> I found where goes wrong ,
>> it's RenderJavaScriptToFooterHeaderResponseDecorator that causes the
>> problem.
>>
>> I am not familiar with wicket-bootstrap , so I mimicked wicket-bootstrap
>> sample's architecture :
>>
>> https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples/src/main/java/de/agilecoders/wicket/samples
>>
>> This is my 'not' working architecture :
>> http://pastebin.com/vB3Ek2t9
>>
>> After removing RenderJavaScriptToFooterHeaderResponseDecorator ,
>> footer-container , it works fine.
>>
>> http://pastebin.com/kAehvaRr
>>
>>
>>
>>
>>
>> 2014-07-05 21:10 GMT+08:00 Francois Meillet <fr...@gmail.com>:
>>
>> Run your app in debug mode and set some breakpoint.
>>>
>>> eclipse
>>>
>>> http://www.eclipse.org/jetty/documentation/current/debugging-with-intellij.html
>>> http://www.vogella.com/tutorials/EclipseDebugging/article.html
>>>
>>> http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Frun-debug%2Fref-run_debug.htm
>>>
>>> intellij
>>> http://www.jetbrains.com/idea/webhelp/run-debug-configurations.html
>>>
>>> http://www.jetbrains.com/idea/webhelp/creating-and-editing-run-debug-configurations.html
>>>
>>> François Meillet
>>> Formation Wicket - Développement Wicket
>>>
>>>
>>>
>>>
>>>
>>> Le 5 juil. 2014 à 14:56, smallufo <sm...@gmail.com> a écrit :
>>>
>>>> 2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
>>>>
>>>>>
>>>>> But i still find another "id6c" or "id6d" in the source code.
>>>>>
>>>>
>>>> sorry typo :
>>>>
>>>> But i still *cannot* find another "id6c" or "id6d" in the source code.
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by smallufo <sm...@gmail.com>.
It seems working now.
But such removal also make theme-switching not working :
If I enable the ThemeProvider :
final ThemeProvider themeProvider = new
BootswatchThemeProvider(BootswatchTheme.Flatly);
settings.setJsResourceFilterName("footer-container").setThemeProvider(themeProvider);
without "footer-container" in the BasePage
wicket-bootstrap will throw
WicketRuntimeException: theme does not exists: bootstrap
at
de.agilecoders.wicket.themes.settings.BootswatchThemeProvider.byName(BootswatchThemeProvider.java:49)
So I could only use the native bootstrap theme now.
2014-07-06 11:30 GMT+08:00 smallufo <sm...@gmail.com>:
> I found where goes wrong ,
> it's RenderJavaScriptToFooterHeaderResponseDecorator that causes the
> problem.
>
> I am not familiar with wicket-bootstrap , so I mimicked wicket-bootstrap
> sample's architecture :
>
> https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples/src/main/java/de/agilecoders/wicket/samples
>
> This is my 'not' working architecture :
> http://pastebin.com/vB3Ek2t9
>
> After removing RenderJavaScriptToFooterHeaderResponseDecorator ,
> footer-container , it works fine.
>
> http://pastebin.com/kAehvaRr
>
>
>
>
>
> 2014-07-05 21:10 GMT+08:00 Francois Meillet <fr...@gmail.com>:
>
> Run your app in debug mode and set some breakpoint.
>>
>> eclipse
>>
>> http://www.eclipse.org/jetty/documentation/current/debugging-with-intellij.html
>> http://www.vogella.com/tutorials/EclipseDebugging/article.html
>>
>> http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Frun-debug%2Fref-run_debug.htm
>>
>> intellij
>> http://www.jetbrains.com/idea/webhelp/run-debug-configurations.html
>>
>> http://www.jetbrains.com/idea/webhelp/creating-and-editing-run-debug-configurations.html
>>
>> François Meillet
>> Formation Wicket - Développement Wicket
>>
>>
>>
>>
>>
>> Le 5 juil. 2014 à 14:56, smallufo <sm...@gmail.com> a écrit :
>>
>> > 2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
>> >
>> >>
>> >> But i still find another "id6c" or "id6d" in the source code.
>> >>
>> >
>> > sorry typo :
>> >
>> > But i still *cannot* find another "id6c" or "id6d" in the source code.
>>
>>
>
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by smallufo <sm...@gmail.com>.
I found where goes wrong ,
it's RenderJavaScriptToFooterHeaderResponseDecorator that causes the
problem.
I am not familiar with wicket-bootstrap , so I mimicked wicket-bootstrap
sample's architecture :
https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples/src/main/java/de/agilecoders/wicket/samples
This is my 'not' working architecture :
http://pastebin.com/vB3Ek2t9
After removing RenderJavaScriptToFooterHeaderResponseDecorator ,
footer-container , it works fine.
http://pastebin.com/kAehvaRr
2014-07-05 21:10 GMT+08:00 Francois Meillet <fr...@gmail.com>:
> Run your app in debug mode and set some breakpoint.
>
> eclipse
>
> http://www.eclipse.org/jetty/documentation/current/debugging-with-intellij.html
> http://www.vogella.com/tutorials/EclipseDebugging/article.html
>
> http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Frun-debug%2Fref-run_debug.htm
>
> intellij
> http://www.jetbrains.com/idea/webhelp/run-debug-configurations.html
>
> http://www.jetbrains.com/idea/webhelp/creating-and-editing-run-debug-configurations.html
>
> François Meillet
> Formation Wicket - Développement Wicket
>
>
>
>
>
> Le 5 juil. 2014 à 14:56, smallufo <sm...@gmail.com> a écrit :
>
> > 2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
> >
> >>
> >> But i still find another "id6c" or "id6d" in the source code.
> >>
> >
> > sorry typo :
> >
> > But i still *cannot* find another "id6c" or "id6d" in the source code.
>
>
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by Francois Meillet <fr...@gmail.com>.
Run your app in debug mode and set some breakpoint.
eclipse
http://www.eclipse.org/jetty/documentation/current/debugging-with-intellij.html
http://www.vogella.com/tutorials/EclipseDebugging/article.html
http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Frun-debug%2Fref-run_debug.htm
intellij
http://www.jetbrains.com/idea/webhelp/run-debug-configurations.html
http://www.jetbrains.com/idea/webhelp/creating-and-editing-run-debug-configurations.html
François Meillet
Formation Wicket - Développement Wicket
Le 5 juil. 2014 à 14:56, smallufo <sm...@gmail.com> a écrit :
> 2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
>
>>
>> But i still find another "id6c" or "id6d" in the source code.
>>
>
> sorry typo :
>
> But i still *cannot* find another "id6c" or "id6d" in the source code.
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by smallufo <sm...@gmail.com>.
2014-07-05 20:55 GMT+08:00 smallufo <sm...@gmail.com>:
>
> But i still find another "id6c" or "id6d" in the source code.
>
sorry typo :
But i still *cannot* find another "id6c" or "id6d" in the source code.
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by smallufo <sm...@gmail.com>.
2014-07-05 20:43 GMT+08:00 Martin Grigorov <mg...@apache.org>:
>
> The code above is again Wicket 6.x/7.x but in DEVELOPMENT mode.
> It should generate also the Wicket.Ajax.*** stuff. I cannot say why it is
> missing for you.
Oops
I must got it wrong.
The two servers are wicket 6.
One is without wicket-bootstrap , and the modal works like a charm.
Another dev server , I incorporated wicket-bootstrap , it seems not
working.
After I change "DEVELOPMENT" to "DEPLOYMENT",
It generates :
<input type="submit" class="btn btn-default" name=":submit" id="*id6c*"
value="submit">
<input type="button" class="btn btn-default" name="cancel" id="*id6d*"
value="cancel">
But i still find another "id6c" or "id6d" in the source code.
I don't know if it is wicket-bootstrap that affects modal ...
The setCloseButtonCallback() , and setWindowClosedCallback() events are
correctly triggered.
Re: [6.16] AjaxButton.onSubmit not working after upgrading to wicket 6
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
On Sat, Jul 5, 2014 at 12:42 PM, smallufo <sm...@gmail.com> wrote:
> I have a LoginModal which pops up a modal with username / password for user
> to login.
> It works before wicket 6.
> After upgrading to wicket 6 , it's not working anymore.
>
> Can someone check where goes wrong ?
>
> Here is the LoginModal code :
> http://pastebin.com/hNTMs3A7
>
> And here is the LoginPage code :
> http://pastebin.com/aDDxuZmx
>
> In wicket 1.5 , it generate the following code :
> <input type="submit" name=":submit" id="*id98*" value="submit">
> <input type="button" name="cancel" id="*id99*" value="cancel">
> And I search "id98" , "id99" , I can see them 'hooked' into wicket by
>
> Wicket.Event.add(window, "domready", function(event) {
>
> Wicket.Ajax.ajax({"sc":":submit","c":"id98","u":"./page?19-1.IBehaviorListener.0-form-submit","e":"click","f":"id97","m":"POST"});;
>
> Wicket.Ajax.ajax({"sc":"cancel","c":"id99","u":"./page?19-1.IBehaviorListener.0-form-cancel","e":"click","f":"id97","m":"POST"});;
>
The code above is generated by Wicket 6.x in DEPLOYMENT mode!
>
> But after upgrading to wicket 6 (well , with wicket-bootstrap ) , it
> generates :
> <input type="submit" class="btn btn-default" name=":submit" id="*submitdc*"
> value="submit">
> <input type="button" class="btn btn-default" name="cancel" id="*canceldd*"
> value="cancel">
>
The code above is again Wicket 6.x/7.x but in DEVELOPMENT mode.
It should generate also the Wicket.Ajax.*** stuff. I cannot say why it is
missing for you.
>
> But I cannot find another "submitdc" or "canceldd" string in the source
> code.
>
> So , no matter 'submit' or 'cancel' , the console prints nothing ( I put
> some logging in the onSubmit , .
> Wicket AJAX Debug console didn't show anything.
>
> What may go wrong here ?
> Thanks.
>