Just hit this bug on 5.7.5 ( is it still supported? ). Please, add this version to the list of affected versions and reopen it if v5.7.5 is still supported.

buysellbewell, pmullercfm, thank you for workaround, it worked for me!

I am currently using Atlassian Confluence 5.6.1. It looks like the fix above needs to be modified as follows (you need to pass ignore_ext=None):

def confluence_soap_parser(xml_str, rules=None, ignore_ext=None, parser=SOAPpy.Parser._parseSOAP):
    attribute = 'xsi:type="soapenc:Array"'
    xml_str = xml_str.replace('%s %s' % (attribute, attribute), attribute)
    return parser(xml_str, rules=rules)

SOAPpy.Parser._parseSOAP = confluence_soap_parser

After some investigation with one of my colleague, we determined that the "duplicate attribute" error comes from expat itself. For example, if you invoke the getSpaces method, Confluence sends a bogus XML response containing the xsi:type attribute twice in the getSpacesReturn element :

<getSpacesReturn soapenc:arrayType="ns2:RemoteSpaceSummary[8]" xsi:type="soapenc:Array" xsi:type="soapenc:Array" xmlns:ns2="http://beans.soap.rpc.confluence.atlassian.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

The issue really looks like the one which affected JIRA almost 5 years ago : JRA-7321.
This one was fixed in a few weeks. What's so different there? Why doesn't Atlassian already fixed it?

Waiting for an official answer, here is a quick and dirty fix for Python users :

def confluence_soap_parser(xml_str, rules=None, parser=SOAPpy.Parser._parseSOAP):
    attribute = 'xsi:type="soapenc:Array"'
    xml_str = xml_str.replace('%s %s' % (attribute, attribute), attribute)
    return parser(xml_str, rules=rules)

SOAPpy.Parser._parseSOAP = confluence_soap_parser

Hi Greg,

Unfortunately it is unlikely that this bug will be fixed soon. We try to prioritise issues according to their severity, impact, number of customers affected, availability of a work around and number of votes. There is always a huge bucket of issues and we try to fix those that have higher priority. This issue has not yet made it to the top of 'fix for' list. Also, at this point we try to prioritise work on REST API (the first glimpse of it will be available in 3.1) above any work on SOAP or XML-RPC.

Please comment/vote if you disagree and think that it should be fixed soon.

Anatoli.

No support for Unicode in the remote API is a serious issue. I hope this will be addressed soon. XML-RPC works fine however the fact that it doesn't support Unicode characters is a serious drawback. The SOAP API would be the solution.

-Greg

Unfortunately this issue is still not scheduled for a fix. This is a reasonably complex issue and is not currently considered to be one of the highest priority bugs to fix at this point in time.
If we receive more votes on this issue, we will consider scheduling at some point in the near future.

Cheers,
Andrew Lynch

still not fixed? I get the same problem On Confluence 2.7.1 using Perl's SOAP::Lite (which in turn uses XML::Parser) - same error. Specifically, the getSpaces call returns this chunk:

<getSpacesReturn
  soapenc:arrayType="ns2:RemoteSpaceSummary[138]"
  xsi:type="soapenc:Array" 
  xsi:type="soapenc:Array" 
  xmlns:ns2="http://beans.soap.rpc.confluence.atlassian.com" 
  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" 
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

I wonder if this will get fixed in 4.5 weeks, or if we need to buy birthday presents for CONF-6720 :o

Thanks for the update on this issue. We'll try and address as soon as we can.

In the mean-time, it may be worth looking to the forums for advice - http://forums.atlassian.com/index.jspa

I had nearly identical code before encountering the error and finding Boris' bug report. I observe the same errors with a similar stack trace (due to the version difference).

Using Confluence 2.6, python 2.5.1, soappy 0.11.3 (ubuntu). Is there any resolution, or might there be an error in how we try to access the information?

I would really like to export all spaces for backup purposes and I'd prefer SOAP over XML-RPC.