Re: GWT compilation error with JDK 11

[Ying Jin]

Thanks for the information. The compilation problem has already been 
resolved. thanks, Jenny

On Wednesday, July 12, 2023 at 8:32:20 AM UTC-5 RobW wrote:

> I can't comment on the Eclipse plugin side of things, because we don't use 
> those. But I can confirm that basic GWT 2.9/2.10 compilation works fine 
> under Java 11 - that's our main Java platform now. I do recall some 
> migration notes in the GWT 2.9 or 2.10 release notes we had to take care 
> over, but I don't think those were Java version specific. More a case of 
> changes in GWT packaging.
>
> On Tuesday, 11 July 2023 at 23:47:37 UTC+1 Ying Jin wrote:
>
>> Ralph, thanks very much for your suggestion. I'll look into more of the 
>> approach to convert our gwt project to maven project.
>>
>> BTW, I've found the solution to make the GWT plugin work again in my 
>> laptop to compile the GWT project.
>>
>> I came across the following post when searching for the error related to 
>> webappcreator. 
>>
>> After I removed the "classpath" system variable from my new laptop and 
>> moved the GWT SDK to the top of the build path, the GWT Compiler starts 
>> working to compile the GWT project. 
>>
>>
>> https://topic.alibabacloud.com/a/exception-invocation-of-font-colorredcomfont-font-colorredgooglefont-gwt-user-font-colorredtoolsfont-webappcreator-failed-see-the-error-log-for-more-details_8_8_31771273.html
>>
>> Cheers ,
>> Jenny
>>
>>
>> On Tuesday, July 11, 2023 at 12:45:24 PM UTC-5 Ralph Fiergolla wrote:
>>
>>>
>>> It should not be that hard actually: you probably have separated client, 
>>> shared and server side classes following the standard package naming 
>>> convention. That is, basically it will be sufficient to copy your source 
>>> code to the according client/shared/server sub projects and you are done. 
>>> Okay, devil is in the details, but I did the same with some legacy project 
>>> and happily live ever after. Give it a try. Definitely better than spending 
>>> more time on installing different eclipse versions and plug-ins.
>>> Cheers
>>> Ralph 
>>> On Tuesday, July 11, 2023 at 6:51:11 PM UTC+2 Ying Jin wrote:
>>>
>>>> Ralph,
>>>>
>>>> Thanks for your suggestion. However, one of our GWT project in 
>>>> production was developed long time ago and has very big codebase. I'm not 
>>>> sure how hard to convert it to Maven oriented project. It seems that we 
>>>> have to do lots of code refactoring 
>>>> in order to separate client side and server side code and other 
>>>> configuraitons. 
>>>>
>>>> thanks,
>>>> Jenny
>>>>
>>>> On Monday, July 10, 2023 at 11:59:01 PM UTC-5 Ralph Fiergolla wrote:
>>>>
>>>>> Hi Jenny!
>>>>> With all these issues related to out-dated Eclipse plug-ins I would 
>>>>> strongly suggest switching to the new GWT Maven plug-in instead. Follow 
>>>>> the 
>>>>> instructions https://github.com/tbroyer/gwt-maven-archetypes/ to 
>>>>> create a project that you can easily import into the most recent Eclipse 
>>>>> (or any other IDE) subsequently. I don’t see much support for Eclipse 
>>>>> plug-ins coming… I learned it the hard way too but am now happily working 
>>>>> the Maven way. 
>>>>> Bon courage!
>>>>> Ralph 
>>>>> On Monday, July 10, 2023 at 7:25:41 PM UTC+2 Ying Jin wrote:
>>>>>
>>>>>> Hi Colin,
>>>>>>
>>>>>> I posted this issue on the gwt plugin site below, but there is no 
>>>>>> reply yet.
>>>>>>
>>>>>> https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/470
>>>>>>
>>>>>> In addition, I've tried to install other version of Eclipse such as 
>>>>>> Eclipse 4.18 (2020-12) with a new workspace. After I installed GWT 
>>>>>> plugin 3 
>>>>>> from market place and tried to create a sample gwt web application 
>>>>>> project 
>>>>>> as described below in gwt site, I got the error " Invocation of 
>>>>>> com.google.gwt.user.tools.WebAppCreator failed. See the error log for 
>>>>>> more 
>>>>>> details."  It seems to me this current market place gwt plugin didn't 
>>>>>> work 
>>>>>> as I didn't use our project at all
>>>>>> and followed

Re: GWT compilation error with JDK 11

[Ying Jin]

Ralph, thanks very much for your suggestion. I'll look into more of the 
approach to convert our gwt project to maven project.

BTW, I've found the solution to make the GWT plugin work again in my laptop 
to compile the GWT project.

I came across the following post when searching for the error related to 
webappcreator. 

After I removed the "classpath" system variable from my new laptop and 
moved the GWT SDK to the top of the build path, the GWT Compiler starts 
working to compile the GWT project. 

https://topic.alibabacloud.com/a/exception-invocation-of-font-colorredcomfont-font-colorredgooglefont-gwt-user-font-colorredtoolsfont-webappcreator-failed-see-the-error-log-for-more-details_8_8_31771273.html

Cheers ,
Jenny


On Tuesday, July 11, 2023 at 12:45:24 PM UTC-5 Ralph Fiergolla wrote:

