Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

XML RPC functionality deprecated in newest version of Confluence?

Ian Mason January 10, 2015

We have a plugin that used an XML RPC call functionality that is no longer working upon upgrading to version 5.6.5. I notice that an add on called Confluence XML-RPC Java Client - Plugin that was present in our previous version (5.1.3) but not in 5.6. Does Confluence no longer support these types of calls? I know the movement is toward REST, but we are hoping to restore this functionality while we rewrite our tool, if that makes sense. 

3 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Ian Mason January 11, 2015

It's hard to tell from the log. We are facing two issues. Some of the calls made are no longer working, including the following: confluence.spacePermissionsFilter.getPermittedSpaceKeysForUserNotInAnyGroup confluence.spacePermissionsFilter.getPermittedSpaceKeysForUser confluence.spacePermissionsFilter.getPermittedSpaceKeysForAnonymousUser I'm not sure if these calls are not being made because Atlassian no longer supports these XML RPC calls. The other problem may be the schema change now uses user keys instead of user names, so these calls may need to be rewritten to use a user key instead of username. https://developer.atlassian.com/display/CONFDEV/Renamable+Users+in+Confluence+5.2 The error returned looks something like: date username IP address - CustomTools.addWikiSite java.lang.Exception: java.lang.IllegalArgumentException: Parameter username does not exist as a named parameter in [ select distinct space.key from SpacePermission as perm inner join perm.space as space where (perm.userSubject = :user or perm.group in (:groups) or (perm.userSubject is null and perm.group is null)) and (perm.type = :permission) ]

0 votes
Alejandro Conde Carrillo
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 10, 2015

I am afraid it has been deprecated since Confluence 5.5. It has been replaced by (the long awaited) REST API. More info in Confluence REST API.

Ian Mason January 11, 2015

Hi Alex, will calls to XML RPC no longer work as of 5.5? We make calls to the following in the our plugin: confluence.spacePermissionsFilter.getPermittedSpaceKeysForUserNotInAnyGroup confluence.spacePermissionsFilter.getPermittedSpaceKeysForUser confluence.spacePermissionsFilter.getPermittedSpaceKeysForAnonymousUser

Davin Studer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 12, 2015

The way I read the deprecation announcement is simply that they are not going to add new features to it. My understanding is that they will keep it around, but new work will be put into the REST API. As of yet the REST API cannot do everything that the other API's can so it would be foolish for them to get rid of it.

0 votes
Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 10, 2015

Have not used the XML-RPC recently, but in configuration options there is a parameter to enable remote API, and it is called "Remote API (XML-RPC & SOAP)". What type of error you are facing? Exception stracktrace to share, may be?

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

TAGS
AUG Leaders

Atlassian Community Events