Hi All,
We have a web application running on Jetty 8. Now we upgraded the Jetty to
Jetty 9.0.7. We are facing an issue now that we are unable to send emails
through our application.
If we move our application back to Jetty 8 the problem is solved.
The JDK version we are using is jdk1.7.0_51
Firstly, you have to use
https://groups.google.com/d/forum/google-web-toolkit to ask support.
Secondly, at first sight, your problem doesn't seem to be related to GWT.
Julien
On Thu, May 22, 2014 at 8:40 AM, shreshth wadhwa shresh...@gmail.comwrote:
Hi All,
We have a web application
For GWT 2.6, Super Dev Mode, and the RemoteServiceServlet, you could set
the gwt.codeserver.port Java property.
On Wed, Nov 20, 2013 at 1:35 AM, Jens jens.nehlme...@gmail.com wrote:
The issue comes up when we change a piece of shared code, like a DTO. What
we've found is that if we don't
You only need to gwt compile once, then just run DevMode.
Ideally, you'd point DevMode's -war at the location Jetty loads your webapp
(so, deploy an exploded WAR, or point -war to the location Jetty exploded
the WAR in the temp folder) so that all the static files it generates
What you're describing is pretty much what we're doing.
The issue comes up when we change a piece of shared code, like a DTO. What
we've found is that if we don't stop, recompile from the command line
(including gwt compile) the updated DTO can't be sent/received...the
GWT-RPC stuff doesn't
The issue comes up when we change a piece of shared code, like a DTO. What
we've found is that if we don't stop, recompile from the command line
(including gwt compile) the updated DTO can't be sent/received...the
GWT-RPC stuff doesn't match up any more and we get failures.
You just
I'm unsure why you need to do a gwtc compile? Why is that?
G
On Wednesday, 20 November 2013 06:39:29 UTC+10, jay wrote:
We have some requirements which have forced us to run our own Jetty
server. This means we're debugging with the --noserver flag. The problem
with this is the amount of
