Eclipse Community Forums: Remote Application Platform (RAP)

Help

Home

Home » Eclipse Projects » Remote Application Platform (RAP) » Extension point namespace change

Show: Today's Messages :: Show Polls :: Message Navigator

Extension point namespace change [message #23691]

Thu, 10 May 2007 10:35

Markus rüger

Messages: 369
Registered: July 2009

Senior Member

Hello,
after updating RAP from CVS and switching the namespaces of the extension to
the new one I get an error that my perspective was not found.

In the plugin.xml I have the following code:

<extension
point="org.eclipse.ui.perspectives">
<perspective
class="ag.ion.rap.internal.ui.perspectives.BasePerspective"
fixed="true"
icon="icons/full/eview16/base_perspective.gif"
id="ag.ion.rap.perspectives.base"
name="%perspective.base.name"/>
</extension>

The error stacktrace is:

java.lang.RuntimeException: org.eclipse.ui.WorkbenchException: Unable to
create perspective 'ag.ion.rap.perspectives.base'. There is no
corresponding perspective extension.
at org.eclipse.ui.internal.Workbench.openFirstTimeWindow(Workbe nch.java:87)
at
org.eclipse.ui.internal.WorkbenchConfigurer.openFirstTimeWin dow(WorkbenchConfigurer.java:18)
at
org.eclipse.ui.entrypoint.WorkbenchAdvisor.openWindows(Workb enchAdvisor.java:19)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:160)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:154)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:46)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:31)
at ag.ion.rap.internal.ui.RAPWorkbench.createUI(RAPWorkbench.ja va:58)
at
org.eclipse.swt.internal.lifecycle.EntryPointManager.createU I(EntryPointManager.java:82)
at
org.eclipse.swt.internal.lifecycle.PrepareUIRoot.execute(Pre pareUIRoot.java:32)
at
org.eclipse.swt.internal.lifecycle.RWTLifeCycle.execute(RWTL ifeCycle.java:60)
at com.w4t.engine.W4TModel$ServiceAdapter.execute(W4TModel.java :47)
at
com.w4t.engine.service.FormRequestServiceHandler.service(For mRequestServiceHandler.java:65)
at
com.w4t.engine.service.ServiceManager$HandlerDispatcher.serv ice(ServiceManager.java:90)
at com.w4t.engine.W4TDelegate.doPost(W4TDelegate.java:75)
at
org.eclipse.ui.internal.servlet.RequestHandler.service(Reque stHandler.java:41)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:177)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:60)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at
org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:277)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:428)
at
org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHan dler.java:677)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java: 820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.ja va:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:8 37)
at
org.mortbay.http.SocketListener.handleConnection(SocketListe ner.java:245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:3 57)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:5 34)
Caused by: org.eclipse.ui.WorkbenchException: Unable to create perspective
'ag.ion.rap.perspectives.base'. There is no corresponding perspective
extension.
at org.eclipse.ui.internal.WorkbenchPage.<init>(WorkbenchPage.java:322)
at
org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(Workben chWindow.java:118)
at org.eclipse.ui.internal.Workbench.openFirstTimeWindow(Workbe nch.java:83)
... 34 more

Could You tell me what I need to do to fix this?

Regards,

Markus

Report message to a moderator

Re: Extension point namespace change [message #23734 is a reply to message #23691]

Thu, 10 May 2007 13:08

Markus rüger

Messages: 369
Registered: July 2009

Senior Member

Hello,
I figured out, that if I exclude the plugins "org.eclipse.core.expressions"
and "org.eclipse.update.configurator" from my launch configuration and call
my perpsective that does not use the "org.eclipse.core.expressions", then it
works. I definitely need the "org.eclipse.core.expressions" plugin and I
have no clue why my perspective can not be loaded if I include this plugin
and
use its functionality. This error only occury since I updated from CVS today
and corrected the namespaces.

Any ideas?

Thank you,
Markus

"Markus Kr

Report message to a moderator

Re: Extension point namespace change [message #23778 is a reply to message #23734]

Thu, 10 May 2007 13:23

Eclipse User

Originally posted by: fappel.innoopract.com

Hi,

I just checked your problem and I don't think that the problem is
'org.eclipse.core.expressions'. I used the propertyTester extension without
problem. The trouble is caused by the 'org.eclipse.update.configurator'
since it resolves all your target plug-ins including 'org.eclipse.ui'. I
guess this causes the namespace conflict. If you need the configurator
plug-in then you should create a seperate target where no RCP-UI-plug-ins
are available.

Hope that helps!

Ciao
Frank

"Markus Kr

Report message to a moderator

Re: Extension point namespace change [message #23862 is a reply to message #23778]

Thu, 10 May 2007 15:59

Markus rüger

Messages: 369
Registered: July 2009

Senior Member

Wow, sometime having over 160 Plugins can lead to some confusion. I had a
"core" plugin that my RCP and RAP was using. This "core" plugin added a
projekt nature. Project natures are in the plugin
"org.eclipse.core.resources" and this plugin has a dependency to
"org.eclipse.core.runtime.compatibility". Now the
"org.eclipse.core.runtime.compatibility" plugin has a dependency to
"org.eclipse.update.configurator" plugin which after the namespace changes
has a problem with RAP.

So, You were right, Frank. After solving this dependency by changing the
structure in my projects everthing works again.

Thanks,
Markus

"Frank Appel" <fappel@innoopract.com> schrieb im Newsbeitrag
news:f1v6dd$3v6$1@build.eclipse.org...
> Hi,
>
> I just checked your problem and I don't think that the problem is
> 'org.eclipse.core.expressions'. I used the propertyTester extension
> without problem. The trouble is caused by the
> 'org.eclipse.update.configurator' since it resolves all your target
> plug-ins including 'org.eclipse.ui'. I guess this causes the namespace
> conflict. If you need the configurator plug-in then you should create a
> seperate target where no RCP-UI-plug-ins are available.
>
> Hope that helps!
>
> Ciao
> Frank
>
>
> "Markus Kr

Report message to a moderator

Previous Topic:	Registering Custom Service Handler
Next Topic:	Error deploy on tomcat (linux)

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 09:43:11 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter