I use a servlet filter to tell the browser not to cache the nocache files:
public class ServletFilter implements Filter {
private static final String NO_CACHE = ".nocache.js";
@Override
public void doFilter(ServletRequest request, ServletResponse response,
FilterChain
chain) throws
Thank you Colin! You're spot on, found
it:
https://mvnrepository.com/artifact/org.gwtproject/gwt-servlet-jakarta/2.11.0
> *Note that this is not compatible with running your jakarta-servlet app
inside dev mode, but you will need to run your own server separately from
dev mode. *
Thanks
Craig, you’ll need to change to the -jakarta artifacts. That is, for
RemoteServiceServlet, instead of gwt-servlet.jar, use gwt-servlet-jakarta.jar,
and the class is in the .rpc.jakarta package to ensure there is no possibility
of referencing the wrong type. Change both the jar and your imports
Awesome! Thank you GWT team!
Regarding:
*> Added release artifacts for jakarta.servlet packages for both
RequestFactory and GWT-RPC.*
When I look at com.google.gwt.user.server.rpc.RemoteServiceServlet, it's
still using javax.servlet.http.HttpServlet. So calls
like getThreadLocalRequest()
One thing I really like about using JSON for my message formats is that
they are human readable (YMMV).
If you're wondering whether a problem is client side or server side, or
when you just want to know exactly what information the client was given,
being able to read the content of messages can
gwt-rpc is one of the parts I like the most about GWT and why we chose GWT
to start with. Same DTOs on client and server and you don't have to care
(too much) about de/serialization. Why do I care about JSON, or binary or
whatever serialized format, as long as it is secure, performant and
