com.ibm.etools.systems.core.ui.widgets
Class ServerConnectionSecurityForm
java.lang.Object
com.ibm.etools.systems.core.ui.SystemBaseForm
com.ibm.etools.systems.core.ui.widgets.ServerConnectionSecurityForm
- All Implemented Interfaces:
- ISystemConnectionWizardErrorUpdator
- public class ServerConnectionSecurityForm
- extends SystemBaseForm
Methods inherited from class com.ibm.etools.systems.core.ui.SystemBaseForm |
addFillerLine, addGrowableFillerLine, addPageCompleteListener, addSeparatorLine, addVerifyListener, getInputObject, getMessageLine, getOutputObject, getShell, getTheErrorMessage, handleEvent, isPageComplete, notifyVerifyListeners, removePageCompleteListener, removePageCompleteListener, setInputObject, setMessageLine, setOutputObject, setPageComplete, setShell, showErrorMessage |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
copyright
public static final String copyright
- See Also:
- Constant Field Values
ServerConnectionSecurityForm
public ServerConnectionSecurityForm(Shell shell,
ISystemMessageLine msgLine)
disable
public void disable()
enable
public void enable()
createContents
public Control createContents(Composite parent)
- Description copied from class:
SystemBaseForm
- CreateContents is the one method that must be overridden from the parent class.
In this method, we populate an SWT container with widgets and return the container
to the caller (JFace). This is used as the contents of this page.
- Specified by:
createContents
in class SystemBaseForm
- Parameters:
parent
- The parent composite- See Also:
SystemBaseForm.createContents(Composite)
setUseSSL
public void setUseSSL(boolean flag)
getUseSSL
public boolean getUseSSL()
Copyright © 2005 IBM Corp. All Rights Reserved.
Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.