Hi, This is how Spring Dev Tools work. When it detects a change it removes the old application class loader and creates a new one. Why this is a problem for you ?
I personally prefer to use DCEVM (https://dcevm.github.io/). It is able to redefine a specific class in the current class loader. When I change a Spring @Configuration or Hibernate mapping I just restart the application manually. On Wed, Aug 28, 2019 at 11:25 AM Per Newgro <per.new...@gmx.ch> wrote: > Hello *, > > I migrate my current wicket app to spring boot version ( > https://github.com/MarcGiffing/wicket-spring-boot). > > So far it was straightforward. But now i experience a problem with > inclusion of > <dependency> > > <groupId>org.springframework.boot</groupId> > > <artifactId>spring-boot-devtools</artifactId> > </dependency> > > It seems that the "restart / reload feature" of devtools loads my classes > multiple times, so that they are not equal anymore (x.class <> x.class). > I understand that this is happening. But i would like to know if there is > another option for me beside - removing spring-boot-devtools. > > Would be nice to here from you > Thanks > Per > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