>
> It should not be that hard actually: you probably have separated client, 
> shared and server side classes following the standard package naming 
> convention. That is, basically it will be sufficient to copy your source 
> code to the according client/shared/server sub projects and you are done. 
> Okay, devil is in the details, but I did the same with some legacy project 
> and happily live ever after. Give it a try. Definitely better than spending 
> more time on installing different eclipse versions and plug-ins.
> Cheers
> Ralph 
> On Tuesday, July 11, 2023 at 6:51:11 PM UTC+2 Ying Jin wrote:
>
>> Ralph,
>>
>> Thanks for your suggestion. However, one of our GWT project in production 
>> was developed long time ago and has very big codebase. I'm not sure how 
>> hard to convert it to Maven oriented project. It seems that we have to do 
>> lots of code refactoring 
>> in order to separate client side and server side code and other 
>> configuraitons. 
>>
>> thanks,
>> Jenny
>>
>> On Monday, July 10, 2023 at 11:59:01 PM UTC-5 Ralph Fiergolla wrote:
>>
>>> Hi Jenny!
>>> With all these issues related to out-dated Eclipse plug-ins I would 
>>> strongly suggest switching to the new GWT Maven plug-in instead. Follow the 
>>> instructions https://github.com/tbroyer/gwt-maven-archetypes/ to create 
>>> a project that you can easily import into the most recent Eclipse (or any 
>>> other IDE) subsequently. I don’t see much support for Eclipse plug-ins 
>>> coming… I learned it the hard way too but am now happily working the Maven 
>>> way. 
>>> Bon courage!
>>> Ralph 
>>> On Monday, July 10, 2023 at 7:25:41 PM UTC+2 Ying Jin wrote:
>>>
>>>> Hi Colin,
>>>>
>>>> I posted this issue on the gwt plugin site below, but there is no reply 
>>>> yet.
>>>>
>>>> https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/470
>>>>
>>>> In addition, I've tried to install other version of Eclipse such as 
>>>> Eclipse 4.18 (2020-12) with a new workspace. After I installed GWT plugin 
>>>> 3 
>>>> from market place and tried to create a sample gwt web application project 
>>>> as described below in gwt site, I got the error " Invocation of 
>>>> com.google.gwt.user.tools.WebAppCreator failed. See the error log for more 
>>>> details."  It seems to me this current market place gwt plugin didn't work 
>>>> as I didn't use our project at all
>>>> and followed the tutorial below.
>>>>
>>>> https://www.gwtproject.org/usingeclipse.html
>>>>
>>>> Is there a way to get a working GWT plugin for Eclipse which can work 
>>>> with JDK 11?
>>>>
>>>> Your help is much appreciated!
>>>> Jenny
>>>> On Tuesday, July 4, 2023 at 12:43:05 PM UTC-5 Colin Alworth wrote:
>>>>
>>>>> If the class can't be found, something is wrong with your gwt-dev, or 
>>>>> the gwt-dev isn't on the classpath, or more details from the error 
>>>>> message 
>>>>> will indicate why the Compiler class couldn't be loaded. 
>>>>>
>>>>> Please file a bug with more details (logs, full error message, other 
>>>>> details about differences between the working computer and non-working 
>>>>> computer) at https://github.com/gwt-plugins/gwt-eclipse-plugin/ so 
>>>>> contributors there can take a closer look?
>>>>>
>>>>> On Sunday, July 2, 2023 at 2:28:44 PM UTC-5 jiny...@gmail.com wrote:
>>>>>
>>>>>> I tried to reinstall Eclipse again and GWT 3 plugin again from 
>>>>>> Eclipse market, downloaded and reinstalled gwt 

Re: GWT compilation error with JDK 11

[Ying Jin]

Ralph,

Thanks for your suggestion. However, one of our GWT project in production 
was developed long time ago and has very big codebase. I'm not sure how 
hard to convert it to Maven oriented project. It seems that we have to do 
lots of code refactoring 
in order to separate client side and server side code and other 
configuraitons. 

thanks,
Jenny

On Monday, July 10, 2023 at 11:59:01 PM UTC-5 Ralph Fiergolla wrote:

> Hi Jenny!
> With all these issues related to out-dated Eclipse plug-ins I would 
> strongly suggest switching to the new GWT Maven plug-in instead. Follow the 
> instructions https://github.com/tbroyer/gwt-maven-archetypes/ to create a 
> project that you can easily import into the most recent Eclipse (or any 
> other IDE) subsequently. I don’t see much support for Eclipse plug-ins 
> coming… I learned it the hard way too but am now happily working the Maven 
> way. 
> Bon courage!
> Ralph 
> On Monday, July 10, 2023 at 7:25:41 PM UTC+2 Ying Jin wrote:
>
>> Hi Colin,
>>
>> I posted this issue on the gwt plugin site below, but there is no reply 
>> yet.
>>
>> https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/470
>>
>> In addition, I've tried to install other version of Eclipse such as 
>> Eclipse 4.18 (2020-12) with a new workspace. After I installed GWT plugin 3 
>> from market place and tried to create a sample gwt web application project 
>> as described below in gwt site, I got the error " Invocation of 
>> com.google.gwt.user.tools.WebAppCreator failed. See the error log for more 
>> details."  It seems to me this current market place gwt plugin didn't work 
>> as I didn't use our project at all
>> and followed the tutorial below.
>>
>> https://www.gwtproject.org/usingeclipse.html
>>
>> Is there a way to get a working GWT plugin for Eclipse which can work 
>> with JDK 11?
>>
>> Your help is much appreciated!
>> Jenny
>> On Tuesday, July 4, 2023 at 12:43:05 PM UTC-5 Colin Alworth wrote:
>>
>>> If the class can't be found, something is wrong with your gwt-dev, or 
>>> the gwt-dev isn't on the classpath, or more details from the error message 
>>> will indicate why the Compiler class couldn't be loaded. 
>>>
>>> Please file a bug with more details (logs, full error message, other 
>>> details about differences between the working computer and non-working 
>>> computer) at https://github.com/gwt-plugins/gwt-eclipse-plugin/ so 
>>> contributors there can take a closer look?
>>>
>>> On Sunday, July 2, 2023 at 2:28:44 PM UTC-5 jiny...@gmail.com wrote:
>>>
>>>> I tried to reinstall Eclipse again and GWT 3 plugin again from Eclipse 
>>>> market, downloaded and reinstalled gwt 2.9 for the project, however, I 
>>>> still encountered the error below.
>>>> It is so weird, the project configuration in eclipse works in my old 
>>>> laptop, not in the new one though it both has windows 10 installed.
>>>>
>>>> Error: Could not find or load main class com.google.gwt.dev.Compiler
>>>>
>>>> eclipse-jee-2020-06-R-win32-x86_64
>>>> GWT Plugin 3.0
>>>> gwt-2.9.0
>>>>
>>>> Please see attached for the java build path dialog in eclipse.
>>>>
>>>> Any idea about resolving this error? Please help shed some light on 
>>>> this problem.
>>>>
>>>> Your help is much appreciated!
>>>> Jenny
>>>>
>>>>
>>>> On Friday, June 16, 2023 at 3:25:42 PM UTC-5 Ying Jin wrote:
>>>>
>>>>> Thanks for your reply. Please see attached for the GWT lib specified 
>>>>> in the java build path in Eclipse. I tried to compile it with JDK 8 and 
>>>>> it 
>>>>> didn't work either. 
>>>>> The same project configuration in Eclipse worked in my old laptop, but 
>>>>> not in my new laptop. The Eclipse in the new laptop is a copy of the 
>>>>> Eclipse installed in the old laptop.
>>>>>
>>>>> In addition, I also tried to  copy the "gwt-dev.jar" from the old 
>>>>> laptop to the new one, but the compilation still gave me the following 
>>>>> error.
>>>>>
>>>>> Error: Could not find or load main class com.google.gwt.dev.Compiler
>>>>>
>>>>> The project was compiled by using GWT->Compile option provided by the 
>>>>> GWT Plugin installed in Eclipse.
>>>>>
>>>>> Version: 2020-06 (4.16.0)
>>>

