If you have a Bonita BPM project in production, or are planning to deploy one, you may have considered an upgrade to a Bonita BPM subscription for the professional support and greater flexibility, scalability and integration capabilities. But, how easy is that upgrade going to be?
Bonitasoft is doing a series of webinars to show how it easy to switch from our Community edition to our Subscription edition, with minimal downtime and no data loss.
Everyone is already aware of the Automated Error Reporter Tool - and if you're not I invite you to check one of these articles: reason of this project, InfoQ interwiew. The excellent news is that it is shipped by default in Eclipse Mars. Each time a stacktrace is logged, you can easily report the error with details by clicking View Details in notification popup.
Should the meta files related to an IDE be committed?
There is a never-ending fight over this question. I'm sure that most of the advanced Eclipse users will answer yes but unfortunately in a team you might get some Eclipse haters (and sometimes even IDE haters, who I also call last-century coders). This second and third categories will answer no.
"Software developers can be heroes. They alone have the power to create vital business solutions that the rest of the organization needs to succeed. Given the right tools, any developer can transform into a developer hero, saving the day and pushing the organization to a new level of productivity." – Miguel Valdes Faura
A Community translation tool for Bonita BPM is available. Currently, only languages with a very high rate of translation completion are integrated in the product itself. It was the case recently with Russian.
I came across a strange issue with manipulating SWTBotTree, and it took me few hours to find a workaround. I found no exact match with my issue during my research, so let's keep a trace here while waiting for a better understanding of the issue and a fix in SWTBot.
In a SWTBot Test, calls to SWTBotTreeItem.contextMenu() or SWTBotTreeItem.select() might lead to the following exception:
Caused by: java.lang.IllegalArgumentException: Argument not valid
Quite an obscure message... what is happening? How can I solve my issue?
Easily applicable - but hard to guess - the workaround consists of simply calling SWTBotTree.setFocus() before manipulating the SWTBotTree.
final SWTBotTree tree = bot.tree();
final SWTBotTreeItem cssNodeFile = tree.expandNode("application", "css", "bonita_form_confirm.css");
I discovered a new issue since my last post about Target Platform migration from Eclipse 4.3 to 4.4.1. It concerns a behavior modification in Datatools API which broke our integration of the Datatools Graphical Designer.