[platform-debug-dev] Launch configuration support not using dialog

[desarmo@xxxxxxxxxx]

I am working on our launch configurations and I really like the design for
launching through the dialog.  However, I have run into difficulty with our
non-dialog scenario when an engine (or kicker) calls our daemon and
specifies the launch configuration (or launch configuration type) that
should be used for the launch. I cannot use
ILaunchConfiguration.launch(String, IProgressMonitor) because I have to
pass additional parameters to the delegate.  Therefore,  I need the
LaunchConfiguration.getDelegate() method to be public so that I know where
to delegate the launch request.

In response to the launch lifecycle changes proposed yesterday, I believe
this is OK provided that I can complete steps 1-4 myself (for the case
above) up to the point that the launch configuration takes over, i.e., I
won't be calling launch()...   I also still need to be able to create and
register a launch without going through a launch configuration.

<steps copied from Darin's proposal>
(1) An empty launch object will be created by a launch configuration when
its launch method is called (since there is only one shared implementation
of ILaunchConfiguration, all clients inherit this behavoir for free). The
launch is empty in the sense that it does not contain any debug targets or
system processes at this point.
(2) The launch object will be seeded to point to the associated launch
configuration being launched
(3) The launch object will be registered with the debug plug-in
(4) The launch object will be passed to the configuration's associated
delegate to perform the actual launch.
(5) The delegate will launch/create processes and debug targets and ADD
them to the provided (already existing) launch object

If the launch fails after step 3, what is the expected error reporting
process? Would the delegate de-register the launch or terminate it or just
set the target to null?

Thanks.

Kristen Desarmo
IBM Distributed Debugger