topic XMLStreamException calling REST deployments/{depID}/resources in Alfresco Archive

XMLStreamException calling REST deployments/{depID}/resources

joeysr20det — Thu, 07 Aug 2014 20:54:22 GMT

I'm making a REST call to get the resources of a deployment in the repository. I have success calling:http://mouse:8084/activiti-rest/service/repository/deployments/1506to get the deployment info, but when I call:http://mouse:8084/activiti-rest/service/repository/deployments/1506/resourcesI get a HT

Re: XMLStreamException calling REST deployments/{depID}/resources

jbarrez — Tue, 19 Aug 2014 08:55:48 GMT

5.16 didn't have much changes in the rest API. But you say the very same call is working on 5.15?

Re: XMLStreamException calling REST deployments/{depID}/resources

joeysr20det — Tue, 19 Aug 2014 15:16:43 GMT

Yes that's right. I don't know whats changed. I'm pretty familiar with your source code and design and couldn't find any noticeable changes from 5.15 to 5.16 with respect to REST.

However, the Accept: application/json HTTP header solves this issue for sure. I've done a great deal of searching and it's highly recommended to specify the Accept header to identify the HTTP response format you expect to receive as the client. I read from a lot of JSON people that there are so many subtle differences at the transport layer from platform to plaform, version to version, etc…. that they just always make sure to use the header. It might be a good idea to throw this in the beginning of the REST section of the user manual.

Keep up the good work. The Activiti is doing a great job. I've worked with many workflow engines and like yours the best by far.

Re: XMLStreamException calling REST deployments/{depID}/resources

jbarrez — Wed, 20 Aug 2014 20:00:14 GMT

That is indeed odd that suddenly these headers are needed.
I added it to the userguide: https://github.com/Activiti/Activiti/commit/abdc39bf386588e71579b9b933c0fd82798a1047

Thanks. And thanks for the positive feedback 🙂