-
Type:
Suggestion
-
Resolution: Won't Fix
-
None
-
Component/s: Core - Content REST APIs
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Bruce Krasnof reported this issue on the user list (http://confluence.atlassian.com/display/DOC/mail/186932). Perhaps we can customise our Axis WSDL to use a non-deprecated encoding
and remove the duplicate method names.
–
We're trying out Eclipse with XFire libraries for web services. I got an exception when using the XFire dynamic client with Confluence's remote soap api, I thought it was a bug in XFire but the developer of XFire says it's an issue with the wsdl file. It's minor, just an fyi for other folks trying out XFire. I think the problem is just the dynamic client approach, which maybe wasn't the best way anyways.
On 8/27/06, Dan Diephouse (JIRA) <jira@codehaus.org> wrote:
>
> [ http://jira.codehaus.org/browse/XFIRE-599?page=all ]
>
> Dan Diephouse closed XFIRE-599.
> -------------------------------
>
> Resolution: Won't Fix
>
> There are two problems with the confluence wsdl which make it non-basic
> profile conformant (see www.ws-i.org for more information about the Basic
> Profile - it is basically a standard which tells you how to build correct
> web services).
> 1. It uses RPC-Encoding which is deprecated
> 2. It has multiple operations with the same name, which isn't allowed in
> the basic profile.
>
> We may support these in the future, but I believe there are already issues
> for these.
- relates to
-
CONFCLOUD-6890 Make remote API WSDL work with XFire dynamic client
- Closed
-
CONFSERVER-3877 Overloaded methods in remote API break some SOAP toolkits
- Closed