If you’re experiencing the posted problem using jpython 2.5.1 with pyamf and Tomcat 6, you’ll need to either patch 2.5.1 or upgrade to 2.5.2b1 or higher. Addition information about the problem and the patch can be found here.
Additional error information follows:
Traceback (most recent call last):
File “__pyclasspath__/pyamf/remoting/gateway/wsgi.py”, line 84, in __call__
File “__pyclasspath__/pyamf/remoting/__init__.py”, line 663, in decode
File “__pyclasspath__/pyamf/remoting/__init__.py”, line 475, in _read_body
File “__pyclasspath__/pyamf/remoting/__init__.py”, line 452, in _read_args
File “__pyclasspath__/pyamf/__init__$py.class”, line 901, in readElement
File “__pyclasspath__/pyamf/__init__$py.class”, line 901, in readElement
File “__pyclasspath__/pyamf/amf0$py.class”, line 298, in readAMF3
File “__pyclasspath__/pyamf/__init__$py.class”, line 1354, in get_context
File “__pyclasspath__/pyamf/__init__$py.class”, line 1374, in _get_context_class
File “__pyclasspath__/pyamf/amf3$py.class”, line 32, in
File “__pyclasspath__/pyamf/flex/__init__$py.class”, line 269, in
File “__pyclasspath__/pyamf/__init__$py.class”, line 1705, in register_package
File “__pyclasspath__/pyamf/__init__$py.class”, line 1670, in
AttributeError: ‘stringmap’ object has no attribute ‘pyamf’