November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2244) MVEL raising errors for declared types when there is a package import (import x.y.x.*)

by Edson Tirelli (JIRA)

MVEL raising errors for declared types when there is a package import (import x.y.x.*) -------------------------------------------------------------------------------------- Key: JBRULES-2244 URL: https://jira.jboss.org/jira/browse/JBRULES-2244 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.0.1.FINAL, 5.0.0.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.1.0.M1 The following DRL: =================================================== package org.drools.examples.broker import org.drools.examples.broker.model.*; declare Statistics symbol : String @key() average : double end rule "Setup statistics" when $c : Company( $s : symbol ) not( Statistics( symbol == $s ) ) then Statistics s = new Statistics(); s.symbol = $s; insert( s ); end =================================================== Generates the error: ----------------------------- BuildError: Unable to build expression for 'consequence': Failed to compile: 1 compilation error(s): - (1,10) unqualified type in strict mode for: Statistics ' Statistics s = new Statistics(); s.symbol = $s; insert( s ); ' broker.drl drools-examples-fusion/src/main/rules line 42 Drools Error ----------------------------- But if we change the import to: =================================================== import org.drools.examples.broker.model.Company import org.drools.examples.broker.model.StockTick import org.drools.examples.broker.model.SuddenDropEvent =================================================== Everything works just fine. -- 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

14 years, 3 months

5
16
0 / 0

[JBoss JIRA] Created: (JBRULES-2805) Problem getting and using drools-api SNAPSHOT version from jboss maven repo

by Kris Verlaenen (JIRA)

Problem getting and using drools-api SNAPSHOT version from jboss maven repo --------------------------------------------------------------------------- Key: JBRULES-2805 URL: https://jira.jboss.org/browse/JBRULES-2805 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kris Verlaenen Assignee: Geoffrey De Smet When adding drools-api as a dependency of another maven project, it will try to download the drools-api jar from the jboss maven repo, but then fail to download its parent somehow. If you first build drools locally, it can then find the parent pom in the repository succesfully. [INFO] snapshot org.drools:drools-api:5.2.0.SNAPSHOT: checking for updates from jboss-public-repository-group Downloading: https://repository.jboss.org/nexus/content/groups/public//org/drools/droo... 6K downloaded (drools-api-5.2.0.20101123.060233-380.pom) [INFO] snapshot org.drools:drools:5.2.0.SNAPSHOT: checking for updates from jboss-public-repository-group Downloading: https://repository.jboss.org/nexus/content/groups/public//org/drools/droo... [INFO] Unable to find resource 'org.drools:drools:pom:5.2.0.SNAPSHOT' in repository jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: null:drools-api:jar:null Reason: Cannot find parent: org.drools:drools for project: null:drools-api:jar:null for project null:drools-api:jar:null -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1801) drools-ant-4.0.7, DroolsCompilerAntTask, classloader mixup leads to ClassCastException if drools-compiler.jar part of classpathref

by Juergen none (JIRA)

drools-ant-4.0.7, DroolsCompilerAntTask, classloader mixup leads to ClassCastException if drools-compiler.jar part of classpathref ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-1801 URL: https://jira.jboss.org/jira/browse/JBRULES-1801 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-ant Affects Versions: 4.0.7 Reporter: Juergen none Assignee: Mark Proctor drools-4.0.7: Original error in build.xml: /home/juergen/workspace/eclipse/kusss-dev/build.xml:777: RuleBaseTask failed: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java' Traceback to: org.drools.compiler.PackageBuilderConfiguration, line 154+: Class cls = classLoader.loadClass( dialectClass ); DialectConfiguration dialectConf = (DialectConfiguration) cls.newInstance(); cls is org.drools.rule.builder.dialect.java.JavaDialectConfiguration, but loaded via classloader given in drools compile ant task property classpathref, while DialectConfiguration is loaded via ant tool classpath used for taskdef --> java.lang.ClassCastException: org.drools.rule.builder.dialect.java.JavaDialectConfiguration interim fix: make sure drools-compiler.jar is not in classpath of classloaderref suggested fix: Class cls = DialectConfiguration.class.getClassLoader().loadClass( dialectClass ); -- 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

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1273) Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)

by Rainer Langbehn (JIRA)

Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task) ---------------------------------------------------------------------------------------------------------------------- Key: JBRULES-1273 URL: http://jira.jboss.com/jira/browse/JBRULES-1273 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Rainer Langbehn Assigned To: Mark Proctor I already created the requested maven2 plugin and i would like to contribute it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
26
0 / 0

[JBoss JIRA] Created: (JBRULES-2384) Unable to process deployment descriptor for context'/drools-server'

by Megha Shetty (JIRA)

