PROBLEM

An ArcXML request posted to the Servlet Connector through an HTML form fails to work

Last Published: April 25, 2020

Description

** Internal Publish Only! This article may contain information that is not intended for external circulation. **

In ArcIMS 3.1, an ArcXML request posted to the Servlet Connector through an HTML Viewer fails to work.PLEASE PROVIDE FEEDBACK TO THE ArcIMS MIDDLEWARE TEAM VIA CQ00137440. WE NEED YOUR FEEDBACK TO FINE TUNE THIS ISSUE FOR FINAL.

Cause

The Servlet Connector may use one of two methods for processing: InputStream (default), or getParameter. The method to use depends upon the locale, web server, and Servlet Engine. If one method doesn't work, the other method might.

Solution or Workaround



The method may be changed by entering the useCustomProcessing property to the Esrimap_prop file: useCustomProcessing=true (uses InputStream method)
useCustomProcessing=false (uses getParameter method)

See the test matrix below for scenarios in which these methods work and do not work.

Test matrix for multi-byte characters in ArcXML request

IS: InputStream
GP: getParameter

Encoding refers to the value of encoding in arcXML.js and htm pages.

Locale Web server–Servlet engine configuration

(Encoding) IIS-Jrun IIS-ServletExec IPlanet Apache/Tomcat
English IS (ok) IS (ok) IS (ok) IS (ok)
(default UTF-8) GP (ok) GP (ok) GP (ok) GP (ok)
Trad Chinese IS (ok) IS (ok) IS (ok) IS (ok)
(Big5) GP (not ok) GP (not ok) GP (ok) GP (not ok)
Simplified Chinese IS (ok) IS (ok) IS (ok) IS (ok)
(GB2312) GP (not ok) GP (not ok) GP (ok) GP (not ok)
Japanese IS (ok) IS (ok) IS (ok) IS (ok)
(shift_jis) GP (not ok) GP (not ok) GP (ok) GP (not ok)

Article ID:000002652

Software:
  • Legacy Products

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options

Discover more on this topic