Class PanelMarkupSourcingStrategy

  • All Implemented Interfaces:
    IMarkupSourcingStrategy

    public class PanelMarkupSourcingStrategy
    extends AssociatedMarkupSourcingStrategy
    The Panel components markup sourcing strategy.

    The strategy supports two modes on how to handle the body markup. A typical Panel will ignore the body markup and replace it with the associated markup. The body markup is allowed to have raw markup only and no Wicket components. But e.g. a Border component will associate the body markup with a Body component which renders the markup including all any number of child Components.

    Author:
    Juergen Donnerstag
    • Constructor Detail

      • PanelMarkupSourcingStrategy

        public PanelMarkupSourcingStrategy​(String wicketTagName,
                                           boolean allowWicketComponentsInBodyMarkup)
        Constructor.
        Parameters:
        wicketTagName - The tag name for <wicket:'name' ..>. Please note that any such tag must have been registered via WicketTagIdentifier.registerWellKnownTagName("name");
        allowWicketComponentsInBodyMarkup - false for Panel and true for Border components. If Panel then the body markup should only contain raw markup, which is ignored (removed), but no Wicket Component. With Border components, the body markup will be associated with the Body Component.
      • PanelMarkupSourcingStrategy

        public PanelMarkupSourcingStrategy​(boolean allowWicketComponentsInBodyMarkup)
        Constructor.
        Parameters:
        allowWicketComponentsInBodyMarkup - false for Panel and true for Border components. If Panel then the body markup should only contain raw markup, which is ignored (removed), but no Wicket Component. With Border components, the body markup will be associated with the Body Component.