Re: GWT compilation error with JDK 11

[Ying Jin]

Hi Colin,

I posted this issue on the gwt plugin site below, but there is no reply yet.

https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/470

In addition, I've tried to install other version of Eclipse such as Eclipse 
4.18 (2020-12) with a new workspace. After I installed GWT plugin 3 from 
market place and tried to create a sample gwt web application project 
as described below in gwt site, I got the error " Invocation of 
com.google.gwt.user.tools.WebAppCreator failed. See the error log for more 
details."  It seems to me this current market place gwt plugin didn't work 
as I didn't use our project at all
and followed the tutorial below.

https://www.gwtproject.org/usingeclipse.html

Is there a way to get a working GWT plugin for Eclipse which can work with 
JDK 11?

Your help is much appreciated!
Jenny
On Tuesday, July 4, 2023 at 12:43:05 PM UTC-5 Colin Alworth wrote:

> If the class can't be found, something is wrong with your gwt-dev, or the 
> gwt-dev isn't on the classpath, or more details from the error message will 
> indicate why the Compiler class couldn't be loaded. 
>
> Please file a bug with more details (logs, full error message, other 
> details about differences between the working computer and non-working 
> computer) at https://github.com/gwt-plugins/gwt-eclipse-plugin/ so 
> contributors there can take a closer look?
>
> On Sunday, July 2, 2023 at 2:28:44 PM UTC-5 jiny...@gmail.com wrote:
>
>> I tried to reinstall Eclipse again and GWT 3 plugin again from Eclipse 
>> market, downloaded and reinstalled gwt 2.9 for the project, however, I 
>> still encountered the error below.
>> It is so weird, the project configuration in eclipse works in my old 
>> laptop, not in the new one though it both has windows 10 installed.
>>
>> Error: Could not find or load main class com.google.gwt.dev.Compiler
>>
>> eclipse-jee-2020-06-R-win32-x86_64
>> GWT Plugin 3.0
>> gwt-2.9.0
>>
>> Please see attached for the java build path dialog in eclipse.
>>
>> Any idea about resolving this error? Please help shed some light on this 
>> problem.
>>
>> Your help is much appreciated!
>> Jenny
>>
>>
>> On Friday, June 16, 2023 at 3:25:42 PM UTC-5 Ying Jin wrote:
>>
>>> Thanks for your reply. Please see attached for the GWT lib specified in 
>>> the java build path in Eclipse. I tried to compile it with JDK 8 and it 
>>> didn't work either. 
>>> The same project configuration in Eclipse worked in my old laptop, but 
>>> not in my new laptop. The Eclipse in the new laptop is a copy of the 
>>> Eclipse installed in the old laptop.
>>>
>>> In addition, I also tried to  copy the "gwt-dev.jar" from the old laptop 
>>> to the new one, but the compilation still gave me the following error.
>>>
>>> Error: Could not find or load main class com.google.gwt.dev.Compiler
>>>
>>> The project was compiled by using GWT->Compile option provided by the 
>>> GWT Plugin installed in Eclipse.
>>>
>>> Version: 2020-06 (4.16.0)
>>> GWT Plugin version: 3.0
>>>
>>> Your help is greatly appreciated!
>>>
>>> thanks,
>>> Jenny
>>> On Friday, June 16, 2023 at 12:33:18 PM UTC-5 Colin Alworth wrote:
>>>
>>>> GWT 2.9 should support running on Java 11, both running on JDK 11 and 
>>>> compiling Java 11 sources.
>>>>
>>>> Without other information, it sounds like there is a problem with your 
>>>> copy of gwt-dev.jar - the jar might be corrupt, or somehow not on your 
>>>> classpath? 
>>>>
>>>> Can you verify that the jar is present and correct, and share more 
>>>> specifics of how you are building?
>>>>
>>>> On Thursday, June 15, 2023 at 6:00:43 PM UTC-5 jiny...@gmail.com wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I tried to compile our GWT 2.9 project with JDK 11, but encountered 
>>>>> the following error:
>>>>>
>>>>> Error: Could not find or load main class com.google.gwt.dev.Compiler
>>>>>
>>>>> Caused by: java.lang.ClassNotFoundException: 
>>>>> com.google.gwt.dev.Compiler
>>>>>
>>>>> BTW, the Eclipse version is  Version: 2020-06 (4.16.0). 
>>>>>
>>>>> Please help shed some lights on this issue.
>>>>>
>>>>> thanks,
>>>>> Jenny
>>>>>
>>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/e627009b-2fb5-48f2-8e6b-b053fd3826d8n%40googlegroups.com.

Re: GWT war file deployment issue on Tomcat 9

[Ying Jin]

Great. Thank you Colin. It works now after using the war file with clean 
build. thanks, Jenny

On Tuesday, July 4, 2023 at 12:44:46 PM UTC-5 Colin Alworth wrote:

