Sounds good, thanks .

Hi Bob,

You make a fair point. We agree this would be better for the community if this breaking API change was reverted. Further, we noticed that the corresponding change of pageId -> commentOwnerId was not made for our RPC API so this would make sense for the sake of consistency.

This revert is estimated to ship with Confluence 4.1.3 (as Confluence 4.1.2 just went out the door). We ask for your patience in the mean time.

Cheers,
Dave

Hmmm... you are more of an expert on the internals than I am. However, I have always used Confluence (and JIRA for that matter) wsdl without modification and it has always worked across multiple releases with the obvious exceptions of new capabilities. For instance 4.0 wsdl against 3.x releases (3.1 - 3.5) and 4.0 introduced significant changes. So, I don't understand how that has worked over the last 6 years without running into this issue . I suppose I don't know for sure though that any new fields/getters/setters were added either. Perhaps there were no fields addedMy other question would be then is why not revert the whole change and leave it totally compatible with previous release? The change added no new capability and I thought SOAP API improvements were minimal at this point (not that I agree with that mind you). I can certainly look into fudging the wsdl too.

No. The problem is not with the renaming of the field. Introducing the accessors getCommentOwnerId() and setCommentOwnerId() is sufficient to cause the problem. This is because Introspector.getBeanInfo(RemoteComment.class) will acknowledge "commentOwnerId" as a property. As such this property will get written out to the SOAP complex type and appear in the WSDL.

If you want to use the remote beans in the com.atlassian.confluence.rpc.soap package in your client, you must be using the WSDL for the same version of Confluence.

If you want your confluence-CLI client to work with an older version of Confluence with an old WSDL, then you will need to introduce your own beans that are compatible with the WSDL of the version you communicating with. I noticed you have already have some generated beans in the package org.swift.common.soap.confluence).

Dave, the code is at https://bitbucket.org/bob_swift/confluence-cli. The specific location is 1255. The problem isn't with using pageId, the problem is the compatibility in using it with client/server being at different levels with the respective errors. There was no need to change the underlying name which i think is the heart of the problem. Just adding the new methods would have served the same purpose without breaking this use case.

Bob,

If you want backwards compatibility, why not just continue using "pageId"?

Extract from the 4.1 WSDL:

   <complexType name="RemoteComment">
    <sequence>
     <element name="commentOwnerId" type="xsd:long"/>
     <element name="content" nillable="true" type="xsd:string"/>
     <element name="created" nillable="true" type="xsd:dateTime"/>
     <element name="creator" nillable="true" type="xsd:string"/>
     <element name="id" type="xsd:long"/>
     <element name="modified" nillable="true" type="xsd:dateTime"/>
     <element name="modifier" nillable="true" type="xsd:string"/>
     <element name="pageId" type="xsd:long"/>
     <element name="parentId" type="xsd:long"/>
     <element name="title" nillable="true" type="xsd:string"/>
     <element name="url" nillable="true" type="xsd:string"/>
    </sequence>
   </complexType>

"pageId" is very much still there. We did rename the field in RemoteComment, but the accessors for getPageId() and setPageId() are very much there (just deprecated).

Failing this, can you please provide the actual code containing the soap request and a fuller stack trace.

No, Confluence CLI is based on SOAP.

Hi Bob,

Are you able to use the RPC (non soap) version of the call instead?