Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRalf Sternberg2012-11-16 15:41:18 +0000
committerRalf Sternberg2012-11-16 15:42:24 +0000
commit2bb348f0dee51155104d68535ac533d302df418f (patch)
treec13149c43084a8c629b6cd0d1c660abd3e0d81a1 /bundles/org.eclipse.rap.ui
parentb911d3b1497ac2556df0db360c1b221d90e2902d (diff)
downloadorg.eclipse.rap-2bb348f0dee51155104d68535ac533d302df418f.tar.gz
org.eclipse.rap-2bb348f0dee51155104d68535ac533d302df418f.tar.xz
org.eclipse.rap-2bb348f0dee51155104d68535ac533d302df418f.zip
Adjust extension points to changed namespace
See bug 394456: Classes in extension points must be adjusted to namespace change https://bugs.eclipse.org/bugs/show_bug.cgi?id=394456
Diffstat (limited to 'bundles/org.eclipse.rap.ui')
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/entrypoint.exsd4
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/phaselistener.exsd10
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/serviceHandler.exsd2
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/settingstores.exsd16
4 files changed, 16 insertions, 16 deletions
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/entrypoint.exsd b/bundles/org.eclipse.rap.ui/schema/rap/entrypoint.exsd
index fa1d002fb9..1194647f6b 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/entrypoint.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/entrypoint.exsd
@@ -63,7 +63,7 @@ As an alternative to registering an entrypoint, Eclipse applications can also us
<attribute name="id" type="string" use="required">
<annotation>
<documentation>
- The identifier of this entrypoint. Used in &lt;code&gt;org.eclipse.rap.ui.branding&lt;/code&gt; extension point.
+ The identifier of this entrypoint.
</documentation>
</annotation>
</attribute>
@@ -73,7 +73,7 @@ As an alternative to registering an entrypoint, Eclipse applications can also us
An implementation of &lt;code&gt;IEntryPoint&lt;/code&gt; which starts the application.
</documentation>
<appInfo>
- <meta.attribute kind="java" basedOn=":org.eclipse.rwt.lifecycle.IEntryPoint"/>
+ <meta.attribute kind="java" basedOn=":org.eclipse.rap.rwt.lifecycle.IEntryPoint"/>
</appInfo>
</annotation>
</attribute>
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/phaselistener.exsd b/bundles/org.eclipse.rap.ui/schema/rap/phaselistener.exsd
index 83c26c7a12..5af76ea822 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/phaselistener.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/phaselistener.exsd
@@ -6,7 +6,7 @@
<meta.schema plugin="org.eclipse.rap.ui" id="phaselistener" name="PhaseListener"/>
</appInfo>
<documentation>
- The extension point is used to register a &lt;code&gt;PhaseListener&lt;/code&gt; implementation. PhaseListeners are objects that are registered to be notified at the beginning and ending of each phase of the request processing lifecycle (see &lt;code&gt;ILifeCycle&lt;/code&gt;). Extensions should provide a class that implements &lt;code&gt;org.eclipse.rwt.lifecycle.PhaseListener&lt;/code&gt;.
+ The extension point is used to register a &lt;code&gt;PhaseListener&lt;/code&gt; implementation. PhaseListeners are objects that are registered to be notified at the beginning and ending of each phase of the request processing lifecycle (see &lt;code&gt;ILifeCycle&lt;/code&gt;). Extensions should provide a class that implements &lt;code&gt;org.eclipse.rap.rwt.lifecycle.PhaseListener&lt;/code&gt;.
</documentation>
</annotation>
@@ -55,7 +55,7 @@
</documentation>
<appInfo>
- <meta.attribute kind="java" basedOn="org.eclipse.rwt.lifecycle.PhaseListener"/>
+ <meta.attribute kind="java" basedOn="org.eclipse.rap.rwt.lifecycle.PhaseListener"/>
</appInfo>
</annotation>
</attribute>
@@ -93,11 +93,11 @@
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
- RWT divides the life cycle of an HTTP request into different phases that are executed sequentially. Each phase has its special purpose and creates the prerequisites needed by the following phases for proper execution. A PhaseListener has to implement the &lt;code&gt;org.eclipse.rwt.lifecycle.PhaseListener&lt;/code&gt; interface.
+ RWT divides the life cycle of an HTTP request into different phases that are executed sequentially. Each phase has its special purpose and creates the prerequisites needed by the following phases for proper execution. A PhaseListener has to implement the &lt;code&gt;org.eclipse.rap.rwt.lifecycle.PhaseListener&lt;/code&gt; interface.
&lt;pre&gt;
-import org.eclipse.rwt.RWT;
-import org.eclipse.rwt.lifecycle.*;
+import org.eclipse.rap.rwt.RWT;
+import org.eclipse.rap.rwt.lifecycle.*;
public class DemoPhaseListener implements PhaseListener {
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/serviceHandler.exsd b/bundles/org.eclipse.rap.ui/schema/rap/serviceHandler.exsd
index 604f746a5d..9c7d6f5497 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/serviceHandler.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/serviceHandler.exsd
@@ -64,7 +64,7 @@ To invoke the service handler a developer needs to construct a URL. The URL must
An implementation of &lt;code&gt;IServiceHandler&lt;/code&gt;
</documentation>
<appInfo>
- <meta.attribute kind="java" basedOn=":org.eclipse.rwt.service.IServiceHandler"/>
+ <meta.attribute kind="java" basedOn=":org.eclipse.rap.rwt.service.IServiceHandler"/>
</appInfo>
</annotation>
</attribute>
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/settingstores.exsd b/bundles/org.eclipse.rap.ui/schema/rap/settingstores.exsd
index 5476e47c2a..24c6d6a473 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/settingstores.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/settingstores.exsd
@@ -14,16 +14,16 @@ Developers that want to implement their own setting store must provide a setting
&lt;p&gt;
Note that at runtime only &lt;b&gt;one&lt;/b&gt; (out of all available) factories will be used to create new &lt;code&gt;ISettingStore&lt;/code&gt; instances. Which factory is used can be controlled in two ways:
&lt;ul&gt;
-&lt;li&gt;In a normal RAP deployment you can specify the factory to be used by placing the following property in the OSGi config.ini file: &lt;code&gt;org.eclipse.rwt.settingStoreFactory=&lt;i&gt;id&lt;/i&gt;&lt;/code&gt; where &lt;i&gt;id&lt;/i&gt; identifies a particular factory element. Example:
+&lt;li&gt;In a normal RAP deployment you can specify the factory to be used by placing the following property in the OSGi config.ini file: &lt;code&gt;org.eclipse.rap.rwt.settingStoreFactory=&lt;i&gt;id&lt;/i&gt;&lt;/code&gt; where &lt;i&gt;id&lt;/i&gt; identifies a particular factory element. Example:
&lt;pre&gt;
-org.eclipse.rwt.settingStoreFactory=file
+org.eclipse.rap.rwt.settingStoreFactory=file
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;In an RWT-only deployment you can specify the factory to be used by placing the following snippet in the web.xml file:&lt;br&gt;
&lt;pre&gt;
&amp;lt;init-param&amp;gt;
- &amp;lt;param-name&amp;gt;org.eclipse.rwt.settingStoreFactory&amp;lt;/param-name&amp;gt;
- &amp;lt;param-value&amp;gt;org.eclipse.rwt.service.RWTFileSettingStoreFactory&amp;lt;/param-value&amp;gt;
+ &amp;lt;param-name&amp;gt;org.eclipse.rap.rwt.settingStoreFactory&amp;lt;/param-name&amp;gt;
+ &amp;lt;param-value&amp;gt;org.eclipse.rap.rwt.service.RWTFileSettingStoreFactory&amp;lt;/param-value&amp;gt;
&amp;lt;/init-param&amp;gt;
&lt;/pre&gt;
&lt;li&gt;If nothing is specified, the class &lt;code&gt;WorkbenchFileSettingStoreFactory&lt;/code&gt; will be used in a regular RAP deployment. In an RWT only deployment the class &lt;code&gt;RWTFileSettingStoreFactory&lt;/code&gt; will be used instead.&lt;/li&gt;
@@ -88,10 +88,10 @@ org.eclipse.rwt.settingStoreFactory=file
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
- a fully qualified name of the class implementing the &lt;code&gt;org.eclipse.rwt.service.ISettingStoreFactory&lt;/code&gt; interface.
+ a fully qualified name of the class implementing the &lt;code&gt;org.eclipse.rap.rwt.service.ISettingStoreFactory&lt;/code&gt; interface.
</documentation>
<appInfo>
- <meta.attribute kind="java" basedOn=":org.eclipse.rwt.service.ISettingStoreFactory"/>
+ <meta.attribute kind="java" basedOn=":org.eclipse.rap.rwt.service.ISettingStoreFactory"/>
</appInfo>
</annotation>
</attribute>
@@ -120,7 +120,7 @@ org.eclipse.rwt.settingStoreFactory=file
id=&quot;file&quot;&gt;
&lt;/factory&gt;
&lt;factory
- class=&quot;org.eclipse.rwt.service.RWTFileSettingStoreFactory&quot;
+ class=&quot;org.eclipse.rap.rwt.service.RWTFileSettingStoreFactory&quot;
id=&quot;rwtfile&quot;&gt;
&lt;/factory&gt;
&lt;/extension&gt;
@@ -133,7 +133,7 @@ org.eclipse.rwt.settingStoreFactory=file
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
- To obtain a setting store use &lt;code&gt;RWT.getSettingStore()&lt;/code&gt;. This will use the configured &lt;code&gt;org.eclipse.rwt.service.ISettingStoreFactory&lt;/code&gt; to generate and return an appropriate &lt;code&gt;org.eclipse.rwt.service.ISettingStore&lt;/code&gt; instance for this session.
+ To obtain a setting store use &lt;code&gt;RWT.getSettingStore()&lt;/code&gt;. This will use the configured &lt;code&gt;org.eclipse.rap.rwt.service.ISettingStoreFactory&lt;/code&gt; to generate and return an appropriate &lt;code&gt;org.eclipse.rap.rwt.service.ISettingStore&lt;/code&gt; instance for this session.
&lt;p&gt;
Developers wishing to provide their own setting store must implement &lt;code&gt;ISettingStore&lt;/code&gt; and &lt;code&gt;ISettingStoreFactory&lt;/code&gt; and contribute their factory using this extension point.
</documentation>

Back to the top