Hello Andrea and Jody, There are two tests in geofence-server that are based on GeoServerTestSupport to initialize the spring context.
They used to work fine but only since recently they started breaking, and I traced it back to this commit you guys did: https://github.com/geoserver/geoserver/commit/ed613876cb6aba59fd922e25fd957f18a85815a2 ("Build speed up with explicitly setting which beans need early initia……lization instead). So I don't understand it 100% yet, but it seems that 'default-autowire="byName"' doesn't function any longer in the test cases, and since geofence beans rely on that they aren't loading properly any more . Before I spend a lot of more time on this I wanted to check if you guys had an easy solution. I noticed the commit adds a lot of 'lazy-init="false"' to the bean definitions. Now the problem is that this regards beans defined in the geofence modules. Does that mean we need to add that stuff to the geofence modules as well? Regards Niels ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
