Package org.apache.wicket.jmx.wrapper
Class DebugSettings
- java.lang.Object
-
- org.apache.wicket.jmx.wrapper.DebugSettings
-
- All Implemented Interfaces:
DebugSettingsMBean
public class DebugSettings extends Object implements DebugSettingsMBean
Exposes Application related functionality for JMX.- Author:
- eelcohillenius
-
-
Constructor Summary
Constructors Constructor Description DebugSettings(org.apache.wicket.Application application)Create.
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description StringgetComponentPathAttributeName()booleangetComponentUseCheck()booleanisAjaxDebugModeEnabled()Returns status of ajax debug mode.booleanisDevelopmentUtilitiesEnabled()Are all of the panels and pages, etc, from wicket-devutils package enabled?booleanisLinePreciseReportingOnAddComponentEnabled()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.booleanisLinePreciseReportingOnNewComponentEnabled()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.booleanisOutputMarkupContainerClassName()Returns whether the output of markup container's should be wrapped by comments containing the container's class name.voidsetAjaxDebugModeEnabled(boolean enable)Enables or disables ajax debug mode.voidsetComponentPathAttributeName(String name)If the parameter value is non-empty then Wicket will use it as the name of an attribute of the component tag to print theComponent's path.voidsetComponentUseCheck(boolean check)Sets componentUseCheck debug settingsvoidsetDevelopmentUtilitiesEnabled(boolean enable)Enables all of the panels and pages, etc, from wicket-devutils package.voidsetLinePreciseReportingOnAddComponentEnabled(boolean enable)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.voidsetLinePreciseReportingOnNewComponentEnabled(boolean enable)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.voidsetOutputMarkupContainerClassName(boolean enable)Enables wrapping output of markup container in html comments that contain markup container's class name.
-
-
-
Constructor Detail
-
DebugSettings
public DebugSettings(org.apache.wicket.Application application)
Create.- Parameters:
application-
-
-
Method Detail
-
getComponentUseCheck
public boolean getComponentUseCheck()
- Specified by:
getComponentUseCheckin interfaceDebugSettingsMBean- Returns:
- true if componentUseCheck is enabled
- See Also:
DebugSettingsMBean.getComponentUseCheck()
-
isAjaxDebugModeEnabled
public boolean isAjaxDebugModeEnabled()
Description copied from interface:DebugSettingsMBeanReturns status of ajax debug mode.- Specified by:
isAjaxDebugModeEnabledin interfaceDebugSettingsMBean- Returns:
- true if ajax debug mode is enabled, false otherwise
- See Also:
DebugSettingsMBean.isAjaxDebugModeEnabled()
-
setAjaxDebugModeEnabled
public void setAjaxDebugModeEnabled(boolean enable)
Description copied from interface:DebugSettingsMBeanEnables or disables ajax debug mode.- Specified by:
setAjaxDebugModeEnabledin interfaceDebugSettingsMBean
-
setComponentUseCheck
public void setComponentUseCheck(boolean check)
Description copied from interface:DebugSettingsMBeanSets componentUseCheck debug settings- Specified by:
setComponentUseCheckin interfaceDebugSettingsMBean
-
setComponentPathAttributeName
public void setComponentPathAttributeName(String name)
Description copied from interface:DebugSettingsMBeanIf the parameter value is non-empty then Wicket will use it as the name of an attribute of the component tag to print theComponent's path.- Specified by:
setComponentPathAttributeNamein interfaceDebugSettingsMBean
-
getComponentPathAttributeName
public String getComponentPathAttributeName()
- Specified by:
getComponentPathAttributeNamein interfaceDebugSettingsMBean- Returns:
- The name of the attribute for the
ComponentTag. Ifnullor empty then the attribute won't be rendered - See Also:
DebugSettingsMBean.setComponentPathAttributeName(String)
-
setOutputMarkupContainerClassName
public void setOutputMarkupContainerClassName(boolean enable)
Description copied from interface:DebugSettingsMBeanEnables 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).- Specified by:
setOutputMarkupContainerClassNamein interfaceDebugSettingsMBean
-
isOutputMarkupContainerClassName
public boolean isOutputMarkupContainerClassName()
Description copied from interface:DebugSettingsMBeanReturns whether the output of markup container's should be wrapped by comments containing the container's class name.- Specified by:
isOutputMarkupContainerClassNamein interfaceDebugSettingsMBean- Returns:
- true if the markup container's class name should be written to response
-
isLinePreciseReportingOnAddComponentEnabled
public boolean isLinePreciseReportingOnAddComponentEnabled()
Description copied from interface:DebugSettingsMBeanReturns 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.- Specified by:
isLinePreciseReportingOnAddComponentEnabledin interfaceDebugSettingsMBean- Returns:
- true if the line precise error reporting is enabled
-
setLinePreciseReportingOnAddComponentEnabled
public void setLinePreciseReportingOnAddComponentEnabled(boolean enable)
Description copied from interface:DebugSettingsMBeanEnables 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.- Specified by:
setLinePreciseReportingOnAddComponentEnabledin interfaceDebugSettingsMBean
-
isLinePreciseReportingOnNewComponentEnabled
public boolean isLinePreciseReportingOnNewComponentEnabled()
Description copied from interface:DebugSettingsMBeanReturns 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.- Specified by:
isLinePreciseReportingOnNewComponentEnabledin interfaceDebugSettingsMBean- Returns:
- true if the line precise error reporting is enabled
-
setLinePreciseReportingOnNewComponentEnabled
public void setLinePreciseReportingOnNewComponentEnabled(boolean enable)
Description copied from interface:DebugSettingsMBeanEnables 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.- Specified by:
setLinePreciseReportingOnNewComponentEnabledin interfaceDebugSettingsMBean
-
setDevelopmentUtilitiesEnabled
public void setDevelopmentUtilitiesEnabled(boolean enable)
Description copied from interface:DebugSettingsMBeanEnables all of the panels and pages, etc, from wicket-devutils package.- Specified by:
setDevelopmentUtilitiesEnabledin interfaceDebugSettingsMBean
-
isDevelopmentUtilitiesEnabled
public boolean isDevelopmentUtilitiesEnabled()
Description copied from interface:DebugSettingsMBeanAre all of the panels and pages, etc, from wicket-devutils package enabled?- Specified by:
isDevelopmentUtilitiesEnabledin interfaceDebugSettingsMBean- Returns:
- true if all of the panels and pages, etc, from wicket-devutils package are enabled
-
-