Skip to content

Conversation

vegegoku
Copy link
Member

@vegegoku vegegoku commented Jan 9, 2025

Copy link
Member

@FrankHossfeld FrankHossfeld left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume, that this will be linked with en error message. If not, should we point out, that this might be different when using Spring Boot?


## Tips

- The most common reason to encounter this problem with a new project is using RPC, which tries to load `com.google.gwt.user.client.rpc.RemoteService`. The solution is to copy `gwt-servlet.jar` from the GWT install directory into your web app's `war/WEB-INF/lib/` directory.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we remove 'with a new project'? So, we would not limit it to new projects.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, these definitely need to be updated - this is just the first step at migrating them out of gwtproject/gwt itself, we'll want to refine them and possibly add more (jsinterop errors and warnings could use some help sections, or anchors on existing pages)


- The most common reason to encounter this problem with a new project is using RPC, which tries to load `com.google.gwt.user.client.rpc.RemoteService`. The solution is to copy `gwt-servlet.jar` from the GWT install directory into your web app's `war/WEB-INF/lib/` directory.

- If you have a good reason for not following the recommended configuration, you can suppress the warning by setting the Java system property `gwt.nowarn.webapp.classpath`. Specify `-Dgwt.nowarn.webapp.classpath` as a JVM argument when launching hosted mode.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we say: 'If you have good reasons for ...'?

vegegoku added a commit to vegegoku/gwt that referenced this pull request Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants