eclipse-ptp-rdt 8.0.0-1 / usr / share / eclipse / dropins / ptp-rdt / eclipse / plugins / org.eclipse.ptp.remote.server.core_2.0.0.dist / schema / remoteServer.exsd

This file is indexed.

/usr/share/eclipse/dropins/ptp-rdt/eclipse/plugins/org.eclipse.ptp.remote.server.core_2.0.0.dist/schema/remoteServer.exsd is in eclipse-ptp-rdt 8.0.0-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.ptp.remote.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
      <appInfo>
         <meta.schema plugin="org.eclipse.ptp.remote.core" id="remoteServer" name="Remote Server"/>
      </appInfo>
      <documentation>
         This extension point allows a plugin to register remote servers that will be launched from the client and run on a remote target system. In addition to the payload to run, the extension point specifies the launch command that will be used, and optional command to unpack the payload on the target systems, and a verification command to check that the environment on the target system is valid for execution of the server.

      </documentation>
   </annotation>

   <element name="extension">
      <annotation>
         <appInfo>
            <meta.element />
         </appInfo>
      </annotation>
      <complexType>
         <choice minOccurs="1" maxOccurs="unbounded">
            <element ref="remoteServer"/>
            <element ref="remoteServerOverride"/>
         </choice>
         <attribute name="point" type="string" use="required">
            <annotation>
               <documentation>
                  
               </documentation>
            </annotation>
         </attribute>
         <attribute name="id" type="string">
            <annotation>
               <documentation>
                  
               </documentation>
            </annotation>
         </attribute>
         <attribute name="name" type="string">
            <annotation>
               <documentation>
                  
               </documentation>
               <appInfo>
                  <meta.attribute translatable="true"/>
               </appInfo>
            </annotation>
         </attribute>
      </complexType>
   </element>

   <element name="remoteServer">
      <complexType>
         <attribute name="name" type="string" use="required">
            <annotation>
               <documentation>
                  A human readable name for this remote server.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="id" type="string" use="required">
            <annotation>
               <documentation>
                  A unique identifier for this remote server.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="continuous" type="boolean" use="required">
            <annotation>
               <documentation>
                  Flag indicating if the server will be running continously until terminated or runs once to completion. Continuously running servers require a &quot;success string&quot; to indicate that they have successfully started operating.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="class" type="string" use="required">
            <annotation>
               <documentation>
                  The fully qualified name of the Java class extending &lt;samp&gt;org.eclipse.ptp.remote.launch.core.AbstractRemoteServerRunner&lt;/samp&gt;.
               </documentation>
               <appInfo>
                  <meta.attribute kind="java" basedOn="org.eclipse.ptp.remote.launch.core.AbstractRemoteServerRunner:"/>
               </appInfo>
            </annotation>
         </attribute>
         <attribute name="payload" type="string" use="required">
            <annotation>
               <documentation>
                  Server payload. This will be copied from the plugin to the working directory on the remote machine prior to launch. The payload is cached on the remote machine and only copied if it is necessary.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="launchCommand" type="string" use="required">
            <annotation>
               <documentation>
                  The command used to launch the payload on the remote machine. The variable &quot;${payload}&quot; can be used to include the name of the payload (as specified in the &quot;payload&quot; attribute) in the launch command.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="unpackCommand" type="string">
            <annotation>
               <documentation>
                  Optional command to unpack the payload prior to execution. The unpack command is only run when the payload is first copied to the server (and if re-copied subsequently). If the unpack fails, payload launch is aborted.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyLaunchCommand" type="string">
            <annotation>
               <documentation>
                  This will be used to specify a command to check the desired launch command is available on remote server
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyLaunchFailMessage" type="string">
            <annotation>
               <documentation>
                  This attribute is used to specify a message which will be shown to the user if the launch command verification fails.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyLaunchPattern" type="string">
            <annotation>
               <documentation>
                  This will be used to specify the search pattern in the form of regular expression which will be used to verify the output of the command specified in the verifyLaunchCommand attribute.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyUnpackCommand" type="string">
            <annotation>
               <documentation>
                  This will be used to specify a command to check the unpack command is available on remote server
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyUnpackFailMessage" type="string">
            <annotation>
               <documentation>
                  This attribute is used to specify message which will be shown to the user if the unpack command verification fails.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyUnpackPattern" type="string">
            <annotation>
               <documentation>
                  This will be used to specify the search pattern in the form of regular expression which will be used to verify the output of the command specified in the verifyUnpackCommand attribute.
               </documentation>
            </annotation>
         </attribute>
      </complexType>
   </element>

   <element name="remoteServerOverride">
      <annotation>
         <documentation>
            Used to override the settings of an existing extension. For example, this could be used to change the launch command to specify a different path.
         </documentation>
      </annotation>
      <complexType>
         <attribute name="id" type="string" use="required">
            <annotation>
               <documentation>
                  The ID of the server that this extension overrides.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="payload" type="string">
            <annotation>
               <documentation>
                  Server payload. This will be copied from the plugin to the working directory on the remote machine prior to launch. The payload is cached on the remote machine and only copied if it is necessary.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="launchCommand" type="string">
            <annotation>
               <documentation>
                  The command used to launch the payload on the remote machine. The variable &quot;${payload}&quot; can be used to include the name of the payload (as specified in the &quot;payload&quot; attribute) in the launch command.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="unpackCommand" type="string">
            <annotation>
               <documentation>
                  Optional command to unpack the payload prior to execution. The unpack command is only run when the payload is first copied to the server (and if re-copied subsequently). If the unpack fails, payload launch is aborted.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyLaunchCommand" type="string">
            <annotation>
               <documentation>
                  This will be used to specify a command to check the desired launch command is available on remote server
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyLaunchFailMessage" type="string">
            <annotation>
               <documentation>
                  This attribute is used to specify a message which will be shown to the user if the launch command verification fails.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyLaunchPattern" type="string">
            <annotation>
               <documentation>
                  This will be used to specify the search pattern in the form of regular expression which will be used to verify the output of the command specified in the verifyLaunchCommand attribute.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyUnpackCommand" type="string">
            <annotation>
               <documentation>
                  This will be used to specify a command to check the unpack command is available on remote server
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyUnpackFailMessage" type="string">
            <annotation>
               <documentation>
                  This attribute is used to specify message which will be shown to the user if the unpack command verification fails.
               </documentation>
            </annotation>
         </attribute>
         <attribute name="verifyUnpackPattern" type="string">
            <annotation>
               <documentation>
                  This will be used to specify the search pattern in the form of regular expression which will be used to verify the output of the command specified in the verifyUnpackCommand attribute.
               </documentation>
            </annotation>
         </attribute>
      </complexType>
   </element>


   <annotation>
      <appInfo>
         <meta.section type="examples"/>
      </appInfo>
      <documentation>
         The following is an example of a remote server extension point: 
