Graceful shutdown of development mode with Eclipse plug in for GWT 2.0?
Some of my session objects implement HttpSessionBindingListener so that they can do stuff on valueUnbound when the session ends (such as when the servlet container is shutdown). In the old hosted mode this worked fine as closing the hosted mode window caused a graceful shutdown of jetty. With the GWT 2.0 plugin for Eclipse I can only see an option in development mode to Terminate which is not a graceful shutdown and does not cause valueUnbound to be fired. Am I missing something? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Graceful shutdown of development mode with Eclipse plug in for GWT 2.0?
This would be nice for those who have a robust server side system in place. Right now, we're definitely testing how the app reacts to a hard crash. :) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Graceful shutdown of development mode with Eclipse plug in for GWT 2.0?
On Dec 18, 11:20 am, Yozons Support on Gmail yoz...@gmail.com wrote: This would be nice for those who have a robust server side system in place. Right now, we're definitely testing how the app reacts to a hard crash. :) One thing I found is that using the reload web server option in the eclipse Development Mode view does properly trigger valueUnbound. Our java servlets communicate with Windows COM objects using J-Interop and Google Protocol Buffers. When the web app gets a hard crash, it takes a little while for the COM objects to realise and kill themselves. When the session is closed gracefully we get a chance to tell the COM objects to close. At the moment I am doing a reload web server followed by a Terminate so that things are cleaned up reasonably well. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
