1 of 1 people found this helpful
if you want to contribute with some code or improvement you can fork the jbpm repository and create your jira issues explaning your new features and then create a pull request from your fork to the master repository.
Thanks for the help.
But I still have some doubts regarding the REST interface:
1. Is it really the bpm-console project that I should be targeting for the enhancement of the REST services?
2. if so, do you know how active is that project? I have seen that no changes have been made since 10 November 2010.
3. How do I test the changes that I have made with my jbpm project?
I'm not in so into the UIs and the rest server but I'm pretty sure that the rest server is located here:
More concrete the project: jbpm-gwt-console-server expose the rest endpoints to interact.
The logic of that services is coded inside jbpm-gwt-core project.
You should be able to fork that and create the appropriate tests to test your proposed functionality.
If you clone all the project you will be able to change the UIs and the server to test your functionality, but Unit Tests are always reuqired (Junit)
I have been looking into to the jbpm-gwt-core and I did not find anything.
The fact is that in the jbpm-gwt-console-server project, there is in the target folder tree structure with some java classes that are the ones that define the REST interface. They are in,
Now the problem is that because they are in the target they are getting rebuilt.
I have looked everywhere in the jbpm-gwt project and I have not been able to identify where these files are coming from.
Doing some research, folliwing some pom files and asking in the IRC channel I've found that the source code that you are looking for is being kept outside of the jbpm repository and can be found here: