-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
after geowebcache upgraded to 1.24, arcgisLayer not working #1373
Comments
The arcgis module is not in good maintenance shape, it has been dumped on us by third parties and nobody amongst the code devs is familiar with it (it literally drives zero business hours). That said, maybe the issue is just a matter of whitelisting classes in XStream... Could you update the report and share the entire stack trace, rather than an excerpt of it? |
Thanks for your response, here is the complete stack trace: |
Hi All, in the 1.24.0 version the geowebcache.xml file does not have arcgisLayer configured inside the in parallel with , but it exists in 1.6.X version, after I added the , now I got exception:
Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: arcgisLayer
I do need the arcgisLayer for the map, it configured in the end inside layers tag in the geowebcache.xml as:
<arcgisLayer> <name>worldStreetMap</name> <tilingScheme>/app/geoserver/images/Basemap_World_Streetmap_2D/Layers/Conf.xml</tilingScheme> </arcgisLayer>
that caused the gwcXmlConfig bean creation failed and the geoserver admin UI not accessible with 503 HTTP error.
Any solution for this issue?
Thanks
The text was updated successfully, but these errors were encountered: