>
> Jody, I also noticed that the Resource API plan doc on the wiki said the
> TemplateLoader wasn't handled yet in the transition. Is that accurate or
> out-of-date? I assume this is where changes would be made to support FTL
> files. https://github.com/geoserver/geoserver/wiki/Resource-API-
> Transition-Plan#file-events
Everything has been migrated over to ResourceStore, if you find any gaps
mark them as bugs.
Note configuring each node with a temporary filesystem is required, a few
libraries we use require us to unpack the BLOB into a file and then pass
file reference in. I think only 1 or 2 spots in the codebase require this
so I am not fussed.
If complete configuration coordination (FTL and Image Mosaic config), to
> your knowledge, is available with the JMS plugin, I may look into that
> again. Doing complete configuration reload works reasonably well for us
> presently as we have a large amount of data in a fairly small number of
> layers (~100) / stores (~10, but I can imagine in a scenario with 1000s+
> plus this would be more problematic.
>
For image mosaic you can also configure it to use a database, rather than a
shapefile for granule management, not sure if that is of interest.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
