Re: Component disabled if it contains data

Good to know :)   Ursprüngliche Nachricht   Von:martijn.dasho...@gmail.com Gesendet:19. April 2016 9:02 nachm. An:users@wicket.apache.org Antworten:users@wicket.apache.org Betreff:Re: Component disabled if it contains data On Tue, Apr 19, 2016 at 7:28 PM, sub es wrote: > In my

Re: Component disabled if it contains data

On Tue, Apr 19, 2016 at 7:28 PM, sub es wrote: > In my opinion one should always validate inputs coming from a submit even if > the inputs were disabled. Using tools like firebug, one can easily change > values of disabled inputs and submit those changed values. Atleast I

Re: Component disabled if it contains data

+1 IMHO a good solution. Have fun Sven On 19.04.2016 19:43, Andrew Geery wrote: 1. Create a Wicket Behavior that encapsulates your requirement. Maybe something like this: public class DisableWhenFilledBehavior extends Behavior { @Override public void onConfigure(Component component) {

Re: Component disabled if it contains data

1. Create a Wicket Behavior that encapsulates your requirement. Maybe something like this: public class DisableWhenFilledBehavior extends Behavior { @Override public void onConfigure(Component component) { component.setEnabled(component.getDefaultModel() == null); } } 2. Add the behavior to

Re: Component disabled if it contains data

In my opinion one should always validate inputs coming from a submit even if the inputs were disabled. Using tools like firebug, one can easily change values of disabled inputs and submit those changed values. Atleast I don't know about wicket not submitting disabled inputs, though I would not

Component disabled if it contains data

Hello, I'm using Wicket 6, with Java 1.7. I'm new to Wicket and I would like to know what is the best way to implement the following: -I have a webpage with several input fields bound to a db table, and a submit button. - two of the fields can be empty when submitting the changes to the db. -

Re: Adding multiple WebSocketBehavior instances to the same page

Hi, You could use something like: if (getBehaviors(WebSocketBehavior.class).isEmpty()) { add(new WebSocketBehavior() {...}); } This way only one instance will be added to one page instance. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Apr 19, 2016 at

Adding multiple WebSocketBehavior instances to the same page

Hi all, in the upcoming Syncope 2.0 we are enjoying WebSocketBehavior for making our admin console UI more reactive. It mostly works - thanks for this! - but we are experiencing some troubles lately. There is a class BasePage which is extended by all other pages, and contains a panel which