Just for the record, GWT 1.6 is switching to Jetty per the roadmap, and adding support for building into a WAR structure already (which will make it easier to customize the embedded, and to just package up for deploy). So this is gonna get better as things go along.
http://googlewebtoolkit.blogspot.com/2008/12/whats-ahead-for-google-web-toolkit_10.html On Dec 12, 7:15 am, "Mirko Nasato" <[email protected]> wrote: > I use jetty:run-exploded to start the server, and mvn gwt:gwt or > gwt:debug when working on the UI. Yes there are limitations with this > approach in that you need to restart Jetty in some cases, but it's > good enough for me at the moment and it's much simpler to set up than > customising the GWT embedded Tomcat server configuration IMO. > > It would be nice to find a way to make Jetty and GWT play more nicely > together, but I haven't had the time to look into it yet. > > Cheers > > Mirko > > 2008/12/10 Charlie Collins <[email protected]>: > > > > > I can't answer that, I don't use noserver. I know some folks here have > > made a lot of progress with noserver and getting changes to show up > > automatically - but back in the day that was one of the reasons I > > didn't use noserver (the rpc files having to be redeployed, AND the > > fact that noserver doesn't support GWTTestCase based tests). (That's > > also one of the reasons we went so far with GWT-Maven to make it easy > > to manipulate the embedded server - so that the embedded server can > > support other non GWT servlets, JDNI, DataSources, filters, security, > > etc, etc, etc - all without any manual work.) > > > Maybe others here can help more with noserver though, I know a lot of > > people use it - anyone? > > > On Dec 9, 12:29 pm, "P.G.Taboada" <[email protected]> wrote: > >> Hi, > > >> I did setup the -noserver thingy succesfully and I am happy with > >> jetty. The only thingy that's missing is a way of automatically adding > >> the required files to the running jetty (I mean the startup js, the > >> host hmtl, the static ressources and the rpc files). The "static" > >> files are easy to setup, but what about the rpc files? Everytime I > >> touch something I need to regenerate/ redeploy this files. > > >> How are you guys handling this? > > >> brgds, > > >> Papick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
