Home » Eclipse Projects » Remote Application Platform (RAP) » Problems using Target Platform
| |
| Re: Problems using Target Platform [message #91701 is a reply to message #91539] |
Wed, 04 June 2008 08:46   |
Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
do you have the RCP and the RAP bundles in the same workspace? I
encountered such problems also by switching the targets in earlier
versions, but this was a tooling problem and had nothing to do with RAP.
Using different workspaces solved the problem for me.
The method FormToolkit.paintBordersFor(...) is not supported in the RAP
version of forms.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: David [mailto:david.seidel@prodyna.de]
Bereitgestellt: Dienstag, 3. Juni 2008 17:19
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Problems using Target Platform
Betreff: Problems using Target Platform
Hi,
I'm delevoping a RCP/RAP Application with same code base (using
different target platforms).
After switching from RAP 1.1 M3 Target Platform to 1.1 RC1, i got a
strange error, when I try to import e.g. "import
org.eclipse.ui.IWorkbenchWindow;":
"Access restriction: The type IWorkbenchWindow is not accessible due to
restriction on required library C:
\development\eclipse_3.4\configuration\rap-1.1.0-RC3-target- 3.4-20080603
-1107\eclipse\plugins
\org.eclipse.rap.ui.workbench_1.1.0.20080603-1107.jar"
If I add the org.eclipse.rap.ui.workbench as required bundle, everything
works fine. But in order to be target platform independent, this is not
my
preferred solution. :-)
Another problem occurs, when i try to use
FormToolkit.paintBordersFor(...):
"The method paintBordersFor(BasicForm) is undefined for the type
FormToolkit"
So what's wrong here?
Regards,
David
|
|
|
| Re: Problems using Target Platform [message #91770 is a reply to message #91701] |
Wed, 04 June 2008 10:48 |
 David Seidel
Messages: 4
Registered: July 2009 |
Junior Member |
|
|
Hi,
I've removed the rcp-dependent bundles from my workspace and also all
calls to FormToolkit.paintBordersFor(...), but doesn't solve the problem.
Maybe some code helps:
MANIFEST.MF
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: myplugin
Bundle-SymbolicName: myplugin;singleton:=true
Bundle-Version: 1.0.0
Bundle-ClassPath: .
Bundle-Activator: myplugin.Activator
Require-Bundle: myplugin.client,
org.eclipse.osgi
Import-Package: org.eclipse.core.commands.common,
org.eclipse.core.databinding,
org.eclipse.core.databinding.beans,
org.eclipse.core.databinding.observable,
org.eclipse.core.databinding.observable.list,
org.eclipse.core.databinding.observable.map,
org.eclipse.core.databinding.observable.set,
org.eclipse.core.databinding.observable.value,
org.eclipse.core.runtime,
org.eclipse.jface.action,
org.eclipse.jface.databinding.swt,
org.eclipse.jface.dialogs,
org.eclipse.jface.resource,
org.eclipse.jface.viewers,
org.eclipse.swt,
org.eclipse.swt.events,
org.eclipse.swt.graphics,
org.eclipse.swt.layout,
org.eclipse.swt.widgets,
org.eclipse.ui,
org.eclipse.ui.forms,
org.eclipse.ui.forms.editor,
org.eclipse.ui.forms.events,
org.eclipse.ui.forms.widgets,
org.eclipse.ui.part
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
sample for imports, which cannot be resolved:
import org.eclipse.ui.IEditorInput;
import org.eclipse.ui.IEditorSite;
import org.eclipse.ui.ISaveablePart;
import org.eclipse.ui.PartInitException;
import org.eclipse.ui.part.EditorPart;
Current target platform:
rap-1.1.0-RC3-target-3.4-20080603-1107
It seems, that org.eclipse.ui cannot be resolved correctly.
Regards,
David
|
|
|
| Re: Problems using Target Platform [message #91914 is a reply to message #91770] |
Thu, 05 June 2008 05:26 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
I've created a project for testing purpose in my workspace using the
import packages of your example manifest. After doing so I've tried to
add an EditorPart using the new wizard, but EditorPart wasn't available.
So it seems that I can reproduce the problem. But currently I don't have
a clue what's happening here - whether this is a problem of the tooling
or some differences in the structure between RCP and RAP. Maybe at least
the concept of using Package Import and Export to declare dependencies
isn't that good as praised in the OSGi spec...
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: David [mailto:david.seidel@prodyna.de]
Bereitgestellt: Mittwoch, 4. Juni 2008 12:48
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Problems using Target Platform
Betreff: Re: Problems using Target Platform
Hi,
I've removed the rcp-dependent bundles from my workspace and also all
calls to FormToolkit.paintBordersFor(...), but doesn't solve the
problem.
Maybe some code helps:
MANIFEST.MF
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: myplugin
Bundle-SymbolicName: myplugin;singleton:=true
Bundle-Version: 1.0.0
Bundle-ClassPath: .
Bundle-Activator: myplugin.Activator
Require-Bundle: myplugin.client,
org.eclipse.osgi
Import-Package: org.eclipse.core.commands.common,
org.eclipse.core.databinding, org.eclipse.core.databinding.beans,
org.eclipse.core.databinding.observable,
org.eclipse.core.databinding.observable.list,
org.eclipse.core.databinding.observable.map,
org.eclipse.core.databinding.observable.set,
org.eclipse.core.databinding.observable.value,
org.eclipse.core.runtime,
org.eclipse.jface.action,
org.eclipse.jface.databinding.swt,
org.eclipse.jface.dialogs,
org.eclipse.jface.resource,
org.eclipse.jface.viewers,
org.eclipse.swt,
org.eclipse.swt.events,
org.eclipse.swt.graphics,
org.eclipse.swt.layout,
org.eclipse.swt.widgets,
org.eclipse.ui,
org.eclipse.ui.forms,
org.eclipse.ui.forms.editor,
org.eclipse.ui.forms.events,
org.eclipse.ui.forms.widgets,
org.eclipse.ui.part
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
sample for imports, which cannot be resolved:
import org.eclipse.ui.IEditorInput;
import org.eclipse.ui.IEditorSite;
import org.eclipse.ui.ISaveablePart;
import org.eclipse.ui.PartInitException; import
org.eclipse.ui.part.EditorPart;
Current target platform:
rap-1.1.0-RC3-target-3.4-20080603-1107
It seems, that org.eclipse.ui cannot be resolved correctly.
Regards,
David
|
|
|
| Re: Problems using Target Platform [message #92090 is a reply to message #91914] |
Fri, 06 June 2008 08:41 |
David Seidel
Messages: 4
Registered: July 2009 |
Junior Member |
|
|
Hi,
I have added a bug report for this issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=235834
Regards,
David
Frank Appel wrote:
> Hi,
> I've created a project for testing purpose in my workspace using the
> import packages of your example manifest. After doing so I've tried to
> add an EditorPart using the new wizard, but EditorPart wasn't available.
> So it seems that I can reproduce the problem. But currently I don't have
> a clue what's happening here - whether this is a problem of the tooling
> or some differences in the structure between RCP and RAP. Maybe at least
> the concept of using Package Import and Export to declare dependencies
> isn't that good as praised in the OSGi spec...
> Ciao
> Frank
> -----Ursprüngliche Nachricht-----
> Von: David [mailto:david.seidel@prodyna.de]
> Bereitgestellt: Mittwoch, 4. Juni 2008 12:48
> Bereitgestellt in: eclipse.technology.rap
> Unterhaltung: Problems using Target Platform
> Betreff: Re: Problems using Target Platform
> Hi,
> I've removed the rcp-dependent bundles from my workspace and also all
> calls to FormToolkit.paintBordersFor(...), but doesn't solve the
> problem.
> Maybe some code helps:
> MANIFEST.MF
> Manifest-Version: 1.0
> Bundle-ManifestVersion: 2
> Bundle-Name: myplugin
> Bundle-SymbolicName: myplugin;singleton:=true
> Bundle-Version: 1.0.0
> Bundle-ClassPath: .
> Bundle-Activator: myplugin.Activator
> Require-Bundle: myplugin.client,
> org.eclipse.osgi
> Import-Package: org.eclipse.core.commands.common,
> org.eclipse.core.databinding, org.eclipse.core.databinding.beans,
> org.eclipse.core.databinding.observable,
> org.eclipse.core.databinding.observable.list,
> org.eclipse.core.databinding.observable.map,
> org.eclipse.core.databinding.observable.set,
> org.eclipse.core.databinding.observable.value,
> org.eclipse.core.runtime,
> org.eclipse.jface.action,
> org.eclipse.jface.databinding.swt,
> org.eclipse.jface.dialogs,
> org.eclipse.jface.resource,
> org.eclipse.jface.viewers,
> org.eclipse.swt,
> org.eclipse.swt.events,
> org.eclipse.swt.graphics,
> org.eclipse.swt.layout,
> org.eclipse.swt.widgets,
> org.eclipse.ui,
> org.eclipse.ui.forms,
> org.eclipse.ui.forms.editor,
> org.eclipse.ui.forms.events,
> org.eclipse.ui.forms.widgets,
> org.eclipse.ui.part
> Bundle-RequiredExecutionEnvironment: JavaSE-1.6
> sample for imports, which cannot be resolved:
> import org.eclipse.ui.IEditorInput;
> import org.eclipse.ui.IEditorSite;
> import org.eclipse.ui.ISaveablePart;
> import org.eclipse.ui.PartInitException; import
> org.eclipse.ui.part.EditorPart;
> Current target platform:
> rap-1.1.0-RC3-target-3.4-20080603-1107
> It seems, that org.eclipse.ui cannot be resolved correctly.
> Regards,
> David
|
|
|
Goto Forum:
Current Time: Tue Apr 23 06:32:21 GMT 2024
Powered by FUDForum. Page generated in 0.03106 seconds |
] 
Search
Help
Register
Login
Home