> It looks as though the war file that was deployed was built after Super 
> Dev Mode had been started, but before the production build had been 
> performed, so the generated JS only works with a local development server. 
> Try a clean build, without starting dev mode?
>
> If this still doesn't work, can you share more details about exactly how 
> you build the project for production?
>
> On Monday, July 3, 2023 at 11:33:26 AM UTC-5 jiny...@gmail.com wrote:
>
>> We were notified that we need to move our applications off from Weblogic 
>> 14 server to OpenShift platform. The first task is to make sure the GWT 
>> application works in local development environment with Tomcat 9 server. 
>>
>> We can run the GWT application by starting Tomcat 9 server from Eclipse 
>> using WTP. However, when we tried to deploy the war file in the tomcat 9 
>> deployment folder "webapps" and tried to access to the site url as below, 
>> an dialog is displayed as attached asking to get code server ready first. 
>> The war file was created from the war directory after GWT compilation 
>> process is finished. 
>>
>>
>> http://127.0.0.1:8080/aries
>>
>> GWT 2.9
>> JDK 11
>> Eclipse 4,15
>> GWT plugin 3
>>
>>
>> Please help shed some lights on this deployment issue.
>>
>> thanks!
>> Jenny
>>
>>
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/4d9102e8-d715-42dd-bf3b-eb3f690912f3n%40googlegroups.com.

GWT war file deployment issue on Tomcat 9

[Ying Jin]

We were notified that we need to move our applications off from Weblogic 14 
server to OpenShift platform. The first task is to make sure the GWT 
application works in local development environment with Tomcat 9 server. 

We can run the GWT application by starting Tomcat 9 server from Eclipse 
using WTP. However, when we tried to deploy the war file in the tomcat 9 
deployment folder "webapps" and tried to access to the site url as below, 
an dialog is displayed as attached asking to get code server ready first. 
The war file was created from the war directory after GWT compilation 
process is finished. 


http://127.0.0.1:8080/aries

GWT 2.9
JDK 11
Eclipse 4,15
GWT plugin 3


Please help shed some lights on this deployment issue.

thanks!
Jenny



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2c1797af-7301-4fa5-9eca-3b96e7df7dd3n%40googlegroups.com.

GWT compilation error with JDK 11

[Ying Jin]

Hello,

I tried to compile our GWT 2.9 project with JDK 11, but encountered the 
following error:

Error: Could not find or load main class com.google.gwt.dev.Compiler

Caused by: java.lang.ClassNotFoundException: com.google.gwt.dev.Compiler

BTW, the Eclipse version is  Version: 2020-06 (4.16.0). 

Please help shed some lights on this issue.

thanks,
Jenny

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/1312f386-3a06-4b56-b87d-567cd48e24cfn%40googlegroups.com.

Re: Eclpse GWT 3.0 plugin not available

[Ying Jin]

Thanks very much for your suggestion!

Therefore, we're going to use the update site below to install GWT Plugin 
4.0. Please correct me if it is not right.
https://eclipse.gwtproject.org.vertispan.com/2023-02-01

BTW, does it work with JDK 11? We're using GWT 2.9 version and it needs JDK 
11 for local debugging.

In addition, I checked the discussion site. It seems that the updated site 
is still not available in the Eclipse marketplace yet.

thanks,
Jenny



On Monday, February 6, 2023 at 10:41:15 PM UTC-6 hprc wrote:

> GWT Plugin 4.0 is a test but has been released.
> https://eclipse.gwtproject.org.vertispan.com/2023-02-01
> In my environment, by setting the compiler and facet to Java8, I have 
> confirmed that it works on 2022-12 as well.
>
> Also, the GWT-eclipse-plugin is discussed at the following URL.
> https://gitter.im/gwt-plugins/gwt-eclipse-plugin
>
> 2023年2月7日火曜日 1:29:18 UTC+9 jiny...@gmail.com:
>
>> We tried to install GWT plugin 3.0 from Eclipse market place on a new 
>> laptop for 
>> Eclipse Version: 2020-06 (4.16.0), but we got the following not available 
>> error message.
>>
>> This approach worked several months ago, so we're not sure why we got 
>> this error now.
>> Please help give some suggestions for this issue.
>>
>> [image: GWTPluginError.jpg]
>>
>> Your help is much appreciated!
>>
>> thanks,
>> Jenny
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/22402acd-0dda-4594-a95d-26ab21cc6218n%40googlegroups.com.

Eclpse GWT 3.0 plugin not available

[Ying Jin]

We tried to install GWT plugin 3.0 from Eclipse market place on a new 
laptop for 
Eclipse Version: 2020-06 (4.16.0), but we got the following not available 
error message.

This approach worked several months ago, so we're not sure why we got this 
error now.
Please help give some suggestions for this issue.

[image: GWTPluginError.jpg]

Your help is much appreciated!

thanks,
Jenny

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/8dffc1bf-5b58-414c-adcc-ff3db60a303bn%40googlegroups.com.

Re: GWT 2.9, JDK 11 and Tomcat

[Ying Jin]

Great tips! Craig, thank you so much! Your answers saved us much time in 
this upgrade project and finally it works correctly! have a great rest of 
the week! Jenny :)

On Monday, March 21, 2022 at 5:27:38 PM UTC-5 Craig Mitchell wrote:

