Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » [GWT] Could not initialize class org.eclipse.emf.server.ecore.resource.URIServiceImpl
[GWT] Could not initialize class org.eclipse.emf.server.ecore.resource.URIServiceImpl [message #872629] Wed, 16 May 2012 13:45 Go to next message
Alex Lenk is currently offline Alex Lenk
Messages: 4
Registered: May 2012
Junior Member
Hello,

I recently tried to run my EMF model as an Web application and used the GWT editor project generation for this. Unfortunately when starting the GWT Web Application the application loads but the console outputs the following stack trace:

Mai 16, 2012 3:05:19 PM com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: Error for /Project.ProjectEditor/uriService
java.lang.NoClassDefFoundError: Could not initialize class org.eclipse.emf.server.ecore.resource.URIServiceImpl
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at java.lang.Class.newInstance0(Class.java:372)
at java.lang.Class.newInstance(Class.java:325)
at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:153)
at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:428)
at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:339)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at com.google.appengine.tools.development.HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:35)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:60)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:122)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.BackendServersFilter.doFilter(BackendServersFilter.java:97)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at com.google.appengine.tools.development.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(JettyContainerService.java:369)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)



Has anyone an idea how I to fix this?

Thanks,
Alex
Re: [GWT] Could not initialize class org.eclipse.emf.server.ecore.resource.URIServiceImpl [message #872743 is a reply to message #872629] Wed, 16 May 2012 18:25 Go to previous messageGo to next message
Ed Merks is currently offline Ed Merks
Messages: 26130
Registered: July 2009
Senior Member
Alex,

That should be on the classpath. In particular, the builder EMF adds
should have automatically copied the org.eclipse.emf.ecore jar to the
war/WEB-INF/lib folder. It does that for me...


On 16/05/2012 3:46 PM, Alex Lenk wrote:
> Hello,
>
> I recently tried to run my EMF model as an Web application and used
> the GWT editor project generation for this. Unfortunately when
> starting the GWT Web Application the application loads but the console
> outputs the following stack trace:
>
> Mai 16, 2012 3:05:19 PM com.google.apphosting.utils.jetty.JettyLogger
> warn
> WARNING: Error for /Project.ProjectEditor/uriService
> java.lang.NoClassDefFoundError: Could not initialize class
> org.eclipse.emf.server.ecore.resource.URIServiceImpl
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
> at java.lang.Class.newInstance0(Class.java:372)
> at java.lang.Class.newInstance(Class.java:325)
> at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:153)
> at
> org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:428)
> at
> org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:339)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
> at
> com.google.appengine.tools.development.HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:35)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at
> com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:60)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at
> com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at
> com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:122)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at
> com.google.appengine.tools.development.BackendServersFilter.doFilter(BackendServersFilter.java:97)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
> at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
> at
> com.google.appengine.tools.development.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:78)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at
> com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(JettyContainerService.java:369)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
>
>
>
> Has anyone an idea how I to fix this?
>
> Thanks,
> Alex
Re: [GWT] Could not initialize class org.eclipse.emf.server.ecore.resource.URIServiceImpl [message #875245 is a reply to message #872743] Tue, 22 May 2012 11:59 Go to previous messageGo to next message
Alex Lenk is currently offline Alex Lenk
Messages: 4
Registered: May 2012
Junior Member
It doesn't work for me. The libs are in the lib folder but the error pops up anyway.
I try a new clean installation and see if the problem still exists. Thanks!
Re: [GWT] Could not initialize class org.eclipse.emf.server.ecore.resource.URIServiceImpl [message #1357082 is a reply to message #875245] Thu, 15 May 2014 11:00 Go to previous message
Adrian Rutle is currently offline Adrian Rutle
Messages: 20
Registered: July 2009
Junior Member
Hi Alex

Did starting from scratch help in your case?

I have had the same problem for while and tried clean installation also, without any luck!

Actually I am not sure if this is related to the second warning I get
WARN::Nested in java.lang.ExceptionInInitializerError:
java.lang.SecurityException: class "org.eclipse.emf.ecore.impl.EFactoryImpl"'s signer information does not match signer information of other classes in the same package

I have seen another Forum topic on the "signer" problem. However I did not understand completely how to solve that problem either.

The problem arises when I try "save" from the created website.

Any info is appreciated.

Kind regards
Previous Topic:Is there a way to use a string as raw XML?
Next Topic:GUI Helper of org.eclipse.emf.ecore.presentation
Goto Forum:
  


Current Time: Wed Oct 22 05:09:46 GMT 2014

Powered by FUDForum. Page generated in 0.01770 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software