Home >> All >> javax >> ide >> [ debug Javadoc ]

• javax.ide.debug: Javadoc index of package javax.ide.debug.


Package Samples:

• javax.ide.debug

Classes:

• ClientConnector: ClientConnectors expect extension writers to start the debuggee process by calling Connector.startDebuggee(java.util.Map) 55 . Once the debuggee is launched, the extension writer can attach the debugger to the debugge by calling attachDebugger() 55 . IDE providers must provide an implementation of this interface. Extension writers can access the Connector through the Debugger.getClientConnector(javax.ide.command.Context) 55 method.
• Connector: The Connector interface is used to connect to a debugging session. The Connector object is used to start the debuggee or to retrieve command line options so the extension can start the debuggee itself. IDE providers must provide an implementation of this interface. Extension writers can access the Connector through the Debugger.getClientConnector(javax.ide.command.Context) 55 and Debugger.getServerConnector(javax.ide.command.Context) 55 methods.
• ServerConnector: ServerConnectors allow clients to start the debugger listening by calling the method startListening() 55 waiting for a debuggee process to start. The debugge process can be started by the extension or the IDE. When the debuggee process is launched, the listening debugger will automatically accept the connection. IDE providers must provide an implementation of this interface. Extension writers can access the Connector through the Debugger.getServerConnector(javax.ide.command.Context) 55 method.
• Debugger: The Debugger can be used to start the debuggee or to retrieve command line options so the extension can start the debuggee itself. IDE providers must provide an implementation of getClientConnector( Context ) 55 and getServerConnector(Context) 55 .

Home | Contact Us | Privacy Policy | Terms of Service