On Tue, Nov 9, 2010 at 12:06 PM, Martin Makundi <martin.maku...@koodaripalvelut.com> wrote: > > (You) as a coder will be responsible for opening that can ;] For good > and for bad. Not wicket. Nor members of this discussion. >
How many times have you done this: add(new TextField(...)) when you meant to do: someSubComponent.add(new TextField(..)) With add, you'll get an exception if the ids/hierarchy don't match up. Now, what if you're queueing instead? Suppose the user does: queue(new TextField(...)) which will work perfectly fine, but they meant to do (to enforce "security"): someSubComponent.queue(new TextField(...)) Now, since security is not enforced the "designer" has the freedom to move stuff around and royally hose things up. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
