I can understand that an error needs to be raised when some markup attempts to bind to a component who's wicket id can't be found in the wicket page class or component class - that make sense but what about the other way around...
What if I wanted to provide a component class with a whole range of data: eg., name, description, image, etc., but I wanted the writer of the markup to pick and choose what he/she wants displayed even though their markup all links to a single wicket component class. For example: Markup author A wants to display name and description but no image. Markup author B wants to display a name and an image but no description. I know I can control visibility of items at the Java side but what if I wanted this control at the markup side? Could wicket be configured so it just ignored 'extra' fields that the Java classes provided but were not used by the markup instead of throwing an exception? ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
