Bug 781005 (SOA-3483) - Drools runtime definition must reference ${SOA-P 5.0} top-level directory, not the ${SOA-P 5.0}/jboss-as/server/default/deploy/jbrules.esb
Summary: Drools runtime definition must reference ${SOA-P 5.0} top-level directory, no...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3483
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation, JBoss Rules, Examples
Version: 5.2.0.ER5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.2.0 GA
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-13 20:17 UTC by Len DiMaggio
Modified: 2011-11-29 02:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
SOA-P 5.2.0.ER5 JBDS 4.1.1 Version: 4.1.1.M2 Build id: v20111006-0040-H1061-M2 Build date: 20111006-0040
Last Closed: 2011-11-29 02:59:33 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 781009 0 urgent CLOSED Different versions of Drools-related mvel jar in 5.2.0.ER5 distribution server configs 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-3483 0 None None None Never

Internal Links: 781009

Description Len DiMaggio 2011-10-13 20:17:37 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
project_key: SOA

The original summary of this JIRA was:
"The DroolsTest program in a Drools sample project, created with JBDS 4.1.1 with the runtime supplied by SOA-P 5.2.0.ER5 fails with a class not found error"

If the user creates a new Drools runtime, and defines the runtime directory as jboss-soa-p-5/jboss-as/server/[profile]/deploy/jbrules.esb

Then errors such as this will result:

1) Create a new Drools project
2) Specify Drools runtime as deployed in SOA-P 5.2.0.ER5 - jboss-soa-p-5/jboss-as/server/default/deploy/jbrules.esb
3) Run DroolsTest.java

Results in:

java.lang.NoClassDefFoundError: com/thoughtworks/xstream/XStream
	at org.drools.audit.KnowledgeRuntimeLoggerProviderImpl.newFileLogger(KnowledgeRuntimeLoggerProviderImpl.java:29)
	at org.drools.logger.KnowledgeRuntimeLoggerFactory.newFileLogger(KnowledgeRuntimeLoggerFactory.java:52)
	at com.sample.DroolsTest.main(DroolsTest.java:25)
Caused by: java.lang.ClassNotFoundException: com.thoughtworks.xstream.XStream
	at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
	... 3 more
Comment 1 Len DiMaggio 2011-10-13 20:18:05 UTC 
Looks like we don't have this fix:

JBRULES-2589
Comment 2 Len DiMaggio 2011-10-13 20:18:28 UTC 
Link: Added: This issue depends JBRULES-2589
Comment 3 Len DiMaggio 2011-10-14 15:35:07 UTC 
See:  https://issues.jboss.org/browse/JBIDE-5568

The correct directory for the runtime is the top-level SOA-P dir ("jboss-soa-p-5/")
Comment 4 Len DiMaggio 2011-10-14 15:35:07 UTC 
Affects: Added: Documentation (Ref Guide, User Guide, etc.)
Comment 5 Len DiMaggio 2011-10-14 15:35:39 UTC 
Link: Added: This issue depends JBIDE-5568
Comment 6 Len DiMaggio 2011-10-14 15:53:40 UTC 
Link: Added: This issue relates to SOA-3487
Comment 7 David Le Sage 2011-10-21 01:17:18 UTC 
Release Notes Docs Status: Added: Documented as Known Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-3483

The Drools runtime definition must reference the ${SOA-P 5.0} top-level directory, not the ${SOA-P 5.0}/jboss-as/server/default/deploy/jbrules.esb or the user will encounter a java.lang.NoClassDefFoundError when the project is run.
Comment 8 David Le Sage 2011-10-21 01:17:42 UTC 
I have documented this in the release notes.
Comment 11 David Le Sage 2011-11-29 02:59:33 UTC 
Picked up for the first update to the release notes.
Note You need to log in before you can comment on or make changes to this bug.