February 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1972) Show DRL for decision tables

by Simon Spielmann (JIRA)

Show DRL for decision tables ---------------------------- Key: JBRULES-1972 URL: https://jira.jboss.org/jira/browse/JBRULES-1972 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse Reporter: Simon Spielmann Assignee: Mark Proctor Sometimes it is very useful to see the generated drl for a decision table. Without it you can't even set breakpoints. I suggest to add a menu item e.g. "show drl" to the context menu for a spreadsheet file in the eclipse ide. I think this shouldn't be to hard to implement. -- 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

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1968) Eclipse ruleflow editor cut, copy and paste operations appear to be allowed but do not work

by Shahad Ahmed (JIRA)

Eclipse ruleflow editor cut, copy and paste operations appear to be allowed but do not work ------------------------------------------------------------------------------------------- Key: JBRULES-1968 URL: https://jira.jboss.org/jira/browse/JBRULES-1968 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse, drools-eclipse (expert), drools-eclipse (flow) Affects Versions: 5.0.0.M5 Reporter: Shahad Ahmed Assignee: Mark Proctor The Edit menu in the drools eclipse plugin contains options to Cut, Copy and Paste nodes for a ruleflow editor. However, these operations do not work in the editor and cause exceptions to be reported in the eclipse log. For example, if you attempt to copy a ruleflow node then you get the following error on the eclipse log: !ENTRY org.eclipse.ui 4 4 2009-02-12 13:40:16.843 !MESSAGE Failed to execute item copy !STACK 0 org.eclipse.core.commands.NotHandledException: There is no handler to execute for command org.eclipse.ui.edit.copy I assume the Ruleflow editor is not intended to support cut, copy and paste of nodes as was the case in Drools 4, and that this is simply a minor bug to do with the cut, copy and paste menu options not being greyed out, as in drools v4 plugin. Of course, it would be nice to have cut, copy and paste for ruleflow nodes, so perhaps this JIRA could be reclassified as a feature request, if appropriate. -- 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

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1770) IndexOutOfBoundsException with subflows while removing listener from RuleFlowEventSupport

by Richard bedard (JIRA)

IndexOutOfBoundsException with subflows while removing listener from RuleFlowEventSupport ----------------------------------------------------------------------------------------- Key: JBRULES-1770 URL: https://jira.jboss.org/jira/browse/JBRULES-1770 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Rule Flow Affects Versions: 4.0.7 Environment: MyEclipse Blue, Windows XP, Reporter: Richard bedard Assignee: Mark Proctor I have 9 ruleFlows, A, B and C and 6 others A is the main one that include B as a subflow and 6 others, B include C as a subflow When RuleFlowEventSupport.fireRuleFlowProcessCompleted is called, the listeners list contains 8 elements, 1 per sub ruleflow. The size of the list is set in a variable "i" for performance i guess: for ( int i = 0, size = this.listeners.size(); i < size; i++ ) { But somehow, i didn't check the reason, the method removeEventListener is called and the list size is now 7, so im having an java.lang.IndexOutOfBoundsException. This appen when the subflow C isn't changing the working memory(no insert, modify or remove), when an object is inserted, there is no error... I've tried with and without shadow fact "setShadowProxy( false/true );" Object removed: listener RuleFlowProcessInstanceImpl (id=7454) id 2 nodeInstances ArrayList<E> (id=7749) process RuleFlowProcessImpl (id=7750) state 2 workingMemory ReteooStatefulSession (id=7444) Stack that show the object removing while iterating on the list: RuleFlowEventSupport.removeEventListener(RuleFlowEventListener) line: 48 <----- A listerner is removed here ReteooStatefulSession(AbstractWorkingMemory).removeEventListener(RuleFlowEventListener) line: 306 RuleFlowProcessInstanceImpl.setState(int) line: 184 EndNodeInstanceImpl.trigger(RuleFlowNodeInstance) line: 30 RuleFlowJoinInstanceImpl.triggerCompleted() line: 89 RuleFlowJoinInstanceImpl.checkActivation() line: 85 RuleFlowJoinInstanceImpl.trigger(RuleFlowNodeInstance) line: 59 SubFlowNodeInstanceImpl.triggerCompleted() line: 51 RuleFlowProcessInstanceImpl.ruleFlowCompleted(RuleFlowCompletedEvent, WorkingMemory) line: 262 RuleFlowEventSupport.fireRuleFlowProcessCompleted(RuleFlowProcessInstance, InternalWorkingMemory) line: 86 <--- Iterating on the listeners list here RuleFlowProcessInstanceImpl.setState(int) line: 185 EndNodeInstanceImpl.trigger(RuleFlowNodeInstance) line: 30 RuleFlowJoinInstanceImpl.triggerCompleted() line: 89 RuleFlowJoinInstanceImpl.checkActivation() line: 85 RuleFlowJoinInstanceImpl.trigger(RuleFlowNodeInstance) line: 59 RuleFlowGroupImpl(RuleFlowSequenceNodeInstanceImpl).triggerCompleted() line: 38 RuleFlowGroupImpl.setActive(boolean) line: 103 RuleFlowGroupImpl$DeactivateCallback.execute(InternalWorkingMemory) line: 211 ReteooStatefulSession(AbstractWorkingMemory).executeQueuedActions() line: 1312 ReteooStatefulSession(AbstractWorkingMemory).fireAllRules(AgendaFilter, int) line: 467 ReteooStatefulSession(AbstractWorkingMemory).fireAllRules() line: 439 DroolsStdImpl.executeRulesEngine(List<Object>, String) line: 100 -- 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