> (2) As we can only use JS debugger, it will only show javascript variable 
> name.
>
> Also, you should see the Java variable name, as well as the Java code, but 
> in the Chrome JS debugger.  GWT uses source maps to map them together.
>
> On Tuesday, 22 March 2022 at 9:19:29 am UTC+11 Craig Mitchell wrote:
>
>> >  GWT documentation, it suggested to use "noserver" for DevMode launcher 
>> argument
>> I don't see that in the doco:  
>> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/devmodes/CodeServer.html
>>
>> > (1)
>> This is outside of GWTs responsibility.  Sounds like you have an Eclipse 
>> / Log4j / Tomcat config issue.
>>
>> > (2)
>> To watch a variable, just use Chromes debugger:  
>> https://developer.chrome.com/docs/devtools/javascript/reference/#watch
>>
>> Use log, use GWT.log("...") to log messages when running in dev.
>>
>> To log messages in production, you'd need something like this:
>>
>> public static native void log(String log) /*-{
>> $wnd.console.log(log);
>> }-*/;
>>
>> Hope this helps.  :)
>>
>> On Tuesday, 22 March 2022 at 7:12:54 am UTC+11 jiny...@gmail.com wrote:
>>
>>> Craig, 
>>>
>>> Thanks very much for your help! After I changed the launcherDir value to 
>>> the path of my war file location as you suggested, the problem got solved. 
>>> I can run the application in super dev. mode with GWT 2.9, JDK 11 and 
>>> Tomcat 9. 
>>>
>>> -launcherDir C:\Users\jiny\gitCodeServer\aries\war
>>>
>>> The reason I chose previous deployment path is that in the GWT Video it 
>>> suggested to use wtp.deploy arg + context path for the launchDir value.
>>>
>>> The thing I'm still a bit puzzled is that in GWT documentation, it 
>>> suggested to use "noserver" for DevMode launcher argument, but I didn't add 
>>> this option to the DevMode configuration. It still works to use GWT 
>>> Development Mode after running the Tomcat server. The  launcherDir is added 
>>> to the GWT Development Mode(CodeServer) launcher configuration. It would be 
>>> great that you help explain a bit.
>>>
>>> During the process of running and debugging the application in this 
>>> updated environment, I have two questions and hope they can be clarified:
>>>
>>> (1) Is there anyway to show log4j debugging information in the "Console" 
>>> view in Eclipse? After the application is compiled and loaded, the logging 
>>> information is removed and it only shows blank window with "Aries(1) 
>>> [launch Chrome]".
>>>
>>> (2) As we can only use JS debugger, it will only show javascript 
>>> variable name and we used to use "Watch" to check expression value, but we 
>>> don't have this option any more. 
>>>  Java System.out message can no longer be displayed in the console.  Any 
>>> tips for debugging in the super dev. mode?
>>>
>>> Your help is greatly appreciated!
>>> Jenny
>>> On Saturday, March 19, 2022 at 12:50:39 AM UTC-5 Craig Mitchell wrote:
>>>
 It sound like your GWT code server launcher directory setting isn't 
 correct.  And it doesn't look correct either.  It should be the war 
 directory of your project.

 So, something like "c:\whereever_your_code_is\your_project\war" (you 
 might not have called it "war", it's called whatever you put in the 
 settings in GWT -> Web Application -> WAR directory).

 Basically, the GWT code server needs to override the 
 (your_module).nocache.js file, so it need to know where that is, and that 
 is in a directory under your war directory.

 On Friday, 18 March 2022 at 9:59:04 am UTC+11 jiny...@gmail.com wrote:

> Hello,
>
> Recently, I started to resume on our GWT upgrade project with GWT 2.9 
> and JDK 11.
>
> As it has been discussed before, the embedded Jetty server can't work 
> with JDK 11 due to the ASM lib version issue. The recommended approach is 
> to set up an external server, so I followed the following GWT document to 
> manually configure GWT development mode by following steps specified in 
> the 
> second Video. I've watched the video and tried this approach many times, 
> but it still gave 404 error. It seems hard to setup external server and 
> configure Development mode correctly for our project.
>
> Any input or suggestion is greatly appreciated!
>
> *http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html
>  
> *
>
> Manually Configure GWT Development Mode
>
> Manually Configuring the -launcherDir in the GWT Eclipse Plugin
>
> Our GWT project is not Maven oriented and it was developed several 
> years ago with a big codebase. 
>
> 

Re: GWT 2.9, JDK 11 and Tomcat

[Ying Jin]

Craig, 

Thanks very much for your help! After I changed the launcherDir value to 
the path of my war file location as you suggested, the problem got solved. 
I can run the application in super dev. mode with GWT 2.9, JDK 11 and 
Tomcat 9. 

-launcherDir C:\Users\jiny\gitCodeServer\aries\war

The reason I chose previous deployment path is that in the GWT Video it 
suggested to use wtp.deploy arg + context path for the launchDir value.

The thing I'm still a bit puzzled is that in GWT documentation, it 
suggested to use "noserver" for DevMode launcher argument, but I didn't add 
this option to the DevMode configuration. It still works to use GWT 
Development Mode after running the Tomcat server. The  launcherDir is added 
to the GWT Development Mode(CodeServer) launcher configuration. It would be 
great that you help explain a bit.

During the process of running and debugging the application in this updated 
environment, I have two questions and hope they can be clarified:

(1) Is there anyway to show log4j debugging information in the "Console" 
view in Eclipse? After the application is compiled and loaded, the logging 
information is removed and it only shows blank window with "Aries(1) 
[launch Chrome]".

(2) As we can only use JS debugger, it will only show javascript variable 
name and we used to use "Watch" to check expression value, but we don't 
have this option any more. 
 Java System.out message can no longer be displayed in the console.  Any 
tips for debugging in the super dev. mode?

Your help is greatly appreciated!
Jenny
On Saturday, March 19, 2022 at 12:50:39 AM UTC-5 Craig Mitchell wrote:

> It sound like your GWT code server launcher directory setting isn't 
> correct.  And it doesn't look correct either.  It should be the war 
> directory of your project.
>
> So, something like "c:\whereever_your_code_is\your_project\war" (you might 
> not have called it "war", it's called whatever you put in the settings in 
> GWT -> Web Application -> WAR directory).
>
> Basically, the GWT code server needs to override the 
> (your_module).nocache.js file, so it need to know where that is, and that 
> is in a directory under your war directory.
>
> On Friday, 18 March 2022 at 9:59:04 am UTC+11 jiny...@gmail.com wrote:
>
>> Hello,
>>
>> Recently, I started to resume on our GWT upgrade project with GWT 2.9 and 
>> JDK 11.
>>
>> As it has been discussed before, the embedded Jetty server can't work 
>> with JDK 11 due to the ASM lib version issue. The recommended approach is 
>> to set up an external server, so I followed the following GWT document to 
>> manually configure GWT development mode by following steps specified in the 
>> second Video. I've watched the video and tried this approach many times, 
>> but it still gave 404 error. It seems hard to setup external server and 
>> configure Development mode correctly for our project.
>>
>> Any input or suggestion is greatly appreciated!
>>
>> *http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html
>>  
>> *
>>
>> Manually Configure GWT Development Mode
>>
>> Manually Configuring the -launcherDir in the GWT Eclipse Plugin
>>
>> Our GWT project is not Maven oriented and it was developed several years 
>> ago with a big codebase. 
>>
>> Step 1: Converted Aries project to Dynamic Web Project by adding project 
>> facet "Dynamic Web Module" in Eclipse.
>>
>> Step 2: Set up Apache Tomcat 9 Server
>>
>> Step 3: Add the project to server. Right click on Server -> Add and Remove
>>
>> Step 4: Start the Tomcat Server
>>
>> Step 5: Right click project->Debug As -> GWT Development mode
>>
>> Step 6. It started fine. Stop it so we can add the -launcherDir Program 
>> Arg
>>
>> Step 7: Double click on Tomcat server, select Open launch configuration
>>
>>  Get the server web app directory root: wtp.deploy
>>
>> Copy path
>>
>>  
>> C:\EclipseGWTCodeServerWorkSpace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps
>>
>> Step 8. Open the file explorer to see the deployment path
>>
>> Step 9: Go to Debug Configurations
>>
>> GWT Development Mode (CodeServer)->Arguments.
>>
>> Add -launcherDir
>>
>> Value: It is the wtp.deploy arg + context path.
>>
>> After updated the Argument to GWT Development Mode(CodeServer), the 
>> Arguments tab has following content:
>>
>> -launcherDir 
>> C:\EclipseGWTCodeServerWorkSpace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\aries
>>  
>> -logLevel INFO -port 9876 edu.vanderbilt.mc.aries.ARIES
>>
>> Step 10 Launch the code server, click on Debug from CodeServer dialog. 
>> Now both the Web Server and Code Server are running. Back to the file 
>> manager. Watching for the application directory to be created.
>>
>> Step 11: Launch the browser for debugging with the Javascript Debugging
>>
>> Open with SBDG debugger
>>
>> Step 12: Open browser with Code Server URL: 127.0.0.1:9876 and Change 
>> the port 

