REST API vs Java API

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2016 09:32 AM
Hi all
I'm pretty new to BPM and Activiti and am currently investigating how we might integrate Activiti into a new project we're building. Can anyone offer any guidance on the pros and cons of using the the REST API over the Java API?
Does the REST API simply wrap the Java API?
Thanks in advance for your advice.
Matt
I'm pretty new to BPM and Activiti and am currently investigating how we might integrate Activiti into a new project we're building. Can anyone offer any guidance on the pros and cons of using the the REST API over the Java API?
Does the REST API simply wrap the Java API?
Thanks in advance for your advice.
Matt
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2016 11:32 AM
Hi Matthew,
I would say that it really depends what you are trying to achieve.
The point of using Activiti REST API is making your BPM engine interoperable.
Since REST leverages the HTTP protocol and its methods and resources you can start processes in Activiti from any other applications.
You can also build a mobile app or a custom UI interface and have your logic handled by Activiti.
I don't see any advantage of using the Java API unless you want to embed Activiti into a Java application.
That's just a thought.
I hope I helped.
Jorge
I would say that it really depends what you are trying to achieve.
The point of using Activiti REST API is making your BPM engine interoperable.
Since REST leverages the HTTP protocol and its methods and resources you can start processes in Activiti from any other applications.
You can also build a mobile app or a custom UI interface and have your logic handled by Activiti.
I don't see any advantage of using the Java API unless you want to embed Activiti into a Java application.
That's just a thought.
I hope I helped.
Jorge
