Yes, I will look at another solution. BTW, ImageCacheRenderer is already catching the Throwable when rendering, and issues a user warning in the Frame statusbar in case of error.
Nicolas On 13 December 2015 at 16:27, <edgar.sol...@web.de> wrote: > On 13.12.2015 16:17, Nicolas Ribot wrote: > > AFAIU, when choosing a layer from a datastore, the OJ Layer is added to > the panel, then a separate thread tries to load the Features. This thread > triggers the actual SQL code for the layer. > > Instead of testing the layer each time a WHERE clause is added/modified, > I chose to catch the SQLException in ImageCacheRenderer thread, then I > remove the layer from the Panel. In case of other error types, layer is > added to the Panel. > > i am not sure that ImageCachingRenderer is a good place to catch > exceptions and remove layers. can you dig in where the renderhook leads to > for database layers? > > ..ede > > > ------------------------------------------------------------------------------ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >
------------------------------------------------------------------------------
_______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
