Interface DebugSettingsMBean

All Known Implementing Classes:
DebugSettings

public interface DebugSettingsMBean
Debug settings.
Author:
eelcohillenius
  • Method Details

    • getComponentUseCheck

      Returns:
      true if componentUseCheck is enabled
    • isAjaxDebugModeEnabled

      Returns status of ajax debug mode.
      Returns:
      true if ajax debug mode is enabled, false otherwise
    • setAjaxDebugModeEnabled

      void setAjaxDebugModeEnabled(boolean enable)
      Enables or disables ajax debug mode.
      Parameters:
      enable -
    • setComponentUseCheck

      void setComponentUseCheck(boolean check)
      Sets componentUseCheck debug settings
      Parameters:
      check -
    • setComponentPathAttributeName

      If the parameter value is non-empty then Wicket will use it as the name of an attribute of the component tag to print the Component's path.
      Parameters:
      name -
    • getComponentPathAttributeName

      Returns:
      The name of the attribute for the ComponentTag. If null or empty then the attribute won't be rendered
      See Also:
    • setOutputMarkupContainerClassName

      void setOutputMarkupContainerClassName(boolean enable)
      Enables wrapping output of markup container in html comments that contain markup container's class name. (Useful for determining which part of page belongs to which markup file).
      Parameters:
      enable -
    • setOutputMarkupContainerClassNameStrategy

      Sets the strategy for outputting the Java class name of a markup container in the HTML output. (Useful for determining which part of page belongs to which markup file).
      Parameters:
      strategyName - the enum name of the class output strategy to use
    • isOutputMarkupContainerClassName

      Returns whether the markup container's Java class name should be written to the response.
      Returns:
      true if the markup container's Java class name should be written to response
    • isLinePreciseReportingOnAddComponentEnabled

      Returns status of line precise error reporting for added components that are not present in the markup: it points to the line where the component was added to the hierarchy in your Java classes. This can cause a significant decrease in performance, do not use in customer facing applications.
      Returns:
      true if the line precise error reporting is enabled
    • setLinePreciseReportingOnAddComponentEnabled

      Enables line precise error reporting for added components that are not present in the markup: it points to the line where the component was added to the hierarchy in your Java classes. This can cause a significant decrease in performance, do not use in customer facing applications.
      Parameters:
      enable -
    • isLinePreciseReportingOnNewComponentEnabled

      Returns status of line precise error reporting for new components that are not present in the markup: it points to the line where the component was created in your Java classes. This can cause a significant decrease in performance, do not use in customer facing applications.
      Returns:
      true if the line precise error reporting is enabled
    • setLinePreciseReportingOnNewComponentEnabled

      Enables line precise error reporting for new components that are not present in the markup: it points to the line where the component was created in your Java classes. This can cause a significant decrease in performance, do not use in customer facing applications.
      Parameters:
      enable -
    • setDevelopmentUtilitiesEnabled

      void setDevelopmentUtilitiesEnabled(boolean enable)
      Enables all of the panels and pages, etc, from wicket-devutils package.
      Parameters:
      enable -
    • isDevelopmentUtilitiesEnabled

      Are all of the panels and pages, etc, from wicket-devutils package enabled?
      Returns:
      true if all of the panels and pages, etc, from wicket-devutils package are enabled