Re: Implications of setRecreateBookmarkablePagesAfterExpiry()
Hi Ravi, Please test my suggested patch attached in the ticket. Thank you! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jul 11, 2016 at 10:50 AM, Martin Grigorov wrote: > Sorry! > It is vacation season :) > I'll try to take a look in the coming days! > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jul 11, 2016 at 9:00 AM, Ravi wrote: > >> Hi, >> >> was the quickstart any help? >> >> Regards, >> >> Ravi >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Implications-of-setRecreateBookmarkablePagesAfterExpiry-tp4674899p4675069.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >
Re: Wicket Bootstrap 0.9.17 & 0.10.7 are released
Thanks! On Wed, Jul 13, 2016 at 6:43 PM, Martin Grigorov wrote: > Wicket Bootstrap 0.9.17 (built against Wicket 6.23.0) and 0.10.7 (built > against Wicket 7.3.0) have been released and soon will be available at > Maven Central! > > New components: > - Bootstrap Markdown editor: http://wb-mgrigorov.rhcloud.com/markdown > - Bootstrap Reting: http://wb-mgrigorov.rhcloud.com/extensions#rating > > The changelog is: > > Martin Tzvetanov Grigorov (67): > [maven-release-plugin] prepare for next development iteration > Fixes #587 - update the versions in README > Update dependencies > Merge branch 'master' into wicket-7.x > s/0.9.16/0.10.6/ > Update JS dependencies. > Update JS dependencies. > Fixes #586 - Update Bootstrap Select to 1.10.0 > Fixes #579 - "Start upload" button type should not be "submit" > because this was it makes normal (non-Ajax) submit > Fix JS issue in application.js > WICKET-6102 StackoverflowError related to enclosures > Use Logger for debug messages > Fixes #579 - "Start upload" button type should not be "submit" > because this was it makes normal (non-Ajax) submit > Fix JS issue in application.js > WICKET-6102 StackoverflowError related to enclosures > Merge branch 'master' into wicket-7.x > PR #592 - Use item's index to find the first carousel item > Fixes #593 - Fix the file names of the resources for Material Design > theme > Update the Google Theme's CSS resources > Update Bootswatch's theme CSS resources > Revert the default theme for the samples application to Bootswatch > Update Metro Theme > Fixes #589 - Add integration with Bootstrap-Markdown > Merge branch 'master' into wicket-7.x > Fix compilation issue > [toggle] Fixes #595: hide BootstrapToggleConfig#with(On|Off)Label > methods and add javadoc that BootstrapToggle#get(On|off)Label() should be > used for better i18n support > Merge branch 'master' into wicket-7.x > Update Wicket to 6.23.0 and Wicket-Webjars to 0.4.9 > Update Wicket to 7.3.0 and Wicket-Webjars to 0.5.4 > Fixes #597 - NotificationMessage#escapeModelStrings should be 'true' > by default > Merge branch 'master' into wicket-7.x > Fixes #599 - Initialize the children in the constructor because > otherwise there are not available in many public methods like #header(), > #setHeaderVisible(), etc. > Merge branch 'master' into wicket-7.x > Fixes #598 - Set the "pagination" CSS class on the element > Fixes #600 - Support Pagination sizing > Merge branch 'master' into wicket-7.x > Fixes #601 - Initialize BootstrapCheckbox's children eagerly in its > constructor > Merge branch 'master' into wicket-7.x > Remove implicit modifiers > Fixes #605 - Do not render for inline > checkboxes > Merge branch 'master' into wicket-7.x > Dependency updates > Merge branch 'master' into wicket-7.x > Fixes #606 - First add the link to ButtonList and then configure it. > Merge branch 'master' into wicket-7.x > Merge branch 'master' into wicket-7.x > Issue #602 - Minor improvements > Merge branch 'master' into wicket-7.x > [rating] Issue #609 - Change the 'step' to Integer > [rating] Issue #609 - Change the type of RatingCssResourceReference > to CssResourceReference > [rating] Issue #609 - Change to AjaxFormComponentUpdatingBehavior so > that the Ajax updates actually send the new model to the server > [rating] Issue #609 - RatingField should be used with type="hidden"/> > [rating] Issue #609 - Code style formatting > Fixes #612 - Initialize the ListBehavior eagerly, in the constructor > [datetimepicker] Fixes #611 - Use predefined date pattern for > minDate, maxDate and defaultDate > [datetimepicker] Add 'defaultDate' and 'useStrict' options. > Merge branch 'master' into wicket-7.x > Code formatting > Merge branch 'master' into wicket-7.x > [DataTable] Fix a compilation problem due to API break in Wicket 7.0 > Update Material Design theme > Update Bootswatch themes > Update Google theme > Fixes #626 - Remove 'wicket' theme > Update dependencies > Merge branch 'master' into wicket-7.x > [maven-release-plugin] prepare release bootstrap-parent-0.10.7 > > heryqk (13): > Adding Contextual Classes support for tables. > Adding support for Bootstrap Panel > Mods requested by martin-g > Removing old PanelType CSS for runtime panel type change support. > Added PanelBehavior to class. Will not create a new instance of > PanelBehavior at onBeforeRender(). > Added getSize() to allow for Override in the new > BootstrapNavigationTooblar > Added a bootstrap styled Navigator label which leverages the > BootstrapPagingNavigator.Size > Adding a Bootstrap style border
Wicket Bootstrap 0.9.17 & 0.10.7 are released
Wicket Bootstrap 0.9.17 (built against Wicket 6.23.0) and 0.10.7 (built against Wicket 7.3.0) have been released and soon will be available at Maven Central! New components: - Bootstrap Markdown editor: http://wb-mgrigorov.rhcloud.com/markdown - Bootstrap Reting: http://wb-mgrigorov.rhcloud.com/extensions#rating The changelog is: Martin Tzvetanov Grigorov (67): [maven-release-plugin] prepare for next development iteration Fixes #587 - update the versions in README Update dependencies Merge branch 'master' into wicket-7.x s/0.9.16/0.10.6/ Update JS dependencies. Update JS dependencies. Fixes #586 - Update Bootstrap Select to 1.10.0 Fixes #579 - "Start upload" button type should not be "submit" because this was it makes normal (non-Ajax) submit Fix JS issue in application.js WICKET-6102 StackoverflowError related to enclosures Use Logger for debug messages Fixes #579 - "Start upload" button type should not be "submit" because this was it makes normal (non-Ajax) submit Fix JS issue in application.js WICKET-6102 StackoverflowError related to enclosures Merge branch 'master' into wicket-7.x PR #592 - Use item's index to find the first carousel item Fixes #593 - Fix the file names of the resources for Material Design theme Update the Google Theme's CSS resources Update Bootswatch's theme CSS resources Revert the default theme for the samples application to Bootswatch Update Metro Theme Fixes #589 - Add integration with Bootstrap-Markdown Merge branch 'master' into wicket-7.x Fix compilation issue [toggle] Fixes #595: hide BootstrapToggleConfig#with(On|Off)Label methods and add javadoc that BootstrapToggle#get(On|off)Label() should be used for better i18n support Merge branch 'master' into wicket-7.x Update Wicket to 6.23.0 and Wicket-Webjars to 0.4.9 Update Wicket to 7.3.0 and Wicket-Webjars to 0.5.4 Fixes #597 - NotificationMessage#escapeModelStrings should be 'true' by default Merge branch 'master' into wicket-7.x Fixes #599 - Initialize the children in the constructor because otherwise there are not available in many public methods like #header(), #setHeaderVisible(), etc. Merge branch 'master' into wicket-7.x Fixes #598 - Set the "pagination" CSS class on the element Fixes #600 - Support Pagination sizing Merge branch 'master' into wicket-7.x Fixes #601 - Initialize BootstrapCheckbox's children eagerly in its constructor Merge branch 'master' into wicket-7.x Remove implicit modifiers Fixes #605 - Do not render for inline checkboxes Merge branch 'master' into wicket-7.x Dependency updates Merge branch 'master' into wicket-7.x Fixes #606 - First add the link to ButtonList and then configure it. Merge branch 'master' into wicket-7.x Merge branch 'master' into wicket-7.x Issue #602 - Minor improvements Merge branch 'master' into wicket-7.x [rating] Issue #609 - Change the 'step' to Integer [rating] Issue #609 - Change the type of RatingCssResourceReference to CssResourceReference [rating] Issue #609 - Change to AjaxFormComponentUpdatingBehavior so that the Ajax updates actually send the new model to the server [rating] Issue #609 - RatingField should be used with [rating] Issue #609 - Code style formatting Fixes #612 - Initialize the ListBehavior eagerly, in the constructor [datetimepicker] Fixes #611 - Use predefined date pattern for minDate, maxDate and defaultDate [datetimepicker] Add 'defaultDate' and 'useStrict' options. Merge branch 'master' into wicket-7.x Code formatting Merge branch 'master' into wicket-7.x [DataTable] Fix a compilation problem due to API break in Wicket 7.0 Update Material Design theme Update Bootswatch themes Update Google theme Fixes #626 - Remove 'wicket' theme Update dependencies Merge branch 'master' into wicket-7.x [maven-release-plugin] prepare release bootstrap-parent-0.10.7 heryqk (13): Adding Contextual Classes support for tables. Adding support for Bootstrap Panel Mods requested by martin-g Removing old PanelType CSS for runtime panel type change support. Added PanelBehavior to class. Will not create a new instance of PanelBehavior at onBeforeRender(). Added getSize() to allow for Override in the new BootstrapNavigationTooblar Added a bootstrap styled Navigator label which leverages the BootstrapPagingNavigator.Size Adding a Bootstrap style border for Header Order By using IconType Added a bootstrap styled HeadersToolbar Added a Bootstrap styled NavigationToolbar A Bootstrap styled DefaultDataTable Changes requested by martin-g Updated the sort icons to use Glyphicon sort by attributes and aligned
Re: Wicket @SpringBean - @Autowired properties not Initialized
Okay, scratch this question. It's working. I was just looking at the Eclipse debugger and saw all the @Autowired fields were null. I failed to read this segment of the Javadoc: * A lazy init proxy waits until the first method invocation before it uses the * {@link IProxyTargetLocator} to retrieve the object to which the method invocation will be * forwarded. When actually running the code with the @SpringBean everything works as expected! Thanks for your quick reply! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-SpringBean-Autowired-properties-not-Initialized-tp4675091p4675093.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket @SpringBean - @Autowired properties not Initialized
Hi, This should just work as you expect it to. I don't remember any problems related to this in 6.11. But if you can reproduce the problem with 6.23/7.3.0 in a quickstart app then please attach it to JIRA. Thanks! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jul 13, 2016 at 2:37 PM, mashleyttu wrote: > Hi All, > > When we include a property on our Page class with the @SpringBean > annotation > it doesn't seem to initialized the @Autowired properties of the bean when > using the GCLib Proxy. If we set wrapInProxy to false as follows, wicket > skips the GCLib code and simply pulls the bean using Springs getBean > method. > > this.getComponentInstantiationListeners().add(new > SpringComponentInjector(this,AppCommon.getApplicationContext(),false)); > > This has the side effect of us having to mark all our @SpringBean > properties > as transient and call Injector.get().inject(this); for all of our AJAX > calls. > > Shouldn't the GCLib proxy still pull the bean from the Spring context and > then wrap it in a proxy? > > Note: We are still using an older version of Wicket 6.11. Maybe this has > been updated in future releases. > > Thanks, > Matt > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-SpringBean-Autowired-properties-not-Initialized-tp4675091.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Wicket @SpringBean - @Autowired properties not Initialized
Hi All, When we include a property on our Page class with the @SpringBean annotation it doesn't seem to initialized the @Autowired properties of the bean when using the GCLib Proxy. If we set wrapInProxy to false as follows, wicket skips the GCLib code and simply pulls the bean using Springs getBean method. this.getComponentInstantiationListeners().add(new SpringComponentInjector(this,AppCommon.getApplicationContext(),false)); This has the side effect of us having to mark all our @SpringBean properties as transient and call Injector.get().inject(this); for all of our AJAX calls. Shouldn't the GCLib proxy still pull the bean from the Spring context and then wrap it in a proxy? Note: We are still using an older version of Wicket 6.11. Maybe this has been updated in future releases. Thanks, Matt -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-SpringBean-Autowired-properties-not-Initialized-tp4675091.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Add attribute to label tag in CheckBoxMultipleChoice component
Hi, The only way I see is to override org.apache.wicket.markup.html.form.CheckBoxMultipleChoice#appendOptionHtml() Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jul 13, 2016 at 11:56 AM, Alberto wrote: > > Hello, > in CheckBoxMultipleChoice component the method > getAdditionalAttributes() is used to add an attribute to the input tag. > Is there a simple way to do the same for the label tag? > Or a way to add a new tag (e.g. ) inside label tag? > > getPrefix() and getSuffix() add content outside of label tag. > > Regards > > Alberto > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Add attribute to label tag in CheckBoxMultipleChoice component
Hello, in CheckBoxMultipleChoice component the method getAdditionalAttributes() is used to add an attribute to the input tag. Is there a simple way to do the same for the label tag? Or a way to add a new tag (e.g. ) inside label tag? getPrefix() and getSuffix() add content outside of label tag. Regards Alberto - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Single Page Applications (SPA), Wicket and the history ajax back issue
Hi, On Thu, Jul 7, 2016 at 11:28 PM, Martin Grigorov wrote: > Hi, > > It seems you use Wicket for several years now and you have no idea how to > use it! > Yes perhaps Martin, I do try but there's a lot too it. > > I have done this for a client of mine 4 years ago. > And I have explained how to do it few times in the mailing lists. > You could use HTML5 History API to manipulate the browser url on each Ajax > call. If you need to support old browsers (why?! almost no one does these > days) then you should use some JS library that falls back to using the > location fragment/hash. > The support of "back/forward" buttons is just registering an > AjaxEventBehavior that listens for "popState"/"hashchange" event. > > I did some extensive searching and only found a couple of threads about this: http://apache-wicket.1842946.n4.nabble.com/Wicket7-History-API-support-for-navigable-AJAX-pages-components-td4660502.html The main issue seems that the page map is not updated (just overriden) for ajax requests from my reading before. I came to the conclusion trying to get wicket to support the back button would be difficult and somewhat hacky. It seems we'd end up with unknown behaviour and issues possibly occurring and therefore too much of a risk. Hence this thread. > > I will try to find time to write a blog article with a demo app at > wicketinaction.com soon. > > That would be great. > >
Re: Single Page Applications (SPA), Wicket and the history ajax back issue
> So you don't use Ajax because of missing back button support? > We have a feature request for that, but it didn't spark much interest: > > https://issues.apache.org/jira/browse/WICKET-5290 Yes in a lot of cases unfortunately. It confuses a lot of non tech users who are used to using the navigation back button - we did some user testing and a fair number of people still use it, from from a UX perspective its not great dropping it. I did't see that request unfortunately > > > Have fun > Sven > > > > On 07.07.2016 14:13, Wayne W wrote: > >> Hi Sven, >> >> of course: Ok so this is simplified somewhat: lets say we have 4 main tab >> areas of the application: Contacts, Files, Calendar, Tasks. When a user >> navigates from one area to the next we need to currently do a whole page >> refresh, where in fact all we really need to do is refresh a sub panel via >> ajax. This already is more 'old school' as I put it in the fact the user >> experiences the whole page refreshing rather than say a loading/spinner in >> the main panel. We want to make the web pp fell more 'app like' rather >> than >> a succession of web pages. Another example is say we are in the "File" tab >> and we want to drill down through some folders, at the moment we need to >> refresh the page if we want to support the back button rather than load >> via >> ajax. >> >> It just gives a much less slick experience as the page reloads visually, >> and there is more data sent over the wire - slower page loads. But >> ultimately it about the users impression of the app and feeling like an >> app >> rather than a bunch of pages. >> >> >> On Thu, Jul 7, 2016 at 1:01 PM, Sven Meier wrote: >> >> Hi, >>> >>> it would be interesting to hear what limitations you're fighting against. >>> As a server-side rendered framework Wicket surely isn't the new kid on >>> the >>> block, but I can't think of anything forcing your application to be 'old >>> school'. >>> >>> Can you be more specific? >>> >>> Sven >>> >>> >>> >>> Am 7. Juli 2016, 13:23, um 13:23, Wayne W >>> schrieb: >>> Hi, we're been using wicket for some time now and we have a very established application used by many clients. It is however feeling some what dated, due to the fact the we have to constantly reload pages to access different functionality/areas if the app. We use ajax fairly heavily within each functional area. The problem is we are starting to 'feel' old school and we're loosing out to the competition that are based on the lasted SPA type JS frameworks talking to APIs. They just feel more slick and more responsive. Doing some research it seems thats it not possible to transform our current wicket app into this form, mainly due to the issues around wicket ajax state storage and history URL support in older browsers. Is this something the Wicket is never going to to attempt to support? I cannot find anything around this subject. Having a huge investment in our Wicket based application, its going to be very very painful to move away from which we must do if we cannot keep up with the competition due to framework limitations. many thanks >>> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >