Take a look on IComponentResolver. If your Page implements this interface, it can serve optional components requested by the markup or it can serve hidden components in case you want to exclude something from some targets.
Sven Jan Kriesten wrote: > hi, > > is it possible to have wicket configured to ignore references which can't be > resolved? > > e.g. trying to add a component which doesn't exist in the markup (ok, this > could > be done by catching the thrown exception, but only if the 'add'-method is > used) > or not adding a component which is referenced in the markup. > > background: i have different targets to publish from the same content system. > not all targets need all information displayed, so some markup files miss > certain id's (same classes are used, markup used is decided by the target to > publish to). > > another use-case would be having generic markup files which are used as > 'default', containing more wicket-tags than actually served by the > corresponding > class. > > optimal would be a page-based property > > greets from sunny hamburg! :-) > > --- jan. > > > > ------------------------------------------------------------------------- > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > > ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
