Scale denominators gets wiped out

[oyvindi]

First: getting the same issue as #165, so tried editing the XML manually.

Pasting this XML (no validation errors):

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<StyledLayerDescriptor version="1.0.0" xsi:schemaLocation="http://www.opengis.net/sld StyledLayerDescriptor.xsd" xmlns="http://www.opengis.net/sld" xmlns:ogc="http://www.opengis.net/ogc" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:se="http://www.opengis.net/se">
  <NamedLayer>
    <Name/>
    <UserStyle>
      <Name/>
      <Title/>
      <FeatureTypeStyle>
        <Rule>
          <Name>Avløp felles ledning</Name>
          <Filter xmlns="http://www.opengis.net/ogc">
            <PropertyIsEqualTo>
              <PropertyName>FCODE</PropertyName>
              <Literal>AF</Literal>
            </PropertyIsEqualTo>
          </Filter>
          <MinScaleDenominator>101</MinScaleDenominator>
          <MaxScaleDenominator>2000</MaxScaleDenominator>
          <LineSymbolizer>
            <Stroke>
              <CssParameter name="stroke">#FFB900</CssParameter>
              <CssParameter name="stroke-width">1</CssParameter>
              <CssParameter name="stroke-linecap">round</CssParameter>
            </Stroke>
          </LineSymbolizer>
          <LineSymbolizer>
            <Stroke>
              <CssParameter name="stroke">#FF0000</CssParameter>
              <CssParameter name="stroke-width">0.5</CssParameter>
              <CssParameter name="stroke-opacity">1</CssParameter>
              <CssParameter name="stroke-linecap">round</CssParameter>
            </Stroke>
          </LineSymbolizer>
        </Rule>
      </FeatureTypeStyle>
    </UserStyle>
  </NamedLayer>
</StyledLayerDescriptor>

..makes the style entry appear in the list, but the min/max scale input boxes are empty:

Saving the style, and I get this in the console output:

java.lang.RuntimeException: org.xml.sax.SAXParseException; lineNumber: 10; columnNumber: 20; Invalid byte 1 of 1-byte UTF-8 sequence.
        at org.geotools.xml.styling.SLDParser.parseSLD(SLDParser.java:473)
        at org.geoserver.catalog.SLDHandler.parse10(SLDHandler.java:173)
        at org.geoserver.catalog.SLDHandler.parse(SLDHandler.java:155)
        at org.geoserver.config.GeoServerDataDirectory.parsedSld(GeoServerDataDirectory.java:725)
        at org.geoserver.config.GeoServerDataDirectory.parsedStyle(GeoServerDataDirectory.java:737)
        at org.geoserver.catalog.ResourcePool.createStyle(ResourcePool.java:2135)
        at org.geoserver.catalog.ResourcePool.getStyle(ResourcePool.java:2116)
        at org.geoserver.catalog.impl.StyleInfoImpl.getStyle(StyleInfoImpl.java:132)
        at jdk.internal.reflect.GeneratedMethodAccessor194.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:569)
        at org.geoserver.catalog.impl.ModificationProxy.invoke(ModificationProxy.java:152)
        at jdk.proxy3/jdk.proxy3.$Proxy50.getStyle(Unknown Source)
        at org.geoserver.wms.WMS.getStyleByName(WMS.java:268)
        at org.geoserver.wms.map.GetMapKvpRequestReader.parseStyle(GetMapKvpRequestReader.java:1573)
       (truncated)

Under "Layer Preview", I get this:

Using GeoServer 2.28.0, with the last version of this plugin.

[dnlkoch]

Thanks @oyvindi for your report!

I checked your example SLD and can confirm that the denominators aren't reflected in the UI. Strangely this is working in the standalone GeoStyler demo, so I assume it's a bug solely in the integration plugin of GeoStyler that needs to be fixed.

Although I was unable to reproduce the RuntimeException error in my environment (also GeoServer 2.28.0 via Docker and the latest GeoStyler plugin version), it seems to be related to the special character ø in the rule name (lineNumber: 10; columnNumber: 20) and I suspect that the encoding settings in Tomcat are probably missing. Please check if the following startup parameters are set:

-Dfile.encoding=UTF-8
-Djavax.servlet.request.encoding=UTF-8
-Djavax.servlet.response.encoding=UTF-8

And also double check that the document is actually saved and pasted in UTF-8 as well.

[oyvindi]

I'm using the default settings in Geoserver, so the default encodings aren't tampered with. I copied the XML from an editor that has the encoding set to UTF-8.

GeoServer reads & validates it though, also works in the preview after removing this plugin.

Also works for me on the demo page...

This was 3 days ago, so can't 100% rule out that something in my workflow messed up the encoding, e.g copy/paste, but I think I pretty much did the same now.