> > +1 The problem is determining what "provided by the server" actually means > though. Servers generally just use their classpath, but in our case the > classpath generally (because of Eclipse, and because of how DevMode loads > client code too) contains the classes that also are in WEB-INF/lib, so > delegation to the "server classpath" just won't work (or rather, it'll work > "too well", and won't detect that "something is missing in WEB-INF/lib". > > I've written a memo on the issue, and possible solutions: > https://docs.google.com/document/d/1bWfafaPA0m0Z1Swodnx7m3QTv31OdqFkE7aeadN_2BU/edit?usp=sharing >
Wouldn't it be a ton easier to just launch Jetty as a separate process using ProcessBuilder when DevMode is launched? Of course this new process should not have DevMode class path. Then its pretty much like -noserver but users do not have to setup a jetty server themselves. Also I am curious why r4944 says its too much of a burden to get the class path right and why the old behavior causes integration problems. If class path is wrong and GWT "repairs" it, it will fail later in production. I don't really see the benefit. But I have to say that I always use -noserver so maybe I am missing something. -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
