Hi Fernando, we have a similar setup in a project and we are treating every cascaded layer as a separate resource and thus we create a separate datastore for it via GeoServer REST-API. The idea is that every layer, which is populated by our "GeoServer 02" could (in theory) be from a different WMS (even tough most of the time it is "GeoServer 01".
Or as Andrea stated drop your datastore and re-create ist. This could also be automated via GeoServer REST-API. Cheers Chris On 17.12.21 11:24, Andrea Aime wrote: > On Thu, Dec 16, 2021 at 7:55 PM Fernando Quadro <fsqua...@gmail.com > <mailto:fsqua...@gmail.com>> wrote: > > The question is, is there how this update can be automatic in > GeoServer 02 (when going to Add new layer), when a new layer is > created in GeoServer 01? > > > Not that I know of. GeoServer has only one instance of that WMS store, > which is used alike for OGC requests and configurations. > Not caching the capabilities document would slow down requests > tremendously... and from the p.o.v. of GeoSever the cache is really > just holding an instance of the store, the caps cache is happening > inside the store, which also offers no way to clear it, it's grabbed on > object creation and the functionality of the object depends on having > it at all times. > Currently the only way to drop it, would be to drop the store itself > (so another way is to go and hit the "clear" button in the GeoServer > status panel)... > code changes would be needed to do that. > > Cheers > Andrea > == > > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us <http://bit.ly/gs-services-us>for > more information.==Ing. Andrea Aime @geowolfTechnical Lead > > GeoSolutions Groupphone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 333 8128928 > > > https://www.geosolutionsgroup.com/ <https://www.geosolutionsgroup.com/> > > http://twitter.com/geosolutions_it <http://twitter.com/geosolutions_it> > > ------------------------------------------------------- > > > Con riferimento alla normativa sul trattamento dei dati personali > (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati > “GDPR”), si precisa che ogni circostanza inerente alla presente email > (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui > conoscenza è riservata al/i solo/i destinatario/i indicati dallo > scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a > cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato > se potesse darmene notizia.This email is intended only for the person > or entity to which it is addressed and may contain information that is > privileged, confidential or otherwise protected from disclosure. We > remind that - as provided by European Regulation 2016/679 “GDPR” - > copying, dissemination or use of this e-mail or the information herein > by anyone other than the intended recipient is prohibited. If you have > received this email by mistake, please notify us immediately by > telephone or e-mail > > > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to this > list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
