Hide Forgot
When you open JBDS and ask it to create new Drools runtime, you get a dialog that gives you two options: - Either you use your own runtime, perhaps one you've received from Red Hat in a BRMS package. - Or you have JBDS generate the runtime for you. There is nothing to talk about in the first case - that's what I've always done when I wanted to work with JBDS. The problem lies in the second case - because when you select it, you get a runtime based on the project binaries, not the product binaries. Also, this runtime is Drools 5.2, not Drools 5.3. Not that it matters, because it most probably won't be compatible with BRMS 5.3 anyway.
JBDS tends to work with the projects by default. The Getting Started documentation for BRMS instructs users to install the runtime from the BRMS packages they have downloaded. I'm not sure what else we could do about option number 2. Thanks Lee
The first case is definitely recommended, and afaik the documented strategy. For option 2, the Drools & jBPM Eclipse plugin that accompanies BRMS 5.3 is built from the same branches as the product, and thus contains the same jars as BRMS 5.3. So creating a runtime from the tooling should create a runtime compatible with BRMS 5.3 (not identical as it only contains a much smaller subset of all the jars). I'm adding the need_info flag on this, to request additional feedback whether anything actually should be changed, and if so what.
This issue is/will be resolved when we get the Drools JBDS plugins built directly by productization. Nothing we can do until then.
This issue's fixes have been picked by ER9. Please verify them on ER9.
Sorry, this is tools bug and it will only be availabe in SOA tools plugins. Revert the target milestone field.
Link to: JBDS-1898