Jump to: navigation, search

Difference between revisions of "FAQ What is an extension point schema?"

 
m
 
Line 1: Line 1:
''
+
Each extension point has a <i>schema</i> file that declares the elements and attributes that extensions to that point must declare.  The schema is used during plug-in development to detect invalid extensions in the <tt>plugin.xml</tt> files in your workspace and is used by the schema-based extension wizard in the plug-in Manifest Editor to help guide you through the steps to creating an extension. Perhaps most important, the schema is used to store and generate documentation for your extension point.  The schema is <i>not</i> used to perform any runtime validation checks on plug-ins that connect to that extension point. In fact, extension point schema files don&#146;t even need to exist in a deployed plug-in.
 
+
 
+
 
+
Each extension point has a <i>schema</i> file that declares the elements
+
and attributes that extensions to that point must declare.  The schema
+
is used during plug-in development to detect invalid extensions in the
+
<tt>plugin.xml</tt> files in your workspace and is used by the  
+
schema-based extension wizard in the plug-in Manifest Editor to help  
+
guide you through the steps to creating an extension. Perhaps most important,
+
the schema is used to store and generate documentation for your
+
extension point.  The schema is <i>not</i> used to perform any runtime
+
validation checks on plug-ins that connect to that extension point. In fact,
+
extension point schema files don&#146;t even need to exist in a deployed plug-in.
+
 
+
 
+
 
+
 
+
The exact format of the schema file is an implementation detail that you
+
probably don&#146;t want to become familiar with.  Instead, you should use
+
the graphical schema editor provided by the Plug-in Development Environment.
+
 
+
 
+
 
+
 
+
  
 +
The exact format of the schema file is an implementation detail that you probably don&#146;t want to become familiar with.  Instead, you should use the graphical schema editor provided by the Plug-in Development Environment.
  
 
== See Also: ==
 
== See Also: ==
 +
*[[FAQ How do I declare my own extension point?]]
 +
*[[FAQ Can my extension point schema contain nested elements?]]
 +
*[[FAQ What are extensions and extension points?]]
  
 
+
{{Template:FAQ_Tagline}}
[[FAQ_How_do_I_declare_my_own_extension_point%3F]]
+
 
+
 
+
[[FAQ_Can_my_extension_point_schema_contain_nested_elements%3F]]
+
 
+
 
+
[[FAQ_What_are_extensions_and_extension_points%3F]]
+
 
+
<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 19:07, 15 June 2006

Each extension point has a schema file that declares the elements and attributes that extensions to that point must declare. The schema is used during plug-in development to detect invalid extensions in the plugin.xml files in your workspace and is used by the schema-based extension wizard in the plug-in Manifest Editor to help guide you through the steps to creating an extension. Perhaps most important, the schema is used to store and generate documentation for your extension point. The schema is not used to perform any runtime validation checks on plug-ins that connect to that extension point. In fact, extension point schema files don’t even need to exist in a deployed plug-in.

The exact format of the schema file is an implementation detail that you probably don’t want to become familiar with. Instead, you should use the graphical schema editor provided by the Plug-in Development Environment.

See Also:


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.