Hide Forgot
++ This bug is a clone of bug 780612 ++ project_key: SOA The problem looks like that JBDS 4 requires/assumes a Drools 5 runtime. The new Drools project references api elements that did not exist before Drools 5 - such as: org.drools.KnowledgeBase
Link: Added: This issue is a dependency of JBDS-1643
When creating a new Drools project, you can set code compatibility (last page of the wizard, in this case set to 4.x). I just tested and I was able to generate and execute the hello world process for Drools 4.x on a Drools 4.0.7 runtime using the latest Drools plugin.
Thanks Kris, Selecting the Drools 4 option solves that problem - I'm now seeing > 70 Warnings such as this for the example project: Discouraged access: The type Package is not accessible due to restriction on required library /opt/local/51_GA/jboss-soa-p-5/jboss-as/server/production/deploy/jbrules.esb/drools-core-5.1.0.BRMS.jar What is the restriction on the library? Are these caused by the examples using internal (Pre-5.1) API calls? (http://lists.jboss.org/pipermail/rules-users/2009-June/009242.html)
These warnings are indeed generated, as we introduced a new API in Drools 5.0 (as defined in drools-api). We discourage access to the internal API using these warnings. You can however turn them off if you want to (for example if you use drools4) in Drools preferences (Windows - Preferences and then under Drools set internal classes to accessible).
Thanks Kris - this is not a critical bug then - but, we should document this for the users.
Isaac, how do we need to go about getting this into the SOA-P 5.2 readme?
Brian - It needs to be assigned to the writer for SOA-P so he is aware of this issue. David, this is why I am assigning it to you ;)
Release Notes Docs Status: Added: Documented as Known Issue Writer: Added: dlesage Release Notes Text: Added: Users may encounter warning messages if the set Rules project code compatibility to JBoss Rules 4.x. These are caused by examples that use pre-5.x API calls and are intended to discourage users from accessing the internal API. If, however, you do need to access the API, you can turn them off by going to Windows - Preferences - JBoss Rules and setting the set internal classes to accessible.
Release note created to document this issue.
Release Notes Text: Removed: Users may encounter warning messages if the set Rules project code compatibility to JBoss Rules 4.x. These are caused by examples that use pre-5.x API calls and are intended to discourage users from accessing the internal API. If, however, you do need to access the API, you can turn them off by going to Windows - Preferences - JBoss Rules and setting the set internal classes to accessible. Added: https://issues.jboss.org/browse/SOA-3051 Users may encounter warning messages if the set Rules project code compatibility to JBoss Rules 4.x. These are caused by examples that use pre-5.x API calls and are intended to discourage users from accessing the internal API. If, however, you do need to access the API, you can turn them off by going to Windows - Preferences - JBoss Rules and setting the set internal classes to accessible.
LOL - Helps if I check them in. ;-)
Verified in the doc here: https://svn.devel.redhat.com/repos/ecs/JBoss_SOA_Platform/trunk/5/5.2.0_Release_Notes/en-US/SOA_Known_Issues.xml