Unable to process deployment descriptor for context'/drools-server' ------------------------------------------------------------------- Key: JBRULES-2384 URL: https://jira.jboss.org/jira/browse/JBRULES-2384 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Environment: windows Reporter: Megha Shetty Assignee: Mark Proctor I am getting the following error when i am trying to deploy drools-server.war through jboss. Unable to process deployment descriptor for context'/drools-server' Following is the complete log when i am starting the jboss server JAVA_HOME is not set. Unexpected results may occur. Set JAVA_HOME to the directory of your local JDK to avoid this message. =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: E:\Eclipse Europa\jboss-4.2.3.GA JAVA: java JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcIn terval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 CLASSPATH: E:\Eclipse Europa\jboss-4.2.3.GA\bin\run.jar =============================================================================== 14:35:43,295 INFO [Server] Starting JBoss (MX MicroKernel)... 14:35:43,295 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag= JBoss_4_2_3_GA date=200807181417) 14:35:43,295 INFO [Server] Home Dir: E:\Eclipse Europa\jboss-4.2.3.GA 14:35:43,295 INFO [Server] Home URL: file:/E:/Eclipse Europa/jboss-4.2.3.GA/ 14:35:43,295 INFO [Server] Patch URL: null 14:35:43,295 INFO [Server] Server Name: default 14:35:43,295 INFO [Server] Server Home Dir: E:\Eclipse Europa\jboss-4.2.3.GA\se rver\default 14:35:43,311 INFO [Server] Server Home URL: file:/E:/Eclipse Europa/jboss-4.2.3 .GA/server/default/ 14:35:43,311 INFO [Server] Server Log Dir: E:\Eclipse Europa\jboss-4.2.3.GA\ser ver\default\log 14:35:43,311 INFO [Server] Server Temp Dir: E:\Eclipse Europa\jboss-4.2.3.GA\se rver\default\tmp 14:35:43,311 INFO [Server] Root Deployment Filename: jboss-service.xml 14:35:43,482 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc. 14:35:43,482 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,S un Microsystems Inc. 14:35:43,498 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 14:35:43,857 INFO [Server] Core system initialized 14:35:45,670 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083 / 14:35:45,670 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:jboss-log4j.xml 14:35:46,513 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 14:35:46,513 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 14:35:46,701 INFO [TransactionManagerService] Starting recovery manager 14:35:46,748 INFO [TransactionManagerService] Recovery manager started 14:35:46,748 INFO [TransactionManagerService] Binding TransactionManager JNDI R eference 14:35:50,263 INFO [EJB3Deployer] Starting java:comp multiplexer 14:35:51,607 INFO [NativeServerConfig] JBoss Web Services - Native 14:35:51,622 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200 803312044) 14:35:52,466 INFO [Embedded] Catalina naming disabled 14:35:52,575 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java .library.path: C:\WINDOWS\system32;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32 ;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem 14:35:52,607 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0 .1-8080 14:35:52,607 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80 09 14:35:52,607 INFO [Catalina] Initialization processed in 147 ms 14:35:52,607 INFO [StandardService] Starting service jboss.web 14:35:52,607 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA 14:35:52,638 INFO [Catalina] Server startup in 24 ms 14:35:52,794 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w eb.deployer/ROOT.war/ 14:35:53,560 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/ http-invoker.sar/invoker.war/ 14:35:53,669 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/ jbossws.sar/jbossws-context.war/ 14:35:53,732 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../ deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 14:35:54,153 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep loy/management/console-mgr.sar/web-console.war/ 14:35:54,513 INFO [MailService] Mail Service bound to java:/Mail 14:35:54,669 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-ha-local-jdbc.rar 14:35:54,763 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-ha-xa-jdbc.rar 14:35:54,856 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-local-jdbc.rar 14:35:54,935 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-xa-jdbc.rar 14:35:55,544 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jms/jms-ra.rar 14:35:55,716 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/mail-ra.rar 14:35:55,903 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/quartz-ra.rar 14:35:55,903 INFO [QuartzResourceAdapter] start quartz!!! 14:35:55,950 INFO [SimpleThreadPool] Job execution threads will use class loade r of thread: main 14:35:55,950 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. 14:35:55,966 INFO [RAMJobStore] RAMJobStore initialized. 14:35:55,966 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule r' initialized from default resource file in Quartz package: 'quartz.properties' 14:35:55,966 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 14:35:55,966 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS TERED started. 14:35:56,966 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 14:35:57,200 INFO [A] Bound to JNDI name: queue/A 14:35:57,200 INFO [B] Bound to JNDI name: queue/B 14:35:57,200 INFO [C] Bound to JNDI name: queue/C 14:35:57,200 INFO [D] Bound to JNDI name: queue/D 14:35:57,200 INFO [ex] Bound to JNDI name: queue/ex 14:35:57,216 INFO [testTopic] Bound to JNDI name: topic/testTopic 14:35:57,216 INFO [securedTopic] Bound to JNDI name: topic/securedTopic 14:35:57,216 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic 14:35:57,216 INFO [testQueue] Bound to JNDI name: queue/testQueue 14:35:57,231 INFO [UILServerILService] JBossMQ UIL service available at : /127. 0.0.1:8093 14:35:57,263 INFO [DLQ] Bound to JNDI name: queue/DLQ 14:35:57,341 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' 14:35:57,794 INFO [TomcatDeployer] deploy, ctxPath=/drools-guvnor, warUrl=.../d eploy/drools-guvnor.war/ 14:36:08,965 INFO [TomcatDeployer] deploy, ctxPath=/drools-server, warUrl=.../d eploy/drools-server.war/ 14:36:09,012 WARN [config] Unable to process deployment descriptor for context '/drools-server' 14:36:09,371 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep loy/jmx-console.war/ 14:36:09,496 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8 080 14:36:09,512 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 14:36:09,512 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBos s_4_2_3_GA date=200807181417)] Started in 26s:201ms -- 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

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2683) DroolsSession's initWorkItemManagerFactory method can not work in a OSGi context

