To use DTSL, a client must create a
DTSLConnection object using the DTSL
ConnectionManager class (
ConnectionManager has static methods that allow the
DTSLConnection object to be created from a set of
connection parameters. After a
object is obtained, calling its
DTSLConfiguration object which contains
all the target component objects.
When the DTSL
creates a new
DTSLConnection, it assigns a unique key
to it. It constructs this key from the connection properties:
dtsl_config_script: the absolute path to the DTSL Jython
dtsl_config: the Jython DTSL class name
config_file: the absolute path to the RDDI configuration
dtsl_config_options: optional DTSL options (a hash of the
content of the DTSL options file)
rddi_retarget_address: optional re-target address for the
- possibly other input.
If the DTSL
ConnectionManager detects an
attempt to connect to an already existing
DTSLConnection (that is, the connection key matches an existing
DTSLConnection instance) then DTSL returns the already
existing instance. There can only be one
DTSLConnection with any given key.
DTSLConnection can also be created by
obtaining an existing DTSL instance key and requesting a connection to that instance.
Both DS-5 Debugger and
third-party Eclipse plugins can therefore connect to an existing
DTSLConnection instance. If the DS-5 Debugger creates the
DTSLConnection instance for a platform, then a
third-party plugin can connect to the same instance by one of two methods:
- Use an identical set of connection properties.
- Arrange to get the
DTSLConnection instance key
from the debugger, and use that key to make the connection.
DTSL reference-counts connections to a platform instance and only closes the
DTSLConnection instance when all clients have