On 22-05-15 12:28, Andrea Aime wrote:
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?
Only to the beans whose creation has side effects I'd say.
In GeoServer we marked as lazy-init=false those beans whose
initialization attaches listeners, and otherwise changes
the enviroment around them. All other beans should be loadable as they
are actually needed.
For all clarity, with geofence modules I was talking about the actual
*geofence* backend modules themselves, not the community modules in
geoserver. Because the problem concerns beans declared in geofence
itself, not the community modules. So this would mean geofence itself
needs to be changed.
I don't think the problem has anything to do with beans having effects
that change the environment. The problem is very clearly that
'default-autowire="byName" is not working any longer for any context
that is loaded. I have confirmed this. Is this a desired or accidental
effect of your changes? Because geofence relies on autowire byname.
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
