Description of problem:
Python's xmlrpclib cannot decode ']]>' as a string parameter.

Character sequence ']]>' is not permitted to appear in content unless
used to mark the end of CDATA-Section. Usually there is no need to
escape the '>' character. But it really should be escaped in the case
of ']]>' sequence generate a valid xml.


How reproducible:
always

Steps to Reproduce:
1. send API XML-RPC request to Spacewalk server, respond should contain ']]>' sequence
  
Actual results:
[[snip]]
  File "/usr/lib/python2.6/xmlrpclib.py", line 1199, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python2.6/xmlrpclib.py", line 1489, in __request
    verbose=self.__verbose
  File "/usr/lib/python2.6/xmlrpclib.py", line 1253, in request
    return self._parse_response(h.getfile(), sock)
  File "/usr/lib/python2.6/xmlrpclib.py", line 1387, in _parse_response
    p.feed(response)
  File "/usr/lib/python2.6/xmlrpclib.py", line 601, in feed
    self._parser.Parse(data, 0)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 1, column 593

Expected results:
python xmlrpclib should parse respond w/o any problems

Additional info:
in request to server sequence ']]>' correctly escaped to ']]>', but in respond from server not. Looks like a bug in redstone XmlRpcSerializer.