Jump to: navigation, search

Difference between revisions of "FAQ When do I use a launch delegate?"

 
m
 
Line 1: Line 1:
A launch configuration captures all  the information required to launch
+
A launch configuration captures all  the information required to launch a particular application, but the  launching is performed by a launch delegate. This separation allows a single launch configuration to be used by several launch delegates to launch an application in different ways using the same launch information. For example, there is a single launch-configuration type for launching Java programs but different launch delegates for launching in run mode versus debug mode. One could define more delegates for launching Java programs by associating with the existing Java launch-configuration type.  This example shows a declaration of a launch delegate for launching Java applications in a special profiling mode:
a particular application, but the  launching is performed by a launch
+
delegate. This separation allows a single launch configuration to be
+
used by several launch delegates to launch an application in different ways
+
using the same launch information. For example, there is a single launch-configuration  
+
type for launching Java programs but different launch delegates
+
for launching in run mode versus debug mode. One could define more delegates
+
for launching Java programs by associating with the existing Java launch-configuration
+
type.  This example shows a declaration of a launch delegate for launching Java
+
applications in a special profiling mode:
+
 
<pre>
 
<pre>
 
   &lt;extension point=&quot;org.eclipse.debug.core.launchDelegates&quot;&gt;
 
   &lt;extension point=&quot;org.eclipse.debug.core.launchDelegates&quot;&gt;
Line 19: Line 10:
 
</pre>
 
</pre>
  
 +
For more information on launch delegates, see the documentation for the <tt>org.eclipse.debug.core.launchDelegates</tt> extension point and the javadoc for <tt>ILaunchConfigurationDelegate</tt> in the debug core plug-in.
  
For more information on launch delegates, see the documentation
+
{{Template:FAQ_Tagline}}
for the <tt>org.eclipse.debug.core.launchDelegates</tt> extension point
+
and the javadoc for <tt>ILaunchConfigurationDelegate</tt> in the debug
+
core plug-in.
+
 
+
<hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font>
+

Latest revision as of 01:17, 16 June 2006

A launch configuration captures all the information required to launch a particular application, but the launching is performed by a launch delegate. This separation allows a single launch configuration to be used by several launch delegates to launch an application in different ways using the same launch information. For example, there is a single launch-configuration type for launching Java programs but different launch delegates for launching in run mode versus debug mode. One could define more delegates for launching Java programs by associating with the existing Java launch-configuration type. This example shows a declaration of a launch delegate for launching Java applications in a special profiling mode:

   <extension point="org.eclipse.debug.core.launchDelegates">
      <launchDelegate
         id="org.eclipse.faq.example.traceDelegate"
         delegate="org.eclipse.faq.example.TraceLauncher"
         type="org.eclipse.jdt.launching.localJavaApplication"
         modes="trace"/>
   </extension>

For more information on launch delegates, see the documentation for the org.eclipse.debug.core.launchDelegates extension point and the javadoc for ILaunchConfigurationDelegate in the debug core plug-in.


This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.