Migrating a plugin from AttachmentManager API to AttachmentService API

Frank Blankenburg

Hi.

I wrote a plugin which manages page attachments via the AttachmentManager API . After upgrading to Confluence version 7.15, I do have various problems with that including large a amount of accumulating open file handles during the day. I suspect this API being deprecated/legacy now might be related to this.

So I would like to migrate the plugin to API version 7.15 and use the AttachmentService API  instead. But I cannot find examples of how to use this API and perform basic tasks like read the attachment data as string, setting the attachment creator, ... except from some githib projects addressing parts to these topics only.

Is there a practical guide of how to use the AttachmentService API or even a document describing the migration process ?

Alternatively, an example of how to read the attachment content data into a byte array or a string via JAVA using this new API would be of great benefit for me.

Thank you very much.

Frank Blankenburg

Ok, some corrections: The error described above has not been caused by the deprecated AttachmentManager API. Instead, some InputStream objects had not been closed after use and some behavior behind the scenes changed so that this led to accumulating handles after the update to 7.15 only. Maybe some internal caching or changes in the garbage collection, but ultimately my fault here (always close your streams).

Nevertheless, having a hint to some AttachmentService API documentation would be helpful.