Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: UDIG 1.2.RC3
    • Fix Version/s: UDIG 1.2.0
    • Component/s: webservices
    • Labels:
      None
    • Environment:
      Windows XP 32bit and GeoServer 2.0.2 (local)

      Description

      When you add a WMS layer to the map uDig sends the following to the server. GeoServer can't figure out the filter

      GET /geoserver/wms?FILTER=%3CFilter%2F%3E%29%3CFilter%2F%3E%29&SERVICE=WMS&LAYERS=sf%3Aarchsites,sf%3Aroads&EXCEPTIONS=application/vnd.ogc.se_xml&FORMAT=image/png8&HEIGHT=349&TRANSPARENT=TRUE&REQUEST=GetMap&BBOX=589434.8564686741,4914490.882968264,609527.2102150217,4926501.8980334345&WIDTH=583&STYLES=burg,simple_roads&SRS=EPSG:26713&VERSION
      =1.1.1

      While 1.1.1 sends GET
      /geoserver/wms?SERVICE=WMS&LAYERS=sf%3Aarchsites&EXCEPTIONS=application/vnd.ogc.se_xml&FORMAT=image/png&HEIGHT=335&TRANSPARENT=TRUE&REQUEST=GetMap&BBOX=-103.8725637911543,44.377511472651264,-103.63794182141925,44.48804280772808&WIDTH=712&STYLES=point&SRS=EPSG:4326&VERSION=1.1.1

      I have no idea why it is sending a blank filter there is no need for it.

        Activity

        Hide
        Jody Garnett added a comment -
        That was my bad; I added a Filter user interface which was using Filter.INCLUDES by default; and the WMS code blindly sent that out.
        Show
        Jody Garnett added a comment - That was my bad; I added a Filter user interface which was using Filter.INCLUDES by default; and the WMS code blindly sent that out.

          People

          • Assignee:
            Jody Garnett
            Reporter:
            Ian Turton
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: