But this is not a multimodule project (means this is not a tbroyer archetype multimodule project), you need a shared lib, and the client should Not depend on the server, but if you continue with this layout at least explicitly exclude non required libs from the server dependency in the client pom, as anything related with spring.
El lun., 17 jul. 2017 11:05, Andrei Anishchenko <[email protected]> escribió: > Hi, > > I have a Maven multi-module project that uses Spring Framework in the > backend. Everything was working fine until I tried to migrate from GWT > 2.7.0 to 2.8.1. Supposedly production mode works fine (never tried though > so far), but in SuperDev mode I am getting initialization errors coming > from Spring bootstrap. Some built-in Spring beans require them to be > created only once, while attempts to create several of them are taken (see > the log file attached for an example). Digging into this, I discovered that > it has something to do with the fix for > https://github.com/gwtproject/gwt/issues/9292, namely, in > com.google.gwt.dev.shell.jetty.JettyLauncher.WebAppContextWithReload.WebAppClassLoaderExtension#getResources > <https://github.com/gwtproject/gwt/blob/master/dev/core/src/com/google/gwt/dev/shell/jetty/JettyLauncher.java#L373> > method. Before this fix, Jetty's classloader loaded resources strictly from > the lib folder of the web application, and now it is so greedy that it > loads them both from this said folder AND local Maven repo. This makes all > my Maven submodules available twice in the classpath, each if them is > treated individually. > > To demonstrate the issue, I've created a simple application that resembles > my original setup. This application is available here: > https://github.com/AndrewAni/GwtDev. If these > <https://github.com/AndrewAni/GwtDev/blob/master/server/src/main/resources/applicationContext.xml#L5> > two scheduler-related bean definitions are commented out, the problem > doesn't present itself. > > It appears that if I go with Java-based Spring configuration, this > wouldn't bother me anymore, since the suspicious classloader code affects > only loading resources like XMLs. But I cannot shake the feeling that I am > doing something wrong, and with the next GWT development iteration even > Java classes would be loaded differently, breaking my stuff even more. > > Am I missing something? Is my setup wrong somehow? Something about Maven > layout maybe? > > -- > You received this message because you are subscribed to the Google Groups > "GWT Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