by Antoine Toulme (JIRA)

DroolsSession's initWorkItemManagerFactory method can not work in a OSGi context -------------------------------------------------------------------------------- Key: JBRULES-2683 URL: https://jira.jboss.org/browse/JBRULES-2683 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.M1 Reporter: Antoine Toulme Assignee: Mark Proctor Fix For: FUTURE This affects the current trunk. The code in the method does this: String className = this.chainedProperties.getProperty( "drools.workItemManagerFactory", "org.drools.process.instance.impl.DefaultWorkItemManagerFactory" ); [..] clazz = (Class<WorkItemManagerFactory>) Thread.currentThread().getContextClassLoader().loadClass( className ); [..] clazz = (Class<WorkItemManagerFactory>) SessionConfiguration.class.getClassLoader().loadClass( className ); None of this can work for the default factory since drools-core does not depend on drools-flow-core (and creating a dependency would create a cycle). Actually, this won't work for customer code as well, since drools-core won't depend on their bundle. I suggest to use a declarative service to work around this problem, while keeping this type of instantiation around when OSGi is not on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-677) Setup integration testing

by Geoffrey De Smet (JIRA)

Setup integration testing ------------------------- Key: JBRULES-677 URL: http://jira.jboss.com/jira/browse/JBRULES-677 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor based on solver configs -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2251) The Solver's score calculation should be reusable without using the Solver itself. The examples should not know the Solver that intimetly and should not use the working memory directly.

by Geoffrey De Smet (JIRA)

The Solver's score calculation should be reusable without using the Solver itself. The examples should not know the Solver that intimetly and should not use the working memory directly. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2251 URL: https://jira.jboss.org/jira/browse/JBRULES-2251 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-solver Affects Versions: 5.0.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet -- 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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2313) Tomcat memery leak with drools 4.0.7 or 5.0.1

by GREFFET Emmanuel (JIRA)

Tomcat memery leak with drools 4.0.7 or 5.0.1 ---------------------------------------------- Key: JBRULES-2313 URL: https://jira.jboss.org/jira/browse/JBRULES-2313 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.0.1.FINAL, 4.0.7 Environment: XP tomcat 5.5.9 Reporter: GREFFET Emmanuel Assignee: Mark Proctor Priority: Critical The memory is never released !!! (never ever ) when à Stop and Start or restart Tomcat. A made this test with a simple Drools call with a simple webapp and i tried with 4.0.7 and 5.0.1 drools version. The problem is the same. We need to stop tomcat process to release memory. Until this stop each Tomcat "Restart" with a drools call, will never release the memory. I made graphic with VisualWM, and we can see this problem ! I made a zip of my simple Eclipse project (webapp + drools) and word file for more information and screen copy of VisualVM. Thanks for help. Emmanuel GREFFET ( FRANCE) -- 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

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1103) Tabu asperation based on stepscore

by Geoffrey De Smet (JIRA)

Tabu asperation based on stepscore ---------------------------------- Key: JBRULES-1103 URL: http://jira.jboss.com/jira/browse/JBRULES-1103 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Fix For: FUTURE Move tabu and property tabu could use "aspiration" Basically even if it's tabu, a move is accepted if the stepscore improves. For solution tabu this is pointless. Aspiration should occur on stepScore and NOT on decisionScore -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2010