[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5568) SOA-P 5.0 could not be used as a Drools runtime
Kris Verlaenen (JIRA)
jira-events at lists.jboss.org
Fri Feb 19 15:03:17 EST 2010
[ https://jira.jboss.org/jira/browse/JBIDE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12515502#action_12515502 ]
Kris Verlaenen commented on JBIDE-5568:
---------------------------------------
This indeed no longer works with the latest release of SOA-P 5.0. Reason is that we used the "jboss-esb/server/default/deploy/jbossesb.sar/lib" dir to detect whether this was SOA-P 4 or SOA-P 5 (based on whether the mvel and xstream jar could be found there or not). But since this directory seems to have been removed in the latest SOA-P 5, the test could no longer detect this, so the SOA-P 5 runtime could not be detected. Fixed on Drools trunk.
> SOA-P 5.0 could not be used as a Drools runtime
> -----------------------------------------------
>
> Key: JBIDE-5568
> URL: https://jira.jboss.org/jira/browse/JBIDE-5568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: drools
> Affects Versions: 3.1.0.CR1
> Environment: SOA-P 5.0 ER6
> Reporter: Dominik Pospisil
> Assignee: Kris Verlaenen
> Priority: Critical
> Fix For: 3.1.0.CR2
>
>
> The Drools runtime in SOA-P 5.0 distribution is located at:
> /jboss-as/server/default/deploy/jbrules.esb
> This could be added to JBT as a Drools runtime, but executing on this runtime fails:
> java.lang.NoClassDefFoundError: org/mvel2/integration/VariableResolverFactory
> at org.drools.rule.builder.dialect.java.JavaDialect.<clinit>(JavaDialect.java:98)
> at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.newDialect(JavaDialectConfiguration.java:65)
> at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:291)
> at org.drools.compiler.PackageRegistry.<init>(PackageRegistry.java:24)
> at org.drools.compiler.PackageBuilder.newPackage(PackageBuilder.java:874)
> at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:592)
> at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:290)
> at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:488)
> at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:25)
> at com.sample.DroolsTest.readKnowledgeBase(DroolsTest.java:40)
> at com.sample.DroolsTest.main(DroolsTest.java:23)
> Caused by: java.lang.ClassNotFoundException: org.mvel2.integration.VariableResolverFactory
> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
> ... 11 more
> Steps to reproduce:
> 1) Setup Drools runtime pointing to ${SOA-P 5.0}/jboss-as/server/default/deploy/jbrules.esb
> 2) Create Drools project
> 3) Right-Click on DroolsTest.java, choose Run As -> Java Application
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list