Community
Participate
Working Groups
The current CVS version causes a RAP application to crash upon startup. It can be reproduced with the RAP workbench/controls demo. The error in the browser: Error: TypeError: this._frameBorder.setColor is not a function When setting the client side library to debug there is a ResourceRegistrationException, here is the stacktrace: org.eclipse.rwt.internal.resources.ResourceRegistrationException: Failed to register resource 'org/eclipse/rwt/Border.js'. at org.eclipse.rwt.internal.resources.ResourceManagerImpl.doRegister(ResourceManagerImpl.java:438) at org.eclipse.rwt.internal.resources.ResourceManagerImpl.register(ResourceManagerImpl.java:236) at org.eclipse.swt.internal.widgets.displaykit.QooxdooResourcesUtil.register(QooxdooResourcesUtil.java:355) at org.eclipse.swt.internal.widgets.displaykit.QooxdooResourcesUtil.registerJavascriptFiles(QooxdooResourcesUtil.java:302) at org.eclipse.swt.internal.widgets.displaykit.QooxdooResourcesUtil.registerResources(QooxdooResourcesUtil.java:290) at org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.registerResources(DisplayLCA.java:221) at org.eclipse.swt.internal.widgets.displaykit.DisplayLCAFacadeImpl.registerResourcesInternal(DisplayLCAFacadeImpl.java:29) at org.eclipse.swt.internal.widgets.displaykit.DisplayLCAFacade.registerResources(DisplayLCAFacade.java:32) at org.eclipse.rwt.internal.service.StartupPageConfigurer.getTemplate(StartupPageConfigurer.java:65) at org.eclipse.rwt.internal.service.StartupPage.render(StartupPage.java:68) at org.eclipse.rwt.internal.service.StartupPage.send(StartupPage.java:49) at org.eclipse.rwt.internal.service.LifeCycleServiceHandler.runLifeCycle(LifeCycleServiceHandler.java:82) at org.eclipse.rwt.internal.service.LifeCycleServiceHandler.synchronizedService(LifeCycleServiceHandler.java:54) at org.eclipse.rwt.internal.service.LifeCycleServiceHandler.service(LifeCycleServiceHandler.java:42) at org.eclipse.rwt.internal.service.ServiceManager$HandlerDispatcher.service(ServiceManager.java:35) at org.eclipse.rwt.internal.engine.RWTDelegate.doPost(RWTDelegate.java:46) at org.eclipse.rwt.internal.engine.RWTDelegate.doGet(RWTDelegate.java:35) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:318) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) 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:924) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) 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)
Just saw that the bug has already been filed a few minutes ago :) *** This bug has been marked as a duplicate of bug 342639 ***