June 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-340) Track component updates

by Jesper Pedersen (JIRA)

Track component updates ----------------------- Key: JBJCA-340 URL: https://jira.jboss.org/browse/JBJCA-340 Project: JBoss JCA Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha13 -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-339) JBoss JCA 1.0.0.Alpha12

by Jesper Pedersen (JIRA)

JBoss JCA 1.0.0.Alpha12 ----------------------- Key: JBJCA-339 URL: https://jira.jboss.org/browse/JBJCA-339 Project: JBoss JCA Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha12 -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2344) Pattern analysis can never be satisfied, however the rule is logically correct

by Claudio Gargiulo (JIRA)

Pattern analysis can never be satisfied, however the rule is logically correct ------------------------------------------------------------------------------ Key: JBRULES-2344 URL: https://jira.jboss.org/jira/browse/JBRULES-2344 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-verifier Affects Versions: 5.0.1.FINAL Environment: MacBook Pro 17" Core 2 Duo Ubuntu 9.10 64bit (native, not virtualized) - Apache Tomcat 6.0.18 - Java 6 Reporter: Claudio Gargiulo Assignee: Mark Proctor When I launch the analysis of a rule I get the following message: Pattern, name: TrafficoEntrata in Rule 'backToNormal' can never be satisfied. Pattern, name: StatoRete in Rule 'backToNormal' can never be satisfied. The Rule "backToNormal" is the following: rule "backToNormal" dialect "mvel" when exists Attacco( ) attack : Attacco( ) StatoRete( numero_utenti > "25" && < "80" ) TrafficoEntrata( banda_occupata > "20" && < "80" ) then retract( attack ); end The integer values are taken from an enumeration. Altering the conditions in this way: numero_utenti >"25", numero_utenti < "80" makes no difference at analysis time. -- 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

16 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1970) Upgrade to jboss-ejb3-deployers 1.0.1

by Carlo de Wolf (JIRA)

Upgrade to jboss-ejb3-deployers 1.0.1 ------------------------------------- Key: EJBTHREE-1970 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1970 Project: EJB 3.0 Issue Type: Thirdparty Change Components: ejb3 Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: 1.1.23 -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2118) comment makes Work Definition parser fail

by Wolfgang Laun (JIRA)

comment makes Work Definition parser fail ----------------------------------------- Key: JBRULES-2118 URL: https://jira.jboss.org/jira/browse/JBRULES-2118 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Affects Versions: 5.0.1.FINAL Environment: Eclipse Reporter: Wolfgang Laun Assignee: Mark Proctor See example in Drools Flow, section 8.2.1., Creating the Work Definition: The comment // add more work items here ... makes the parser fail when calling up the RuleFlow editor ("Could not parse work definitions ...: null") -- 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

16 years, 1 month

5
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2232) NullPointerException using drools-persistance-jpa and Drools Flows (WorkItemInfo)

by Noel Keating (JIRA)

NullPointerException using drools-persistance-jpa and Drools Flows (WorkItemInfo) --------------------------------------------------------------------------------- Key: JBRULES-2232 URL: https://jira.jboss.org/jira/browse/JBRULES-2232 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.0.M1 Reporter: Noel Keating Assignee: Mark Proctor I'm getting a NPE exception when using drools-persistence-jpa with Drools Flow (I'm working with the trunk version 28274). It occurs in MarshallerReaderContext and seems to be a result of JBRULES-2149. When loading a WorkItemInfo from the database a MarshallerReaderContext is created without the ruleBase set, however the MarshallerReaderContext expects the ruleBase to be set. In the attached patch I have added a null check and call the super method if it is not set. This seems to be working correctly and would have been the behaviour before JBRULES-2149. -- 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

16 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2450) Nullpointer Exception when refacroring in unreleted projects

by JÃ¼rgen Schmied (JIRA)

Nullpointer Exception when refacroring in unreleted projects ------------------------------------------------------------ Key: JBRULES-2450 URL: https://jira.jboss.org/jira/browse/JBRULES-2450 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 5.1.0.M1 Environment: eclipse.buildId=3.5.2 java.version=1.6.0_14 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product Reporter: JÃ¼rgen Schmied Assignee: Mark Proctor When renaming a class in a non drools project I get a NullPointerException in the drools plugin. Participant 'org.drools.eclipse.refactoring.moveParticipant' removed due to the following exception java.lang.NullPointerException at org.drools.eclipse.refactoring.DRLProjectDetector.detect(Unknown Source) at org.drools.eclipse.refactoring.DRLProjectDetector.detect(Unknown Source) at org.drools.eclipse.refactoring.DRLProjectDetector.detect(Unknown Source) at org.drools.eclipse.refactoring.RuleIFileMoveParticipant.createChange(Unknown Source) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:308) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:211) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- 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

16 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2452) Conversion issues when using comparaison in name of a ruletask.

by philippe rouxel (JIRA)

Conversion issues when using comparaison in name of a ruletask. --------------------------------------------------------------- Key: JBRULES-2452 URL: https://jira.jboss.org/jira/browse/JBRULES-2452 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Affects Versions: 5.0.1.FINAL Environment: org.drools.eclipse (5.1.0.v201003050540R-H56-31764) "Drools Eclipse Plug-in" [Active] org.drools.eclipse.task (5.1.0.v201003050540R-H56-31764) "Drools Eclipse Task Plug-in" [Active] jdk1.6.17 winxp Reporter: philippe rouxel Assignee: Mark Proctor if I put a ruletask withe the name "N >10", the node is save as name = "N >10" instead of "N >10". when I reload the ruleflow file, Sax generate an exception. when I replace the > by > it's ok. -- 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

16 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2095) MVEL action in Flow does not support .* imports

by Kris Verlaenen (JIRA)

MVEL action in Flow does not support .* imports ----------------------------------------------- Key: JBRULES-2095 URL: https://jira.jboss.org/jira/browse/JBRULES-2095 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (flow) Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.1.0.M1 There seems to be an issue where MVEL is not picking up the imports in a Flow Action node if the imports are package imports. For example: context.getKnowledgeRuntime().insert( new Fact() ); results in "could not resolve class: Fact" when using import org.drools.examples.model.* Using import org.drools.examples.model.Fact works 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

16 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2531) Event expiration set to 0 (zero) on type declaration is not being considered

by Edson Tirelli (JIRA)

Event expiration set to 0 (zero) on type declaration is not being considered ---------------------------------------------------------------------------- Key: JBRULES-2531 URL: https://jira.jboss.org/browse/JBRULES-2531 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (fusion), drools-core (fusion) Affects Versions: 5.1.0.M2 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.1.0.CR1 Event expiration set to 0 (zero) on type declaration is not being considered -- 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

16 years, 1 month

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 June 2010