Re: [ANNOUNCE] WicketStuff 7.3.0 Released

On Tue, May 10, 2016 at 9:27 PM, Gabriel Landon wrote: > A big thank you to kkaravitis for his work on the portlet bridge. > Yes! Thank you, Kostas! > I will definitely use it within the year to upgrade to wicket 7 and liferay > 6.2. > > -- > View this message in context: >

Re: [ANNOUNCE] WicketStuff 7.3.0 Released

A big thank you to kkaravitis for his work on the portlet bridge. I will definitely use it within the year to upgrade to wicket 7 and liferay 6.2. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/ANNOUNCE-WicketStuff-7-3-0-Released-tp4674633p4674636.html Sent from the

Re: [ANNOUNCE] WicketStuff 7.3.0 Released

Thanks! On Tue, May 10, 2016 at 9:26 PM, Martin Grigorov wrote: > WicketStuff core 7.3.0 based on Apache Wicket 7.3.0 is released and > available > at Maven Central. > > The changelog since 7.2.0 is: > > kkaravitis (33): > Override the System Mapper functionality for

[ANNOUNCE] WicketStuff 7.3.0 Released

WicketStuff core 7.3.0 based on Apache Wicket 7.3.0 is released and available at Maven Central. The changelog since 7.2.0 is: kkaravitis (33): Override the System Mapper functionality for portlet specific purposes added support for wicket ajax requets. The

[ANNOUNCE] WicketStuff 6.23.0 is released

Hi, WicketStuff core 6.23.0 based on Apache Wicket 6.23.0 is released and available at Maven Central. The changelog since 6.22.0 is: Andrea Del Bene (2): [restannotations] Issue #477 [restannotations] Issue #490 Martin Tzvetanov Grigorov (2): [native-web-socket-javax]

Re: Which model to use for forwarding form processing results?

Thorsten, Yes, that is normal behavior I think - for invisible components we either wrap it in a container which receives the event, or let the page be the coordinator. Invisible components also don’t receive clicks on links etc, so I think this was done to be consistent. Met vriendelijke

Re: Which model to use for forwarding form processing results?

Guten Tag Bas Gooren, am Dienstag, 10. Mai 2016 um 13:43 schrieben Sie: > This sounds like a good use-case for an event. Thanks for this hint, I totally forgot about it and decided to give it a try. There was a pitfall in my case, though: Component.canCallListenerInterface is asked before an

Re: [wicketstuff-restannotations] AbstractRestResource.toObject makes it impossible for mapped methods to know a parameter conversion went wrong.

I confirm version 6.23.0 fixed the problem. Thank you for the great support! Kind regards, Fabio On Thu, Apr 28, 2016 at 12:02 PM, Fabio Fioretti < windom.macroso...@gmail.com> wrote: > Thanks Andrea, that would be excellent! > > Keep up the great work, > Fabio > > On Thu, Apr 28, 2016 at

Re: Which model to use for forwarding form processing results?

Hi Thorsten, This sounds like a good use-case for an event. You can have the form broadcast an event to the page, and let any component that needs to redraw based on the data handle that event. This provides a nice decoupling between the form result and 0…n other components in your page that

Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

Hi Ernesto, We are fully aware of this! That's why the migration guide is split into "API breaks" and "Behavior changes". API breaks usually are easy to fix because the compiler complains about them. Behavior changes are not problem for Semantic Versioning but we postpone them to major versions

Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

Tobias, > I think as long as the third party library is not Wicket 7.0 proofed you > should use it careful. Because of this the migration guide is very useful - > each framework should be checked when upgrade a major version. > Mind that I'm fully aware of the personal sacrifices some people

Which model to use for forwarding form processing results?

Hi all, I have one and the same form on different pages used to provide some input data which is afterwards used by the form's onSubmit handler to request some complex data structure from a 3rd party service. This result needs to be forwarded to the caller/owner of the form, mainly pages, so