GWT 2.9, JDK 11 and Tomcat

[Ying Jin]

Hello,

Recently, I started to resume on our GWT upgrade project with GWT 2.9 and 
JDK 11.

As it has been discussed before, the embedded Jetty server can't work with 
JDK 11 due to the ASM lib version issue. The recommended approach is to set 
up an external server, so I followed the following GWT document to manually 
configure GWT development mode by following steps specified in the second 
Video. I've watched the video and tried this approach many times, but it 
still gave 404 error. It seems hard to setup external server and configure 
Development mode correctly for our project.

Any input or suggestion is greatly appreciated!

*http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html*

Manually Configure GWT Development Mode

Manually Configuring the -launcherDir in the GWT Eclipse Plugin

Our GWT project is not Maven oriented and it was developed several years 
ago with a big codebase. 

Step 1: Converted Aries project to Dynamic Web Project by adding project 
facet "Dynamic Web Module" in Eclipse.

Step 2: Set up Apache Tomcat 9 Server

Step 3: Add the project to server. Right click on Server -> Add and Remove

Step 4: Start the Tomcat Server

Step 5: Right click project->Debug As -> GWT Development mode

Step 6. It started fine. Stop it so we can add the -launcherDir Program Arg

Step 7: Double click on Tomcat server, select Open launch configuration

 Get the server web app directory root: wtp.deploy

Copy path

 
C:\EclipseGWTCodeServerWorkSpace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps

Step 8. Open the file explorer to see the deployment path

Step 9: Go to Debug Configurations

GWT Development Mode (CodeServer)->Arguments.

Add -launcherDir

Value: It is the wtp.deploy arg + context path.

After updated the Argument to GWT Development Mode(CodeServer), the 
Arguments tab has following content:

-launcherDir 
C:\EclipseGWTCodeServerWorkSpace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\aries
 
-logLevel INFO -port 9876 edu.vanderbilt.mc.aries.ARIES

Step 10 Launch the code server, click on Debug from CodeServer dialog. Now 
both the Web Server and Code Server are running. Back to the file manager. 
Watching for the application directory to be created.

Step 11: Launch the browser for debugging with the Javascript Debugging

Open with SBDG debugger

Step 12: Open browser with Code Server URL: 127.0.0.1:9876 and Change the 
port number to 8080 ( the Tomcat web server port number)

It gave me 404 Not found error.

Your help is greatly appreciated, 

Jenny

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/0a4b0900-1c40-4e2e-b9c8-de70743745f2n%40googlegroups.com.

Re: GWT 2.9, JDK 11 project upgrade issue: HTTP ERROR: 503: SERVICE_UNAVAILABLE

[Ying Jin]

Jens, Thanks very much for your help! We'll follow the instructions in the 
guide you provided for further configuration. have a great rest of the 
week! Jenny

On Wednesday, June 30, 2021 at 4:42:45 PM UTC-5 Jens wrote:

> Currently, I'm working on installing WebLogic server 14 my in Eclipse for 
>> local deployment, however, I'm not sure if this is a better way for our 
>> local development as I don't have much experience with Weblogic server. The 
>> production WebLogic server on Linux is maintained by another group.  
>>
>
>> Would Jetty or Tomcat server be a better choice in terms of easy 
>> configuration etc.? If so, we should install the latest version, right?
>>
>
> If your server side code does not need a complete Java EE 8 server then 
> you could also use Jetty/Tomcat. Since WebLogic 14 supports Servlet API 4.0 
> your Jetty/Tomcat version should also support it. So for Jetty you would 
> choose Jetty 10.x.
>
> Jetty is relatively easy to configure, all you need to do is activating 
> the modules/plugins you need. To deploy a *.war file to Jetty you would 
> need the server, http and deploy module. You can basically do the quick 
> setup in their documentation: 
> https://www.eclipse.org/jetty/documentation/jetty-10/operations-guide/index.html#og-quick-setup
>
> If you don't want to copy your war file into the jetty-base/webapps folder 
> you could instead place a xml file into that folder which tells jetty where 
> to find the *.war file, see: 
> https://www.eclipse.org/jetty/documentation/jetty-10/operations-guide/index.html#og-deploy-jetty
>  
> . Since Jetty can deploy exploded war folders that xml file could point 
> directly to C:/Users/jiny/gitTestUpgrade/aries/war
>
> -- J.
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/ef32b229-3156-49c3-a0f2-a1121b1e10fdn%40googlegroups.com.

Re: GWT 2.9, JDK 11 project upgrade issue: HTTP ERROR: 503: SERVICE_UNAVAILABLE

[Ying Jin]

Thanks a lot for your explanation. 

The thing that puzzled me was that the HTTP 503 error generated when the 
ear file was deployed to Weblogic 14 server. If the error and warning can 
be ignored, why did we encounter this HTTP 503 error? What is the best way 
to figure out what caused this server error?

Currently, I'm working on installing WebLogic server 14 my in Eclipse for 
local deployment, however, I'm not sure if this is a better way for our 
local development as I don't have much experience with Weblogic server. The 
production WebLogic server on Linux is maintained by another group. 

Would Jetty or Tomcat server be a better choice in terms of easy 
configuration etc.? If so, we should install the latest version, right?

Your help is much appreciated,
Jenny 

On Friday, June 25, 2021 at 5:01:19 AM UTC-5 Jens wrote:

>
>> The code server is ready at http://127.0.0.1:9876/
>> Code server started in 4.878 s ms
>> *[ERROR] jreLeakPrevention.gcDaemonFail*
>> *java.lang.ClassNotFoundException: sun.misc.GC*
>>
>
> This can be ignored. GWT's class JettyLauncher tries to fix a class loader 
> memory leak within sun.misc.GC but this class does not exist in that 
> package in Java 11. The exception is catched and logged as error, but code 
> will continue.
>
>
> java.lang.RuntimeException: Error scanning entry module-info.class from 
>> jar 
>> file:/C:/Users/jiny/gitTestUpgrade/aries/war/WEB-INF/lib/jakarta.xml.soap-api-1.4.1.jar
>> at 
>> org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:913)
>> at 
>> org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)
>> at 
>> org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)
>> at 
>> org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)
>> at 
>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
>> at 
>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
>> at java.base/java.lang.Thread.run(Thread.java:834)
>> Caused by: java.lang.UnsupportedOperationException: This feature requires 
>> ASM6
>> at org.objectweb.asm.ClassVisitor.visitModule(ClassVisitor.java:130)
>> at 
>> org.objectweb.asm.ClassReader.readModuleAttributes(ClassReader.java:724)
>> at org.objectweb.asm.ClassReader.accept(ClassReader.java:544)
>> at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)
>> at 
>> org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)
>> at 
>> org.eclipse.jetty.annotations.AnnotationParser.parseJarEntry(AnnotationParser.java:956)
>> at 
>> org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:909)
>> ... 6 more
>>
>
>
> The embedded Jetty provided by GWT's DevMode class is too old to handle 
> module-info.class files correctly during class file scanning. It basically 
> requires newer ASM version.
>
> The recommend approach for anything other than a small demo app is to not 
> use the embedded Jetty provided by GWT DevMode. Instead use your own Jetty 
> installation or a Jetty plugin for Gradle/Maven to deploy the server side 
> part of your app. Or even better use the same application server that you 
> are also using in production to minimize development/production 
> differences. Once you do that you can also directly use GWT's CodeServer 
> class without going through DevMode class. This will also remove the error 
> log regarding sun.misc.GC.
>
> There is also a discussion in 
> https://groups.google.com/g/google-web-toolkit-contributors/c/iU9hckIab2o 
> to gather feedback wether or not GWT should remove embedded Jetty support. 
> It makes configuring a server more complex but you also don't run into a 
> situation where everything seems to look right, but still it does not work, 
> as in your case.
>
> -- J.
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/beefbaf2-c7f9-4399-acd6-392380d378a4n%40googlegroups.com.

GWT 2.9, JDK 11 project upgrade issue: HTTP ERROR: 503: SERVICE_UNAVAILABLE

[Ying Jin]

Thanks in advance for your time to help with this issue.

After much hard work, we finally resolved all of the errors related to the 
GWT compilation process for our application upgraded from GWT 2.5 to 2.9, 
from JDK 8 to JDK 11. 

However, when I run the application with "Run as -> GWT development mode 
with Jetty",
I got the following error and warning:

I searched online for the error highlighted below and the post said this 
error can be ignored. When we created ear file and deployed it to Weblogic 
server 14 and it gave 
HTTP ERROR: 503: SERVICE_UNAVAILABLE

It would be great if you can help shed some light on this issue.

Running CodeServer with parameters: [-noprecompile, -port, 9876, 
-sourceLevel, 1.8, -bindAddress, 127.0.0.1, -launcherDir, 
C:\Users\jiny\gitTestUpgrade\aries\war, -logLevel, INFO, -style, 
OBFUSCATED, edu.vanderbilt.mc.aries.ARIES]
Super Dev Mode starting up
   workDir: 
C:\Users\jiny\AppData\Local\Temp\gwt-codeserver-15364372133406537389.tmp
   Loading Java files in edu.vanderbilt.mc.aries.ARIES.
   Ignored 9 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 4592 ms

The code server is ready at http://127.0.0.1:9876/
Code server started in 4.878 s ms
*[ERROR] jreLeakPrevention.gcDaemonFail*
*java.lang.ClassNotFoundException: sun.misc.GC*
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:315)
at 
com.google.gwt.dev.shell.jetty.JettyLauncher.jreLeakPrevention(JettyLauncher.java:899)
at 
com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:722)
at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:636)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:898)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:705)
at com.google.gwt.dev.DevMode.main(DevMode.java:432)
Starting Jetty on port 
   [WARN] 
java.lang.NullPointerException
at 
java.base/java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
at 
org.eclipse.jetty.annotations.ClassInheritanceHandler.addToInheritanceMap(ClassInheritanceHandler.java:72)
at 
org.eclipse.jetty.annotations.ClassInheritanceHandler.handle(ClassInheritanceHandler.java:58)
at 
org.eclipse.jetty.annotations.AnnotationParser$MyClassVisitor.visit(AnnotationParser.java:480)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:533)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)
at 
org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)
at 
org.eclipse.jetty.annotations.AnnotationParser.parseJarEntry(AnnotationParser.java:956)
at 
org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:909)
at 
org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)
at 
org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)
at 
org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.base/java.lang.Thread.run(Thread.java:834)
   [WARN] Failed startup of context 
