August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1031) using Not only allows me to use 4 equality checks for fact

by Eric Miles (JIRA)

using Not only allows me to use 4 equality checks for fact ---------------------------------------------------------- Key: JBRULES-1031 URL: http://jira.jboss.com/jira/browse/JBRULES-1031 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.MR3 Environment: Fedora 7, JDK 1.5.0_12 Reporter: Eric Miles Assigned To: Mark Proctor Attachments: drools-not-fact-test.tar.gz I have a single rule in my test bed as such: rule "5th Item Not Test" when $first : FirstClass($i1 : item1, $i2 : item2, $i3 : item3, $i4 : item4, $i5 : item5) not SecondClass(item1 == $i1, item2 == $i2, item3 == $i3, item4 == $i4, item5 == $i5) then System.out.println("NOT test matched"); end In the not SecondClass() section of the test, the last equality checks always fail, no matter what it is. I can switch the order around of the checks, no matter what the last one is, it causes THEN clause to not fire, even when I am absolutely positive there is not a match. (I can remove the not and the equality works fine). Is there a limit on the number of equality tests I can do with a not? It seems as though it is 4. I have attached a test case that can reproduce this (it is different from my project's code, but I have been able to reproduce this in multiple projects). It is a maven Eclipse project and includes a junit with some minor instructions. I have created a rule that will fire as the opposite of the rule I'm trying to test and it prints out the values to the console. You can see in the console that the values are not equal, although the rule fired that they were. If these instructions do not make sense, please email me. -- 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

18 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (GPD-81) Add support for reconnecting transitions

by Ronald van Kuijk (JIRA)

Add support for reconnecting transitions ---------------------------------------- Key: GPD-81 URL: http://jira.jboss.com/jira/browse/GPD-81 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.alpha4 Environment: Clean eclipse 3.2.2 and gpd 3.1alpha4 Reporter: Ronald van Kuijk Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.beta1 Not being able to reconnect transitions graphically from e.g. node a to node b is still a big omission for the gpd to be used by 'grey suites' as well as 'jeans and t-shirts', at least within our company. I thought there was a long standing issue for this, but I cannot find it. If someone could point me to a place to start looking into this, I'd be happy to try to implement this (but it will be the only gpd thing I do ;-) ) -- 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

18 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (GPD-77) Need a way to initialize palette objects in GD 3.1

by John Ruud (JIRA)

Need a way to initialize palette objects in GD 3.1 -------------------------------------------------- Key: GPD-77 URL: http://jira.jboss.com/jira/browse/GPD-77 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: John Ruud Assigned To: Koen Aers For example, whenever an 'EndState' node is added to the diagram, I need for it to be initialized with a particular event, action, and some action properties. I have made some minor changes to the GD code in order to support this, as described in the following post: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=108175 It would be very helpful if these changes, or similar functionality, can be included in 3.1, as I wouldn't need to keep maintaining my own custom version of the GD feature. I'd be happy to post a patch, if that helps (while my changes are very simple, as described in the post) -- 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

18 years, 11 months

2
16
0 / 0

[JBoss JIRA] Created: (JBRULES-1084) Provide case insentive completions in eth DRL Editor for MVEL and Java completions

by Philippe Ombredanne (JIRA)

Provide case insentive completions in eth DRL Editor for MVEL and Java completions ----------------------------------------------------------------------------------- Key: JBRULES-1084 URL: http://jira.jboss.com/jira/browse/JBRULES-1084 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Philippe Ombredanne Assigned To: Mark Proctor Priority: Minor Fix For: 4.0.1 You do not get the same completions when typing a lower case or upper case prefix. Completaions should be offered for all the lower or uppercase prefix -- 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

18 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1080) Modify (var) added to Eclipse code completion for mvel

by Philippe Ombredanne (JIRA)

Modify (var) added to Eclipse code completion for mvel ------------------------------------------------------ Key: JBRULES-1080 URL: http://jira.jboss.com/jira/browse/JBRULES-1080 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.1 Reporter: Philippe Ombredanne Assigned To: Philippe Ombredanne Priority: Minor Attachments: mvel.png Reported by Mark: I've found a weird one with context assist, some how its adding "modify ( var )" to the list of context completions, but it only does that if you've already added the line to the consequence. See modify( game ). -- 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

18 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1630) WindowState and Mode comparator severely broken

by Julien Viet (JIRA)

WindowState and Mode comparator severely broken ----------------------------------------------- Key: JBPORTAL-1630 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1630 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.6.1 Final, 2.8 Final Reporter: Julien Viet Assigned To: Julien Viet Fix For: 2.6.2 Final, 2.8 Final - not thread safe - is using family for comparison instead of name -- 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

18 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-858) org.jboss.test.messaging.jms.bridge.ReconnectTest times out

by Ovidiu Feodorov (JIRA)

org.jboss.test.messaging.jms.bridge.ReconnectTest times out ----------------------------------------------------------- Key: JBMESSAGING-858 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-858 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Tim Fox Fix For: 1.2.0.GA Temporarily commented out. -- 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

18 years, 11 months

2
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot

by Ovidiu Feodorov (JIRA)

Starting two node clusters simultaneously may end in failed messaging server node boot -------------------------------------------------------------------------------------- Key: JBMESSAGING-693 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in RequestHandler java.lang.IllegalStateException: Don't know about node id: 1 at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597) at org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55) at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526) at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602) at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623) at org.jgroups.blocks.RequestCorrelator.access -- 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

18 years, 11 months

6
11
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-26) Standalone Messaging configuration.

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ] Tim Fox updated JBMESSAGING-26: ------------------------------- Assignee: (was: Alex Pinkin) > Standalone Messaging configuration. > ----------------------------------- > > Key: JBMESSAGING-26 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Fix For: 2.0.0 Beta 1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. > Must have at least the JNDI server, Logging, Remoting and AOP support. > We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-222) Run "findbugs" on the code base

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-222?page=all ] Tim Fox updated JBMESSAGING-222: -------------------------------- Fix Version/s: Unscheduled (was: 2.0.0 Beta 1) > Run "findbugs" on the code base > ------------------------------- > > Key: JBMESSAGING-222 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-222 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Attachments: build.xml, findbugs-0.9.5.zip, findbugs.patch, findbugs.patch, report-fb.xml > > > Run "findbugs" or similar regularily on the code base. Integrate it in the continous build process. -- 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

18 years, 11 months

1
0
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 August 2007