2 replies [Last post]
happy.madness
Offline
Joined: 2012-01-22

Hi everybody

Can't tell if this is the right place to post the content below but I haven't found any section dedicated to the Docmosis REST interface and placing this under Java seems unappropriate.

I have tried to request document rendering using the REST interface invoked via some Ruby code.

A few weeks ago I was able to have the request be honoured but lately I have "400 Bad Request" errors returned by the REST client.

Is somebody else here using the REST interface as well and have you experienced similar issues?

I can post the Ruby code that has been used as well.

Generally speaking the documentation is quite sparse and it takes a lot of guessing to figure out how to use the REST interface, which is a shame since a proper documentation of the REST interface would actually allow interoperability and decoupling from a specific programming language.

I hope that the community can provide some answers since I like the positioning of the Docmosis product offering.

A question on the stand alone Docmosis solution: does it also offer REST interfaces as well or is the REST interface only proposed for the "on demand" product offering?

Looking forward to hearing from you.

Regards.

alienisty
Offline
Joined: 2012-01-25
Ruby example

Hello happy.madness,
An example for Ruby has been added to the code samples section (http://www.docmosis.com/code-samples).
The example is well commented, so it should be easy to follow and understand.

Make sure you keep the print out instructions for the response contents from the Docmosis service since, if the client request gets that far, Docmosis will be giving you a Docmosis-specific error message (comments about error code classes are also reported in the case block in the response handling block).

I hope this helps.

Regards

happy.madness
Offline
Joined: 2012-01-22
Thanks

Hi alienisty

Thank you for publishing a Ruby code snippet aiming at highlighting the use of the REST API with RestClient.

This will also benefit other users who may have been facing the same "getting started" issues that I was encountering.

This surely helps to explore further the Docmosis solution in my case.

Regards.