Re: upgrade gwt 2.7 to gwt 2.8.1 not working
On Friday, February 1, 2019 at 10:31:01 PM UTC+1, Thad Humphries wrote: > > Thanks! You answered this question over a year and a half ago, but I just > hit this very problem while converting an app from 2.7.0 to 2.8.2. (Why > now? With Oracle cutting off Java 8, we moved to Amazon Corretto, and found > some old imaging stuff that would not work with OpenJDK. As long as I was > correcting this and moving from Java 6 to OpenJDK 8--and with this weeks > Canary problems in mind--I decided to bump GWT as well.) > > Interesting what you say about Jetty in 2.7.0: I've never had a problem > with Servlet spec 2.5 and GWT 2.7.0 (this app has used 2.5 for years). > > From my testing with Tomcat 8.5, I can still use servlet 2.5 or 3.0 in the > web.xml header of the deployed app. Have you seen issues in deployment? I > ask because we've one customer who runs WebLogic and their current > version--12.1.3.0.0--only supports up to 3.0. > This was a classpath issue, not a webapp one. You never package the servlet APIs in your WARs, and even if you did, the server would use its own version and ignore yours. So as long as you don't use newer APIs that the target server doesn't support, you're safe. The problem is if you put an older API in the server's classpath (in the case of GWT, the devmode classpath), like if you shadowed/replaced WebLogic's own servlet API with another one. Fwiw, separating client and server code into separate "modules" (separate classpaths: only including client-side dependencies in the devmode classpath, leaving server-side dependencies to the webapp's WEB-INF/lib), something I've been advocating for years, generally solves these conflicts. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: upgrade gwt 2.7 to gwt 2.8.1 not working
Thanks! You answered this question over a year and a half ago, but I just
hit this very problem while converting an app from 2.7.0 to 2.8.2. (Why
now? With Oracle cutting off Java 8, we moved to Amazon Corretto, and found
some old imaging stuff that would not work with OpenJDK. As long as I was
correcting this and moving from Java 6 to OpenJDK 8--and with this weeks
Canary problems in mind--I decided to bump GWT as well.)
Interesting what you say about Jetty in 2.7.0: I've never had a problem
with Servlet spec 2.5 and GWT 2.7.0 (this app has used 2.5 for years).
>From my testing with Tomcat 8.5, I can still use servlet 2.5 or 3.0 in the
web.xml header of the deployed app. Have you seen issues in deployment? I
ask because we've one customer who runs WebLogic and their current
version--12.1.3.0.0--only supports up to 3.0.
On Wednesday, May 10, 2017 at 5:35:50 AM UTC-4, Thomas Broyer wrote:
>
>
>
> On Wednesday, May 10, 2017 at 6:57:25 AM UTC+2, Gal Lavie wrote:
>>
>> Hi everyone
>> I develop application in gwt and google app engine.
>> until now i used with gwt 2.7 lib and google app engine 1.51 lib
>> i try to upgrade the gwt 2.7 to 2.8.1 lib
>> and i have 2 problems now
>> i hope you can help me
>> 1) when i try to run the project i get exception in devModeBase.class
>> file in run method
>> this is the log of run + exception:
>>
>> Running CodeServer with parameters: [-noprecompile, -port, 65462,
>> -sourceLevel, 1.8, -bindAddress, 127.0.0.1, -launcherDir,
>> /Users/gallavie/Documents/workspace/Darimpo/war, -logLevel, INFO, -style,
>> OBFUSCATED, com.darimpo.Darimpo, com.darimpo.Darimpo]
>>
>> Super Dev Mode starting up
>>
>>workDir:
>> /var/folders/fj/8gtg078929j8hjtfzyy5srv4gn/T/gwt-codeserver-8030568012575356208.tmp
>>
>> 2017-05-10 06:44:10.582:INFO::main: Logging initialized @3822ms
>>
>>Loading Java files in com.darimpo.Darimpo.
>>
>>Ignored 33 units with compilation errors in first pass.
>>
>> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
>> errors.
>>
>>Module setup completed in 4961 ms
>>
>>Loading Java files in com.darimpo.Darimpo.
>>
>>Ignored 33 units with compilation errors in first pass.
>>
>> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
>> errors.
>>
>>Module setup completed in 1273 ms
>>
>> 2017-05-10 06:44:15.046:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
>>
>> 2017-05-10 06:44:15.164:INFO:oejsh.ContextHandler:main: Started
>> o.e.j.s.ServletContextHandler@7a508fdc{/,null,AVAILABLE}
>>
>> 2017-05-10 06:44:15.301:INFO:oejs.ServerConnector:main: Started
>> ServerConnector@4ca4b342{HTTP/1.1}{127.0.0.1:65462}
>>
>> 2017-05-10 06:44:15.313:INFO:oejs.Server:main: Started @8553ms
>>
>>
>> The code server is ready at http://127.0.0.1:65462/
>>
>> Code server started in 6.828 s ms
>>
>> 2017-05-10 06:44:15.702:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
>>
>> 2017-05-10 06:44:19.948:WARN:oejuc.AbstractLifeCycle:main: FAILED
>> org.eclipse.jetty.annotations.ServletContainerInitializersStarter@1e23623:
>> java.lang.NoSuchMethodError:
>> javax.servlet.ServletContext.getJspConfigDescriptor()Ljavax/servlet/descriptor/JspConfigDescriptor;
>>
>> java.lang.NoSuchMethodError:
>> javax.servlet.ServletContext.getJspConfigDescriptor()Ljavax/servlet/descriptor/JspConfigDescriptor;
>>
>
> Check your classpath, you probably have Servlets API in version 2.x (2.4,
> 2.5). This method was added in Servlets 3.0 (
> https://docs.oracle.com/javaee/7/api/javax/servlet/ServletContext.html#getJspConfigDescriptor--),
>
> and Jetty 9.2.14.v20151106 (the version that GWT uses) actually needs
> Servlets 3.1.0 (
> https://search.maven.org/#artifactdetails%7Corg.eclipse.jetty%7Cjetty-project%7C9.2.14.v20151106%7Cjar
> )
> (GWT 2.7.0 was using Jetty 8.1.12.v20130726, which BTW already needed
> Servlets 3.0
> https://search.maven.org/#artifactdetails%7Corg.eclipse.jetty%7Cjetty-project%7C8.1.12.v20130726%7Cjar,
>
> but could have maybe worked OK with Servlets 2.5 – I doubt it, maybe you
> changed the order of JARs in your classpath when upgrading; GWT 2.7 used to
> bundle the Servlets API into gwt-dev, and this has changed in 2.8.1, when
> retrieved from the Central Repository)
>
> 2) when i try to compile the project i get this exception
>>
>>
>>
>>[ERROR] An internal compiler exception occurred
>>
>> com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during
>> visit.
>>
>> at
>> com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:111)
>>
>> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:276)
>>
>> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
>>
>> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
>>
>> at
>> com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:76)
>>
>> at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
>>
>> at
Re: upgrade gwt 2.7 to gwt 2.8.1 not working
Hi thank you for replay but i dont understand what i need to do so i live this for now and continue so i continue and i get another exception when i call to database org.datanucleus.exceptions.NucleusException: Plugin (Bundle) "org.datanucleus" is already registered. Ensure you dont have multiple JAR versions of the same plugin in the classpath. The URL "file:/Users/gallavie/Documents/workspace/Darimpo/war/WEB-INF/lib/datanucleus-core-3.1.3.jar" is already registered, and you are trying to register an identical plugin located at URL "file:/Users/gallavie/Documents/workspace/libs/appengine-java-sdk-1.9.51/lib/opt/user/datanucleus/v2/datanucleus-core-3.1.3.jar." at org.datanucleus.plugin.NonManagedPluginRegistry.registerBundle( NonManagedPluginRegistry.java:541) at org.datanucleus.plugin.NonManagedPluginRegistry.registerBundle( NonManagedPluginRegistry.java:395) at org.datanucleus.plugin.NonManagedPluginRegistry.registerExtensions( NonManagedPluginRegistry.java:219) at org.datanucleus.plugin.NonManagedPluginRegistry.registerExtensionPoints( NonManagedPluginRegistry.java:160) at org.datanucleus.plugin.PluginManager.(PluginManager.java:65) at org.datanucleus.plugin.PluginManager.createPluginManager( PluginManager.java:427) at org.datanucleus.NucleusContext.(NucleusContext.java:224) at org.datanucleus.NucleusContext.(NucleusContext.java:204) at org.datanucleus.NucleusContext.(NucleusContext.java:182) at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.( JDOPersistenceManagerFactory.java:409) at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.createPersistenceManagerFactory( JDOPersistenceManagerFactory.java:294) at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.getPersistenceManagerFactory( JDOPersistenceManagerFactory.java:195) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at javax.jdo.JDOHelper$16.run(JDOHelper.java:1965) at java.security.AccessController.doPrivileged(Native Method) at javax.jdo.JDOHelper.invoke(JDOHelper.java:1960) at javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation( JDOHelper.java:1166) at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:844) at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:1099) at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:919) at com.darimpo.server.persist.PMF.(PMF.java:9) at com.darimpo.server.managers.BuildingsManager.getBuildingPlaces( BuildingsManager.java:654) at com.darimpo.server.servlets.GreetingServiceImpl.pullBuildingPlaces( GreetingServiceImpl.java:378) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:587) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall( RemoteServiceServlet.java:333) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall( RemoteServiceServlet.java:303) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost( RemoteServiceServlet.java:373) at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost( AbstractRemoteServiceServlet.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:648) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587 ) at org.eclipse.jetty.server.handler.ScopedHandler.handle( ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle( SecurityHandler.java:577) at org.eclipse.jetty.server.session.SessionHandler.doHandle( SessionHandler.java:223) at org.eclipse.jetty.server.handler.ContextHandler.doHandle( ContextHandler.java:1127) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) at org.eclipse.jetty.server.session.SessionHandler.doScope( SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope( ContextHandler.java:1061) at org.eclipse.jetty.server.handler.ScopedHandler.handle( ScopedHandler.java:141) at org.eclipse.jetty.server.handler.HandlerWrapper.handle( HandlerWrapper.java:97) at org.eclipse.jetty.server.handler.RequestLogHandler.handle( RequestLogHandler.java:95) at org.eclipse.jetty.server.handler.HandlerWrapper.handle( HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:499) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311) at org.eclipse.jetty.server.HttpConnection.onFillable(
Re: upgrade gwt 2.7 to gwt 2.8.1 not working
Hi thank you for replay but i dont understand what i need to do so i live this for now and continue so i continue and i get another exception when i call to database org.datanucleus.exceptions.NucleusException: Plugin (Bundle) "org.datanucleus" is already registered. Ensure you dont have multiple JAR versions of the same plugin in the classpath. The URL "file:/Users/gallavie/Documents/workspace/Darimpo/war/WEB-INF/lib/datanucleus-core-3.1.3.jar" is already registered, and you are trying to register an identical plugin located at URL "file:/Users/gallavie/Documents/workspace/libs/appengine-java-sdk-1.9.51/lib/opt/user/datanucleus/v2/datanucleus-core-3.1.3.jar." at org.datanucleus.plugin.NonManagedPluginRegistry.registerBundle( NonManagedPluginRegistry.java:541) at org.datanucleus.plugin.NonManagedPluginRegistry.registerBundle( NonManagedPluginRegistry.java:395) at org.datanucleus.plugin.NonManagedPluginRegistry.registerExtensions( NonManagedPluginRegistry.java:219) at org.datanucleus.plugin.NonManagedPluginRegistry.registerExtensionPoints( NonManagedPluginRegistry.java:160) at org.datanucleus.plugin.PluginManager.(PluginManager.java:65) at org.datanucleus.plugin.PluginManager.createPluginManager( PluginManager.java:427) at org.datanucleus.NucleusContext.(NucleusContext.java:224) at org.datanucleus.NucleusContext.(NucleusContext.java:204) at org.datanucleus.NucleusContext.(NucleusContext.java:182) at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.( JDOPersistenceManagerFactory.java:409) at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.createPersistenceManagerFactory( JDOPersistenceManagerFactory.java:294) at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.getPersistenceManagerFactory( JDOPersistenceManagerFactory.java:195) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at javax.jdo.JDOHelper$16.run(JDOHelper.java:1965) at java.security.AccessController.doPrivileged(Native Method) at javax.jdo.JDOHelper.invoke(JDOHelper.java:1960) at javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation( JDOHelper.java:1166) at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:844) at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:1099) at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:919) at com.darimpo.server.persist.PMF.(PMF.java:9) at com.darimpo.server.managers.BuildingsManager.getBuildingPlaces( BuildingsManager.java:654) at com.darimpo.server.servlets.GreetingServiceImpl.pullBuildingPlaces( GreetingServiceImpl.java:378) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:587) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall( RemoteServiceServlet.java:333) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall( RemoteServiceServlet.java:303) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost( RemoteServiceServlet.java:373) at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost( AbstractRemoteServiceServlet.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:648) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587 ) at org.eclipse.jetty.server.handler.ScopedHandler.handle( ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle( SecurityHandler.java:577) at org.eclipse.jetty.server.session.SessionHandler.doHandle( SessionHandler.java:223) at org.eclipse.jetty.server.handler.ContextHandler.doHandle( ContextHandler.java:1127) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) at org.eclipse.jetty.server.session.SessionHandler.doScope( SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope( ContextHandler.java:1061) at org.eclipse.jetty.server.handler.ScopedHandler.handle( ScopedHandler.java:141) at org.eclipse.jetty.server.handler.HandlerWrapper.handle( HandlerWrapper.java:97) at org.eclipse.jetty.server.handler.RequestLogHandler.handle( RequestLogHandler.java:95) at org.eclipse.jetty.server.handler.HandlerWrapper.handle( HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:499) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311) at org.eclipse.jetty.server.HttpConnection.onFillable(
Re: upgrade gwt 2.7 to gwt 2.8.1 not working
On Wednesday, May 10, 2017 at 9:02:44 PM UTC+2, Gal Lavie wrote: > > wwoo thank you > this worked for me > for the second problem i removed google map and this is worked for me (i > did this in past and it not worked but now it work i do not know why but > now it work) > for the first problem the solution is the order of libs. i go to the > orders of libs and put the gwt before google app engine and it worked. > Oh, I had missed the part where you said you're using App Engine. Aren't you supposed to use the AppEngineLauncher with DevMode then? (AFAICT, it's no longer supported though, so you'll actually want to run the AppEngine server and then run DevMode in "no server" mode, or use CodeServer instead) See https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/AppEngine.html -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: upgrade gwt 2.7 to gwt 2.8.1 not working
I found why this problem happens
HTTP ERROR 403
Problem accessing /Darimpo.html. Reason:
!Secure
--
*Powered by Jetty://*
it happened because i used ssl in my web.xml like this
**
*
/*
CONFIDENTIAL
when i remove this code my
app worked but i need this code so what i can do?*
On Wednesday, 10 May 2017 22:02:44 UTC+3, Gal Lavie wrote:
>
> wwoo thank you
> this worked for me
> for the second problem i removed google map and this is worked for me (i
> did this in past and it not worked but now it work i do not know why but
> now it work)
> for the first problem the solution is the order of libs. i go to the
> orders of libs and put the gwt before google app engine and it worked.
>
> but now i have another problem when i run the code i get exception like
> this:
> maybe you know why?
> HTTP ERROR 403
>
> Problem accessing /Darimpo.html. Reason:
>
> !Secure
>
> --
> *Powered by Jetty://*
>
>
> thank you again
>
>
> On Wednesday, 10 May 2017 12:35:50 UTC+3, Thomas Broyer wrote:
>>
>>
>>
>> On Wednesday, May 10, 2017 at 6:57:25 AM UTC+2, Gal Lavie wrote:
>>>
>>> Hi everyone
>>> I develop application in gwt and google app engine.
>>> until now i used with gwt 2.7 lib and google app engine 1.51 lib
>>> i try to upgrade the gwt 2.7 to 2.8.1 lib
>>> and i have 2 problems now
>>> i hope you can help me
>>> 1) when i try to run the project i get exception in devModeBase.class
>>> file in run method
>>> this is the log of run + exception:
>>>
>>> Running CodeServer with parameters: [-noprecompile, -port, 65462,
>>> -sourceLevel, 1.8, -bindAddress, 127.0.0.1, -launcherDir,
>>> /Users/gallavie/Documents/workspace/Darimpo/war, -logLevel, INFO, -style,
>>> OBFUSCATED, com.darimpo.Darimpo, com.darimpo.Darimpo]
>>>
>>> Super Dev Mode starting up
>>>
>>>workDir:
>>> /var/folders/fj/8gtg078929j8hjtfzyy5srv4gn/T/gwt-codeserver-8030568012575356208.tmp
>>>
>>> 2017-05-10 06:44:10.582:INFO::main: Logging initialized @3822ms
>>>
>>>Loading Java files in com.darimpo.Darimpo.
>>>
>>>Ignored 33 units with compilation errors in first pass.
>>>
>>> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
>>> errors.
>>>
>>>Module setup completed in 4961 ms
>>>
>>>Loading Java files in com.darimpo.Darimpo.
>>>
>>>Ignored 33 units with compilation errors in first pass.
>>>
>>> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
>>> errors.
>>>
>>>Module setup completed in 1273 ms
>>>
>>> 2017-05-10 06:44:15.046:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
>>>
>>> 2017-05-10 06:44:15.164:INFO:oejsh.ContextHandler:main: Started
>>> o.e.j.s.ServletContextHandler@7a508fdc{/,null,AVAILABLE}
>>>
>>> 2017-05-10 06:44:15.301:INFO:oejs.ServerConnector:main: Started
>>> ServerConnector@4ca4b342{HTTP/1.1}{127.0.0.1:65462}
>>>
>>> 2017-05-10 06:44:15.313:INFO:oejs.Server:main: Started @8553ms
>>>
>>>
>>> The code server is ready at http://127.0.0.1:65462/
>>>
>>> Code server started in 6.828 s ms
>>>
>>> 2017-05-10 06:44:15.702:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
>>>
>>> 2017-05-10 06:44:19.948:WARN:oejuc.AbstractLifeCycle:main: FAILED
>>> org.eclipse.jetty.annotations.ServletContainerInitializersStarter@1e23623:
>>> java.lang.NoSuchMethodError:
>>> javax.servlet.ServletContext.getJspConfigDescriptor()Ljavax/servlet/descriptor/JspConfigDescriptor;
>>>
>>> java.lang.NoSuchMethodError:
>>> javax.servlet.ServletContext.getJspConfigDescriptor()Ljavax/servlet/descriptor/JspConfigDescriptor;
>>>
>>
>> Check your classpath, you probably have Servlets API in version 2.x (2.4,
>> 2.5). This method was added in Servlets 3.0 (
>> https://docs.oracle.com/javaee/7/api/javax/servlet/ServletContext.html#getJspConfigDescriptor--),
>>
>> and Jetty 9.2.14.v20151106 (the version that GWT uses) actually needs
>> Servlets 3.1.0 (
>> https://search.maven.org/#artifactdetails%7Corg.eclipse.jetty%7Cjetty-project%7C9.2.14.v20151106%7Cjar
>> )
>> (GWT 2.7.0 was using Jetty 8.1.12.v20130726, which BTW already needed
>> Servlets 3.0
>> https://search.maven.org/#artifactdetails%7Corg.eclipse.jetty%7Cjetty-project%7C8.1.12.v20130726%7Cjar,
>>
>> but could have maybe worked OK with Servlets 2.5 – I doubt it, maybe you
>> changed the order of JARs in your classpath when upgrading; GWT 2.7 used to
>> bundle the Servlets API into gwt-dev, and this has changed in 2.8.1, when
>> retrieved from the Central Repository)
>>
>> 2) when i try to compile the project i get this exception
>>>
>>>
>>>
>>>[ERROR] An internal compiler exception occurred
>>>
>>> com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error
>>> during visit.
>>>
>>> at
>>> com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:111)
>>>
>>> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:276)
>>>
>>> at
Re: upgrade gwt 2.7 to gwt 2.8.1 not working
wwoo thank you
this worked for me
for the second problem i removed google map and this is worked for me (i
did this in past and it not worked but now it work i do not know why but
now it work)
for the first problem the solution is the order of libs. i go to the orders
of libs and put the gwt before google app engine and it worked.
but now i have another problem when i run the code i get exception like
this:
maybe you know why?
HTTP ERROR 403
Problem accessing /Darimpo.html. Reason:
!Secure
--
*Powered by Jetty://*
thank you again
On Wednesday, 10 May 2017 12:35:50 UTC+3, Thomas Broyer wrote:
>
>
>
> On Wednesday, May 10, 2017 at 6:57:25 AM UTC+2, Gal Lavie wrote:
>>
>> Hi everyone
>> I develop application in gwt and google app engine.
>> until now i used with gwt 2.7 lib and google app engine 1.51 lib
>> i try to upgrade the gwt 2.7 to 2.8.1 lib
>> and i have 2 problems now
>> i hope you can help me
>> 1) when i try to run the project i get exception in devModeBase.class
>> file in run method
>> this is the log of run + exception:
>>
>> Running CodeServer with parameters: [-noprecompile, -port, 65462,
>> -sourceLevel, 1.8, -bindAddress, 127.0.0.1, -launcherDir,
>> /Users/gallavie/Documents/workspace/Darimpo/war, -logLevel, INFO, -style,
>> OBFUSCATED, com.darimpo.Darimpo, com.darimpo.Darimpo]
>>
>> Super Dev Mode starting up
>>
>>workDir:
>> /var/folders/fj/8gtg078929j8hjtfzyy5srv4gn/T/gwt-codeserver-8030568012575356208.tmp
>>
>> 2017-05-10 06:44:10.582:INFO::main: Logging initialized @3822ms
>>
>>Loading Java files in com.darimpo.Darimpo.
>>
>>Ignored 33 units with compilation errors in first pass.
>>
>> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
>> errors.
>>
>>Module setup completed in 4961 ms
>>
>>Loading Java files in com.darimpo.Darimpo.
>>
>>Ignored 33 units with compilation errors in first pass.
>>
>> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
>> errors.
>>
>>Module setup completed in 1273 ms
>>
>> 2017-05-10 06:44:15.046:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
>>
>> 2017-05-10 06:44:15.164:INFO:oejsh.ContextHandler:main: Started
>> o.e.j.s.ServletContextHandler@7a508fdc{/,null,AVAILABLE}
>>
>> 2017-05-10 06:44:15.301:INFO:oejs.ServerConnector:main: Started
>> ServerConnector@4ca4b342{HTTP/1.1}{127.0.0.1:65462}
>>
>> 2017-05-10 06:44:15.313:INFO:oejs.Server:main: Started @8553ms
>>
>>
>> The code server is ready at http://127.0.0.1:65462/
>>
>> Code server started in 6.828 s ms
>>
>> 2017-05-10 06:44:15.702:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
>>
>> 2017-05-10 06:44:19.948:WARN:oejuc.AbstractLifeCycle:main: FAILED
>> org.eclipse.jetty.annotations.ServletContainerInitializersStarter@1e23623:
>> java.lang.NoSuchMethodError:
>> javax.servlet.ServletContext.getJspConfigDescriptor()Ljavax/servlet/descriptor/JspConfigDescriptor;
>>
>> java.lang.NoSuchMethodError:
>> javax.servlet.ServletContext.getJspConfigDescriptor()Ljavax/servlet/descriptor/JspConfigDescriptor;
>>
>
> Check your classpath, you probably have Servlets API in version 2.x (2.4,
> 2.5). This method was added in Servlets 3.0 (
> https://docs.oracle.com/javaee/7/api/javax/servlet/ServletContext.html#getJspConfigDescriptor--),
>
> and Jetty 9.2.14.v20151106 (the version that GWT uses) actually needs
> Servlets 3.1.0 (
> https://search.maven.org/#artifactdetails%7Corg.eclipse.jetty%7Cjetty-project%7C9.2.14.v20151106%7Cjar
> )
> (GWT 2.7.0 was using Jetty 8.1.12.v20130726, which BTW already needed
> Servlets 3.0
> https://search.maven.org/#artifactdetails%7Corg.eclipse.jetty%7Cjetty-project%7C8.1.12.v20130726%7Cjar,
>
> but could have maybe worked OK with Servlets 2.5 – I doubt it, maybe you
> changed the order of JARs in your classpath when upgrading; GWT 2.7 used to
> bundle the Servlets API into gwt-dev, and this has changed in 2.8.1, when
> retrieved from the Central Repository)
>
> 2) when i try to compile the project i get this exception
>>
>>
>>
>>[ERROR] An internal compiler exception occurred
>>
>> com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during
>> visit.
>>
>> at
>> com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:111)
>>
>> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:276)
>>
>> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
>>
>> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
>>
>> at
>> com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:76)
>>
>> at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
>>
>> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
>>
>> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
>>
>> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
>>
>> at
>>
Re: upgrade gwt 2.7 to gwt 2.8.1 not working
On Wednesday, May 10, 2017 at 6:57:25 AM UTC+2, Gal Lavie wrote:
>
> Hi everyone
> I develop application in gwt and google app engine.
> until now i used with gwt 2.7 lib and google app engine 1.51 lib
> i try to upgrade the gwt 2.7 to 2.8.1 lib
> and i have 2 problems now
> i hope you can help me
> 1) when i try to run the project i get exception in devModeBase.class file
> in run method
> this is the log of run + exception:
>
> Running CodeServer with parameters: [-noprecompile, -port, 65462,
> -sourceLevel, 1.8, -bindAddress, 127.0.0.1, -launcherDir,
> /Users/gallavie/Documents/workspace/Darimpo/war, -logLevel, INFO, -style,
> OBFUSCATED, com.darimpo.Darimpo, com.darimpo.Darimpo]
>
> Super Dev Mode starting up
>
>workDir:
> /var/folders/fj/8gtg078929j8hjtfzyy5srv4gn/T/gwt-codeserver-8030568012575356208.tmp
>
> 2017-05-10 06:44:10.582:INFO::main: Logging initialized @3822ms
>
>Loading Java files in com.darimpo.Darimpo.
>
>Ignored 33 units with compilation errors in first pass.
>
> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
> errors.
>
>Module setup completed in 4961 ms
>
>Loading Java files in com.darimpo.Darimpo.
>
>Ignored 33 units with compilation errors in first pass.
>
> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
> errors.
>
>Module setup completed in 1273 ms
>
> 2017-05-10 06:44:15.046:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
>
> 2017-05-10 06:44:15.164:INFO:oejsh.ContextHandler:main: Started
> o.e.j.s.ServletContextHandler@7a508fdc{/,null,AVAILABLE}
>
> 2017-05-10 06:44:15.301:INFO:oejs.ServerConnector:main: Started
> ServerConnector@4ca4b342{HTTP/1.1}{127.0.0.1:65462}
>
> 2017-05-10 06:44:15.313:INFO:oejs.Server:main: Started @8553ms
>
>
> The code server is ready at http://127.0.0.1:65462/
>
> Code server started in 6.828 s ms
>
> 2017-05-10 06:44:15.702:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
>
> 2017-05-10 06:44:19.948:WARN:oejuc.AbstractLifeCycle:main: FAILED
> org.eclipse.jetty.annotations.ServletContainerInitializersStarter@1e23623:
> java.lang.NoSuchMethodError:
> javax.servlet.ServletContext.getJspConfigDescriptor()Ljavax/servlet/descriptor/JspConfigDescriptor;
>
> java.lang.NoSuchMethodError:
> javax.servlet.ServletContext.getJspConfigDescriptor()Ljavax/servlet/descriptor/JspConfigDescriptor;
>
Check your classpath, you probably have Servlets API in version 2.x (2.4,
2.5). This method was added in Servlets 3.0
(https://docs.oracle.com/javaee/7/api/javax/servlet/ServletContext.html#getJspConfigDescriptor--),
and Jetty 9.2.14.v20151106 (the version that GWT uses) actually needs
Servlets 3.1.0
(https://search.maven.org/#artifactdetails%7Corg.eclipse.jetty%7Cjetty-project%7C9.2.14.v20151106%7Cjar)
(GWT 2.7.0 was using Jetty 8.1.12.v20130726, which BTW already needed
Servlets
3.0
https://search.maven.org/#artifactdetails%7Corg.eclipse.jetty%7Cjetty-project%7C8.1.12.v20130726%7Cjar,
but could have maybe worked OK with Servlets 2.5 – I doubt it, maybe you
changed the order of JARs in your classpath when upgrading; GWT 2.7 used to
bundle the Servlets API into gwt-dev, and this has changed in 2.8.1, when
retrieved from the Central Repository)
2) when i try to compile the project i get this exception
>
>
>
>[ERROR] An internal compiler exception occurred
>
> com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during
> visit.
>
> at
> com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:111)
>
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:276)
>
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
>
> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
>
> at
> com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:76)
>
> at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
>
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
>
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
>
> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
>
> at
> com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse(JDeclarationStatement.java:49)
>
> at
> com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(JModVisitor.java:88)
>
> at
> com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(JModVisitor.java:331)
>
> at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:94)
>
> at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
>
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
>
> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:139)
>
> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:135)
>
> at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83)
>
> at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
>
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
>
