Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Swordfish Capabilities"
(New page: This page is intended to document how to provide basic capability/activity definitions to allow for Swordfish Tooling UI contributions to be hidden. <source lang="xml"> <extension point=...) |
|||
| Line 1: | Line 1: | ||
| − | This page is intended to document how to provide basic capability/activity definitions to allow for Swordfish Tooling UI contributions to be hidden. | + | This page is intended to document how to provide basic capability/activity definitions to allow for Swordfish Tooling UI contributions to be hidden. Swordfish tooling is subsumed in the org.eclipse.swordfish.tooling.feature feature, all other swordfish features are only relevant for runtime and do not contain any UI contributions. |
| + | The following snippet binds all Swordfish tooling related UI contributions to the "org.eclipse.swordfish.tooling.ui" activity. | ||
<source lang="xml"> | <source lang="xml"> | ||
<extension point="org.eclipse.ui.activities"> | <extension point="org.eclipse.ui.activities"> | ||
| Line 16: | Line 17: | ||
pattern="org\.eclipse\.swordfish\.registry\.tooling/.*"/> | pattern="org\.eclipse\.swordfish\.registry\.tooling/.*"/> | ||
</extension> | </extension> | ||
| + | </source> | ||
| + | To allow the user to manually configure conventional activities you need to bind your activities to a category which is then shown in the Capabilities dialog. The following snippet defines an exemplary SOA category to which our Swordfish activity is bound. | ||
| + | <source lang="xml"> | ||
| + | <extension point="org.eclipse.ui.activities"> | ||
| + | <category | ||
| + | description="Capabilities related to SOA development." | ||
| + | id="org.eclipse.soa.Category" | ||
| + | name="SOA Development"/> | ||
| + | |||
| + | <categoryActivityBinding | ||
| + | activityId="org.eclipse.swordfish.tooling.ui" | ||
| + | categoryId="org.eclipse.soa.Category" /> | ||
| + | </extension> | ||
</source> | </source> | ||
| + | For the samples we used real names and descritions for illustartive pusposes. In your plugin.xml of course you should externalize them. | ||
| + | |||
| + | More detailed information how to define capabilities can be found in the [http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm Help] | ||
| + | |||
| + | [[Category:Swordfish]] | ||
Revision as of 02:27, 18 March 2010
This page is intended to document how to provide basic capability/activity definitions to allow for Swordfish Tooling UI contributions to be hidden. Swordfish tooling is subsumed in the org.eclipse.swordfish.tooling.feature feature, all other swordfish features are only relevant for runtime and do not contain any UI contributions.
The following snippet binds all Swordfish tooling related UI contributions to the "org.eclipse.swordfish.tooling.ui" activity.
<extension point="org.eclipse.ui.activities"> <activity description="Use Swordfish to develop Web Service consumers and providers." id="org.eclipse.swordfish.tooling.ui" name="Swordfish Development"> </activity> <activityPatternBinding activityId="org.eclipse.swordfish.tooling.ui" pattern="org\.eclipse\.swordfish\.tooling\.ui/.*"/> <activityPatternBinding activityId="org.eclipse.swordfish.tooling.ui" pattern="org\.eclipse\.swordfish\.registry\.tooling/.*"/> </extension>
To allow the user to manually configure conventional activities you need to bind your activities to a category which is then shown in the Capabilities dialog. The following snippet defines an exemplary SOA category to which our Swordfish activity is bound.
<extension point="org.eclipse.ui.activities"> <category description="Capabilities related to SOA development." id="org.eclipse.soa.Category" name="SOA Development"/> <categoryActivityBinding activityId="org.eclipse.swordfish.tooling.ui" categoryId="org.eclipse.soa.Category" /> </extension>
For the samples we used real names and descritions for illustartive pusposes. In your plugin.xml of course you should externalize them.
More detailed information how to define capabilities can be found in the Help