Bug 1015097 - redirection to Phreak when reteoo JAR not found
redirection to Phreak when reteoo JAR not found
Status: CLOSED WONTFIX
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: BRE (Show other bugs)
6.0.0
All All
low Severity low
: ---
: ---
Assigned To: Edson Tirelli
Lukáš Petrovický
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-03 08:55 EDT by Richard Bourner
Modified: 2013-12-16 12:15 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-12-16 12:15:45 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Richard Bourner 2013-10-03 08:55:49 EDT
Description of problem:
When the reteeoo JAR file is forgotten, a redirection to Phreak algorith is performed. 
The following message can be found in the log:
[WARN - org.drools.core.RuleBaseConfiguration.getComponentFactory(RuleBaseConfiguration.java:910)] Cannot find drools-reteoo.jar on the classpath, switching to phreak 

It might be interesting to be notified in a more visible way, either as an error, or an exception so that it is more obvious that RETE cannot be used in that scenario.


Version-Release number of selected component (if applicable):
6.0.0.CR4

How reproducible:
Omit to add reteoo dependency in the POM and set the engine in RETE mode.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Edson Tirelli 2013-12-16 12:15:45 EST
Richard,

This is an error that only makes sense to sysadmins and developers. I believe showing any message about this subject to users will not help in any way. The actual algorithm choice should be transparent to users. 

Our understanding is that the current approach of presenting a log warning is the right way to go. 

If you have any other suggestions, feel free to re-open this ticket, but I will close it for now.

Note You need to log in before you can comment on or make changes to this bug.