Hi,
I am trying to make use of a live non-cached DI connection to consume a WFS services served by geoserver. The data displays in arcmap fine, and using fiddler to monitor the HTTP traffic, I can see the live http requests and responses as I pan and zoom the map. However, viewing the attribute table, or other operations such as select by rectangle are not working. Looking at the requests and responses with fiddler, the problem seems to be with the format of the filter xml embedded by arc10/DI within the request.
Arc/DI is embedding something like this:
<ogc:Filter>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>SomeProperty</PropertyName>
<ogc:Literal>100</Literal>
</ogc:PropertyIsEqualTo>
<ogc:/Filter>
The server is failing to parse this filter xml.
When I manually edit the xml in the requests within fiddler to this (ie drop the ogc namespace)
<Filter>
<PropertyIsEqualTo>
<PropertyName>SomeProperty</PropertyName>
<Literal>100</Literal>
</PropertyIsEqualTo>
</Filter>
the server understands the request and send the feature gml back.
Is this is a bug on the Arc/DI side?
I am trying to make use of a live non-cached DI connection to consume a WFS services served by geoserver. The data displays in arcmap fine, and using fiddler to monitor the HTTP traffic, I can see the live http requests and responses as I pan and zoom the map. However, viewing the attribute table, or other operations such as select by rectangle are not working. Looking at the requests and responses with fiddler, the problem seems to be with the format of the filter xml embedded by arc10/DI within the request.
Arc/DI is embedding something like this:
<ogc:Filter>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>SomeProperty</PropertyName>
<ogc:Literal>100</Literal>
</ogc:PropertyIsEqualTo>
<ogc:/Filter>
The server is failing to parse this filter xml.
When I manually edit the xml in the requests within fiddler to this (ie drop the ogc namespace)
<Filter>
<PropertyIsEqualTo>
<PropertyName>SomeProperty</PropertyName>
<Literal>100</Literal>
</PropertyIsEqualTo>
</Filter>
the server understands the request and send the feature gml back.
Is this is a bug on the Arc/DI side?