c.g.g.d.s.j.WebAppContextWithReload@491dfd8e{/,file:/C:/Users/jiny/gitTestUpgrade/aries/war/,STARTING}{C:\Users\jiny\gitTestUpgrade\aries\war}
java.lang.RuntimeException: Error scanning entry module-info.class from jar 
file:/C:/Users/jiny/gitTestUpgrade/aries/war/WEB-INF/lib/jakarta.xml.soap-api-1.4.1.jar
at 
org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:913)
at 
org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)
at 
org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)
at 
org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.UnsupportedOperationException: This feature requires 
ASM6
at org.objectweb.asm.ClassVisitor.visitModule(ClassVisitor.java:130)
at org.objectweb.asm.ClassReader.readModuleAttributes(ClassReader.java:724)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:544)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)
at 
org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)
at 
org.eclipse.jetty.annotations.AnnotationParser.parseJarEntry(AnnotationParser.java:956)

[no subject]

[Ying Jin]

Hello,

We have an application can not compile using GWT-2.9 with JDK 11 after
upgraded from GWT 2.5 and JDK 8.

It would be great if you can help shed some light on this. Please see below
for the error:

Compiling module edu.vanderbilt.mc.aries.ARIES
[ERROR] Unexpected internal compiler error
java.lang.NoSuchFieldError: warningThreshold
at com.google.gwt.dev.javac.JdtCompiler$1.(JdtCompiler.java:634)
at
com.google.gwt.dev.javac.JdtCompiler.getStandardCompilerOptions(JdtCompiler.java:632)
at
com.google.gwt.dev.javac.JdtCompiler.getCompilerOptions(JdtCompiler.java:664)
at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:1015)
at
com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:322)
at
com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:532)
at
com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:464)
at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:423)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:210)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:190)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:131)
at com.google.gwt.dev.Compiler.compile(Compiler.java:192)
at com.google.gwt.dev.Compiler.compile(Compiler.java:143)
at com.google.gwt.dev.Compiler.compile(Compiler.java:132)
at com.google.gwt.dev.Compiler$1.run(Compiler.java:110)
at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
at
com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
at com.google.gwt.dev.Compiler.main(Compiler.java:113)

Your help is greatly appreiciated!
Jenny

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CAM6-NoWf2obbXjeN7Y5aUFjthf_0EcsyW_%2Bv9U%2B-6X2Q_7htqg%40mail.gmail.com.

Re: upgrade GWT project from 2.5 to 2.7

[Ying Jin]

Thanks for all of the information.

Thomas, you're right. Eclipse showed me an error mark in the web.xml as
below, but there is no error message.


http://java.sun.com/dtd/web-app_2_3.dtd;>



dropdownboxServlet

edu.vanderbilt.mc.aries.server.rpc.control.DropDownBoxUIServiceImpl
  

On Mon, Feb 11, 2019 at 4:29 AM Thomas Broyer  wrote:

>
> On Sunday, February 10, 2019 at 1:41:52 PM UTC+1, Jenny Jin wrote:
>>
>> Hello,
>>
>> I'm working on upgrading our application from gwt 2.5 to gwt 2.7 in order
>> to take advantage of the Super Dev mode. I installed new GWT plugin in
>> Eclipse 4.4 in order to get gwt 2.7 library.
>> However, it has been a trying process for this version upgrade. After
>> fixing many errors found in the upgrade process, finally, the application
>> can be compiled by GWT compiler without any errors.
>>
>> After executing command "Run as GWT Development Mode in Eclipse,  I can
>> see the coderserver url as follows:
>> http://localhost:9876
>>
>> When I click on the application link, it gave me message as "This module
>> hasn't been compiled yet.". Therefore, I searched online trying to find out
>> solution. A post suggested that the application should be run on
>> web server first before using code server. After executing the command
>> Run as "GWT Development mode with Jetty",  I got following error message:
>>
>> I've spent much time online trying to find out solution for this error,
>> but I haven't got any luck yet. Hope you can help shed some lights on this
>> issue. Thanks in advance!
>>
>> Runing CodeServer with parameters: [-noprecompile, -port, 9876,
>> -sourceLevel, 1.7, -bindAddress, 127.0.0.1, -launcherDir,
>> C:\Users\jiny\gitNeon\aries\war, -logLevel, INFO,
>> edu.vanderbilt.mc.aries.ARIES]
>> Super Dev Mode starting up
>>workDir:
>> C:\Users\jiny\AppData\Local\Temp\gwt-codeserver-507199880381658069.tmp
>>Loading Java files in edu.vanderbilt.mc.aries.ARIES.
>>Ignored 9 units with compilation errors in first pass.
>> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
>> errors.
>> Starting Jetty on port 
>>[WARN] Failed startup of context
>> c.g.g.d.s.j.WebAppContextWithReload{/,file:/C:/Users/jiny/gitNeon/aries/war/},C:\Users\jiny\gitNeon\aries\war
>> java.lang.reflect.InvocationTargetException
>> 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
>> org.eclipse.jetty.webapp.IterativeDescriptorProcessor.visit(IterativeDescriptorProcessor.java:85)
>> at
>> org.eclipse.jetty.webapp.IterativeDescriptorProcessor.process(IterativeDescriptorProcessor.java:72)
>> at org.eclipse.jetty.webapp.MetaData.resolve(MetaData.java:367)
>> at
>> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1240)
>> at
>> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)
>> at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494)
>> at
>> com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:541)
>> at
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>> at
>> org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
>> at
>> org.eclipse.jetty.server.handler.RequestLogHandler.doStart(RequestLogHandler.java:162)
>> at
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>> at
>> org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
>> at org.eclipse.jetty.server.Server.doStart(Server.java:282)
>> at
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>> at
>> com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:740)
>> at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:632)
>> at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1054)
>> at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:836)
>> at com.google.gwt.dev.DevMode.main(DevMode.java:413)
>> Caused by: java.lang.IllegalStateException: No such servlet:
>> dropdownboxServlet
>> at
>> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1320)
>> at
>> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1414)
>> at
>> org.eclipse.jetty.servlet.ServletHandler.addServletMapping(ServletHandler.java:896)
>> at
>> org.eclipse.jetty.webapp.StandardDescriptorProcessor.addServletMapping(StandardDescriptorProcessor.java:1199)
>> at
>> org.eclipse.jetty.webapp.StandardDescriptorProcessor.visitServletMapping(StandardDescriptorProcessor.java:632)
>> ... 23 more
>>Module setup completed in 5687 ms
>>
>
> Check your web.xml, you seem to have a  with no
> corresponding .
>
> --
> You received this message because you are