July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-568) IDE to understand new XXX.package rule package config file, and support 1 rule per file "convention" to sync with repository

by Michael Neale (JIRA)

IDE to understand new XXX.package rule package config file, and support 1 rule per file "convention" to sync with repository ---------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-568 URL: http://jira.jboss.com/jira/browse/JBRULES-568 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1-m3 Reporter: Michael Neale Assigned To: Kris Verlaenen Fix For: 3.1-m3 package layout will be something like: /<RulePackageName>.package - has imports in it etc... /Rule Name 1.rule (vanilla DRL) /Rule Name 2.brule (uses DSL) /XXX.dsl (used by brule file) None of the atomic rule files will have package name, or anything other then when/then/attributes, the IDE will have to look in to the .package file to find this out. .drl files can work as they do now. Let me know if this is a dupe ;) -- 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

13 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBRULES-493) Remember selected working memory for debug views

by Mark Proctor (JIRA)

Remember selected working memory for debug views ------------------------------------------------ Key: JBRULES-493 URL: http://jira.jboss.com/jira/browse/JBRULES-493 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m1 When you select working memory it should remember that instance, so when you are propagating through the network you shouldn't have to keep re-selecting it to view data. Better yet we should have another debug view that collects working memory instances as it "realises" them during debug runtime, the current one is highlighed and a different current can easily be selected. -- 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

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-775) tree views should remember open/close toggle

by Mark Proctor (JIRA)

tree views should remember open/close toggle -------------------------------------------- Key: JBRULES-775 URL: http://jira.jboss.com/jira/browse/JBRULES-775 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m2 When using the views, such as agenda view, they keep expanding everything, when you have a large number of entries having to repeatedly re-adjust the layout of the tree view is annoying. -- 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

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-776) Working Memory View by Object Type

by Mark Proctor (JIRA)

Working Memory View by Object Type ---------------------------------- Key: JBRULES-776 URL: http://jira.jboss.com/jira/browse/JBRULES-776 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m2 It would be nice in the Working Memory view if we could also view by object type. -- 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

13 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-980) Support drl files that contain only one rule

by Kris Verlaenen (JIRA)

Support drl files that contain only one rule -------------------------------------------- Key: JBRULES-980 URL: http://jira.jboss.com/jira/browse/JBRULES-980 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Fix For: FUTURE As possible in the BRMS, a drl file can possibly contain only one rule without rule name, in combination with a .package file. Currently, the drl editor does not support this type of drl file. -- 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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-804) Provide "Source Path" with includes/excludes pattern capability for JBoss Rules Eclipse IDE (3.1-M1 currently validates _all_ .xls files in project)

by Bree VanOss (JIRA)

Provide "Source Path" with includes/excludes pattern capability for JBoss Rules Eclipse IDE (3.1-M1 currently validates _all_ .xls files in project) ---------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-804 URL: http://jira.jboss.com/jira/browse/JBRULES-804 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.1-m1 Environment: WinXP, Sun JRE 1.4.2_12 Reporter: Bree VanOss Assigned To: Mark Proctor Priority: Minor The Eclipse "Drools Builder" is validating every Excel (.xls) in my rules project. Apparently this feature was added to 3.1-M1 by Kris. I really like the idea of validating decision tables in Eclipse, my issue is that we have FIT tests (in Excel) in a separate source folder in our "rules project". These .xls files are falsely being identified as decision tables with a ton of problems. Validation also seems to take much longer than it does with the 3.0.x branch (like from 30 seconds in 3.0 to to 5 minutes in 3.1 !?!?). Though the two issues may be related. A common way of dealing with this problem in Eclipse is to allow for ant-like "source path include/exclude" patterns. i.e. exclude test/**/*.xls For that matter it would be nice to have the same thing for standard DRL files. The validation of a large rule base can take some time and randomly results in exceptions much of the time. Once I've tested and verified a set of rules I could (optionally) exclude them from validation. -- 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

13 years, 8 months

5
5
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

13 years, 8 months

2
21
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

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-396) Replace all uses of Vector, ArrayList etc with interfaces

by Bela Ban (JIRA)

Replace all uses of Vector, ArrayList etc with interfaces --------------------------------------------------------- Key: JGRP-396 URL: http://jira.jboss.com/jira/browse/JGRP-396 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 - E.g. - Vector --> Collection - ArrayList --> List -- 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

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-412) Replace all uses of Channel.receive() with Receiver.receive() callbacks

by Bela Ban (JIRA)

Replace all uses of Channel.receive() with Receiver.receive() callbacks ----------------------------------------------------------------------- Key: JGRP-412 URL: http://jira.jboss.com/jira/browse/JGRP-412 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 This includes removing PullPushAdapters and converting MessageDispatcher/RpcDispatcher to use Receiver instead of PullPushAdapter -- 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

13 years, 8 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007