&lt;p&gt;
&lt;pre&gt;
   &lt;extension point=&quot;org.eclipse.ptp.remote.core.remoteServer&quot;&gt;
      &lt;remoteServer
           class=&quot;org.eclipse.ptp.rdt.server.dstore.core.DStoreServer&quot;
           continuous=&quot;true&quot;
           id=&quot;org.eclipse.ptp.rdt.server.dstore.RemoteToolsDStoreServer&quot;
           launchCommand=&quot;java -Xms64m -Xmx128m -Xss2m -jar ${payload} 0 60000&quot;
           name=&quot;%RemoteToolsDStoreServer.name&quot;
           payload=&quot;rdt-server.jar&quot;
           verifyLaunchCommand=&quot;java -version&quot;
           verifyLaunchFailMessage=&quot;{0}: Invalid java version or java not installed on &amp;quot;{1}&amp;quot;&quot;
           verifyLaunchPattern=&quot;^(java version )(.)(1\.[5-9]|[2-9]\.).*$&quot;&gt;
      &lt;/remoteServer&gt;
   &lt;/extension&gt;
&lt;/pre&gt;
&lt;/p&gt;

The following is an example of a remote server override extension point: 
&lt;p&gt;
&lt;pre&gt;
   &lt;extension point=&quot;org.eclipse.ptp.remote.core.remoteServerOverride&quot;&gt;
      &lt;remoteServer
           id=&quot;org.eclipse.ptp.rdt.server.dstore.RemoteToolsDStoreServer&quot;
           launchCommand=&quot;/other/path/java -Xms64m -Xmx128m -Xss2m -jar ${payload} 0 60000&quot;
      &lt;/remoteServer&gt;
   &lt;/extension&gt;
&lt;/pre&gt;
&lt;/p&gt;
      </documentation>
   </annotation>




</schema>

APT Browse - Built by Thomas Orozco.