15 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1791) Parenthesis required for 'exist' rule in Split constraint editor

by Roger Lefebvre (JIRA)

Parenthesis required for 'exist' rule in Split constraint editor ---------------------------------------------------------------- Key: JBRULES-1791 URL: https://jira.jboss.org/jira/browse/JBRULES-1791 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Rule Flow Affects Versions: 4.0.7 Environment: Fedora 5, tomcat 6, drools 4.0.7 Reporter: Roger Lefebvre Assignee: Mark Proctor Priority: Minor A rule such as: exists Item() throws InvalidRulePackage "Unexpected token exists ..." when doing performing ruleBase.addPackage(builder.getPackage()). Adding parenthesis resolves the problem. e.g. exists (Item()) Similar applies to not and other qualifiers/functions. -- 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

15 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JGRP-814) Probe dump to show deadlocks and use JDK6 APIs is available

by Galder Zamarreno (JIRA)

Probe dump to show deadlocks and use JDK6 APIs is available ----------------------------------------------------------- Key: JGRP-814 URL: https://jira.jboss.org/jira/browse/JGRP-814 Project: JGroups Issue Type: Feature Request Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 2.7 Probe dump does not currently show locked monitors or synchronisers that can be retrieved using JDK6 API and does not show detected deadlocks either. -- 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

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-833) Maven2ize drools-examples

by Geoffrey De Smet (JIRA)

Maven2ize drools-examples ------------------------- Key: JBRULES-833 URL: http://jira.jboss.com/jira/browse/JBRULES-833 Project: JBoss Rules Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 3.1-m1 Reporter: Geoffrey De Smet Assigned To: Mark Proctor Priority: Minor - the eclipse files can now be generate and generate the maven builder in it too - it compiles with a mvn install => catch compile errors early -- 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

15 years, 3 months

2
21
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1166) jta-data-source / non-jta-data-source

by Jesper Pedersen (JIRA)

jta-data-source / non-jta-data-source ------------------------------------- Key: EJBTHREE-1166 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1166 Project: EJB 3.0 Issue Type: Bug Environment: JBoss AS: SVN / trunk (rev 68402) jboss-ejb3-cache version="0.11.1" jboss/jboss-ejb3-ext-api version="0.1.2.Beta1" jboss/jboss-ejb3-impl version="0.1.2.Beta1" Reporter: Jesper Pedersen I get the following: persistence.units:ear=rasp-sender.ear,unitName=e-akten-test -> java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named: e-akten-test persistence.units:ear=rasp-sender.ear,unitName=e-akten -> java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a jta-data-source for a JTA enabled persistence context named: e-akten The EJB3 persistence spec section 6.2.1.5 states: "In Java EE environments, the jta-data-source and non-jta-data-source elements are used to specify the global JNDI name of the JTA and/or non-JTA data source to be used by the persistence provider. If neither is speciﬁed, the deployer must specify a JTA data source at deployment or a JTA data source must be provided by the container, and a JTA EntityManagerFactory will be created to cor- respond to it." I'm counting on the last case -- data source must be provided by container + entity manager. Hope this helps ! -- 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

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4413) Incorrect behaviour in TCLFilter

by Poyan (JIRA)

Incorrect behaviour in TCLFilter -------------------------------- Key: JBAS-4413 URL: http://jira.jboss.com/jira/browse/JBAS-4413 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: JBossAS-4.0.5.GA Reporter: Poyan Assigned To: Scott M Stark Just one TCLFilter can be added to an appender, decide method return either ACCEPT or DENY. Should return NEUTRAL is some case. public int decide(LoggingEvent event) { int ok = Filter.DENY; if( acceptOnMatch == true ) { ok = Filter.DENY; if( isMatchingTCL() ){ ok = Filter.ACCEPT; } } else { ok = Filter.ACCEPT; // CHANGING THIS ROW TO ok = Filter.NEUTRAL; should do that you check the other filters to. if( isMatchingTCL() ) ok = Filter.DENY; } return ok; } Log4j.xml: <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender"> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d %-5p [%t] %c - %m%n"/> </layout> <filter class="org.jboss.logging.filter.TCLFilter"> <param name="AcceptOnMatch" value="false"/> <param name="DeployURL" value="jboss-common-client.jarpoyan"/> </filter> <filter class="org.jboss.logging.filter.TCLFilter"> <param name="AcceptOnMatch" value="false"/> <param name="DeployURL" value="dnsns.jarpoyan"/> </filter> </appender> -- 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

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-900) Address: remove isMulticastAddress()

by Bela Ban (JIRA)

Address: remove isMulticastAddress() ------------------------------------ Key: JGRP-900 URL: https://jira.jboss.org/jira/browse/JGRP-900 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 With logical addresses, we don't need this anymore: Address dest=msg.getDest(); boolean mcast=dest == null || dest.isMulticastAddress(); should be changed to boolean mcast=msg.isMulticastMessage(); // or isGroupMessage() ? -- 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

15 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JGRP-899) Message: remove dest_addr

by Bela Ban (JIRA)

Message: remove dest_addr ------------------------- Key: JGRP-899 URL: https://jira.jboss.org/jira/browse/JGRP-899 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 We don't need this field, this will save us some memory. Note that today dest_addr is *not* shipped with a message, but nevertheless filled in on the receiving side. We have tests which use dest_addr to determine whether the message is a unicast or multicast message. This should go away, too, and be replaced by a flag in the message itself, ie. MULTICAST. Maybe add a method Message.isMulticast(). -- 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

15 years, 3 months

1
3
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 February 2009