I havent tried raising the Java level yet, its still  JavaSE-1.8. 
Got as far as using latest versions:
JDK 21
gcloud CLI app & cloudSdkVersion  457.0.0 
appengine-maven-plugin 2.5.0

To get it to run, so far:
1 I had to remove all DOCTYPE declarations in xml files in the server 
project (new restrictions on DTD)
2 appengine-maven-plugin 2.5.0 requires:
                <configuration>
                    <jvmFlags>
                        <item>--add-opens</item>
                <item>java.base/java.util=ALL-UNNAMED</item>
This stops 500 Server Error which I've not seen before:
GCLOUD: java.lang.reflect.InaccessibleObjectException:
Unable to make field accessible: module java.base does not "opens 
java.util" to unnamed module @2c95ac9e

So Craig, you say with Java17 on GAE, there isn't a web server included 
anymore.
So this has to be defined somewhere in  appengine-maven-plugin ?
The minimum level to avoid being shut down on GAE standard is >8
& 11 is the max for GWT, so that would seem do for now, why Java 17  ?

On Wednesday, December 20, 2023 at 4:46:03 AM UTC Craig Mitchell wrote:

> No worries not posting the POMs Tim.
>
> The bit I'm struggling with, the old Java 8 version had its own GAE 
> server.  So I would run that, and a GWT Code Server.  Easy!
>
> *btw:* I'm talking about GAE Standard.  GAE Flexible you can do whatever 
> you want, but that's more work and more expensive.
>
> Now with the upgrade to Java17 on GAE, there isn't a web server included 
> anymore.  It's up to you to supply one.  I would assume when you deploy it, 
> it doesn't actually use your server, but what setup is GAE expecting for 
> the deploy?
>
> I see there is a SpringBoot GAE example, so it might be easier to use 
> that, and get GWT to work with SpringBoot.  Not sure.  Very interested to 
> hear what you're doing.
>
> Thanks!
>
> On Wednesday 20 December 2023 at 1:51:55 pm UTC+11 [email protected] 
> wrote:
>
>> For some years I've been deploying GWT 2.8.2 to GAE with Maven & Google 
>> Cloud Tools. 
>> I now find GAE is not supporting Java 8 after January, so currently 
>> upgrading (rather slowly). 
>> There are 4 long POM files,  probably better to mail them then post a 
>> distilled version here ?
>>
>> On Sunday, December 17, 2023 at 5:20:56 AM UTC Craig Mitchell wrote:
>>
>>> Hi,
>>>
>>> The instructions here 
>>> https://www.gwtproject.org/doc/latest/tutorial/appengine.html are no 
>>> longer valid, as the Google Plugin for Eclipse is now dead (Google no 
>>> longer supports Java 1.8, and the Google Plugin for Eclipse doesn't support 
>>> any Eclipse versions that support anything after Java 1.8).  Ref:  
>>> https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3710
>>>
>>> The new approach with GAE is to use Maven or Gradle with Google Cloud 
>>> Tools.
>>>
>>> I've been struggling to work out how this is supposed to happen.  It 
>>> looks like we now have to provide our own Web Server for GAE, but can we 
>>> use the Jetty server that GWT uses for development?  I assume the deploy 
>>> build would not include the Jetty web server?
>>>
>>> If anyone has deployed a GWT app to GAE with Maven and the new Google 
>>> Cloud Tools, it would be great if you could give high level instructions on 
>>> how it's all supposed to fit together.
>>>
>>> An example Maven POM file with both the Google Cloud Tools, and GWT 
>>> would be even better.  🙂
>>>
>>> Thanks!
>>>
>>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/f0436ca1-fe5c-424f-af21-719788552a78n%40googlegroups.com.

Reply via email to