[#CONF-10235] Confluence 2.7 SOAP API is broken

Confluence

Confluence 2.7 SOAP API is broken

Created: 13/Dec/07 12:35 AM Updated: 03/Jan/08 09:43 PM

Component/s:

Remote API (SOAP & XML-RPC)

Affects Version/s:

2.7

Fix Version/s:

2.7.1

Time Tracking:

Not Specified

File Attachments:

CONF-10235.patch (0.7 kB)
2.

ConfluenceAxisSoapService.class (1 kB)

Issue Links:

Cause

This issue is caused by:

~~CONF-9743~~ RPC plugins cannot be loaded dynamically

Participants:	Christopher Owen [Atlassian], Igor Minar, Ming Giet Chong [Atlassian] and Richard Scott
Since last comment:	36 weeks, 2 days ago
Resolution Date:	13/Dec/07 11:06 PM
Labels:

Description

« Hide

Confluence version 2.7 SOAP API is broken.

To reproduce this issue, simply access http://confluence.atlassian.com/rpc/soap-axis/confluenceservice-v1?wsdl and the error exception shown as following:

AXIS error

Sorry, something seems to have gone wrong... here are the details:

Fault - ; nested exception is: 
	java.lang.ClassCastException: java.lang.Class

AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: java.lang.ClassCastException: java.lang.Class
 faultActor: 
 faultNode: 
 faultDetail: 
	{http://xml.apache.org/axis/}hostname:test

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Christopher Owen [Atlassian] added a comment - 13/Dec/07 07:32 PM

Change to return type of SoapModuleDescriptor::getPublishedInterface() has broken this. No strong typing involved as return value is just placed into a generic object map by Axis to be cast to required type later. Very crap API. Our SOAP integration testing also appears to be crap - we need to do a get on the WSDL and make sure that the result is 200 OK (at the very least)

[ Permlink | « Hide ]

Richard Scott added a comment - 14/Dec/07 10:08 AM - edited

Status shows this is resolved in 2.7.1. When will 2.7.1 be released. This is a critical problem for us. We got everything up under 2.7 and now have found out that the critical remote access components don't work at all. It no eta, is there a workaround.

[ Permlink | « Hide ]

Christopher Owen [Atlassian] added a comment - 16/Dec/07 05:30 PM

Patched ConfluenceAxisSoapService.class

[ Permlink | « Hide ]

Christopher Owen [Atlassian] added a comment - 16/Dec/07 05:33 PM

Hi Richard,

I've attached a patched version of the soap service to this issue which will resolve the problem.

Create directories to form the following path in your Confluence installation:

confluence/WEB-INF/classes/com/atlassian/confluence/rpc/soap

and copy the attached class (ConfluenceAxisSoapService.class) to that directory.

Restart Confluence and the SOAP service will be restored.

Please let me know if you have any further issues.

[ Permlink | « Hide ]

Christopher Owen [Atlassian] added a comment - 16/Dec/07 05:43 PM

Diff for this patch

[ Permlink | « Hide ]

Christopher Owen [Atlassian] added a comment - 16/Dec/07 05:45 PM

For anyone else having to diagnose faults in the AXIS SOAP server I've modified the service to spit out stack traces when confluence.devmode is enabled.

In production mode, AXIS won't generate any stack traces making it near impossible to track down problems in the service.

[ Permlink | « Hide ]

Igor Minar added a comment - 19/Dec/07 02:05 PM

Thanks Chris for providing the raw patch as well!