On 07.06.2016 21:59, Michaël Michaud wrote: > Hi Ede, > > Yeah, works fine now.
good to hear > Can you explain in a few words what problem is the new code going to solve ? the initial bug itself was that "instanceof WFSLayer" and casting to it didn't work as the same class was obviously loaded by two different classloaders https://sourceforge.net/p/jump-pilot/feature-requests/234/ that was the result of the former classloader used in PluginManager that explicitly but late loaded some classes from our codebase instead of out of the jars in lib/ext/ and this is needed because for WFS i had to patch some classes in the jars and i didn't want to setup a whole new repo and update the old deegree jars, which will probably be replaced by some other means to load wfs in the future ;) > Why do we need to use a special class loader for the main application ? because if we use "our" class loader early, it is the parent classloader for everything loaded afterwards and hence we can control which class is loaded from where. regards.. ede PS: http://dilbert.com/strip/2016-06-07 PPS: http://dilbert.com/strip/2016-06-08 ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
