May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBRULES-231) add "not contains" constraint

by Michael Neale (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-231?page=all ] Michael Neale reassigned JBRULES-231: ------------------------------------- Assignee: Edson Tirelli (was: Michael Neale) > add "not contains" constraint > ----------------------------- > > Key: JBRULES-231 > URL: http://jira.jboss.com/jira/browse/JBRULES-231 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Drl Parser/Builder > Reporter: Michael Neale > Assigned To: Edson Tirelli > Fix For: 4.0.0.MR2 > > > Person(addresses not_contains foo) > simple extension to the contains feature for collections. > Any other sytax ideas? > Person(something !contains foo) > Person(something !<< foo) > Person(something << foo) > I prefer as natural as possible... -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-577) Please add "contained by" syntax for constraints

by Dirk Bergstrom (JIRA)

Please add "contained by" syntax for constraints ------------------------------------------------ Key: JBRULES-577 URL: http://jira.jboss.com/jira/browse/JBRULES-577 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Dirk Bergstrom Assigned To: Mark Proctor I'd like to be able to write a constraint to determine if a field's value is a member of some collection. This is the inverse of the "contains" keyword. The proposed syntax is: [bindingVar :] <fieldName> in <someCollection> (I'm not picky about the keyword, other possibilities are "containedBy" or "memberOf", but "in" is a single word) Use case: I have a container class with a field that exposes a collection of record numbers. In the working memory, I have a bunch of record objects, and one container object. I want to write a rule that fires when it encounters a container that has records matching some criteria: when Container( $recordNums : records ) Record( number in $recordNums, otherField == "somevalue" ) then doStuff(); The current workaround is: Record( num : number -> ( $recordNums.contains(num) ) ) Which is problematic, as the predicate may not be time-constant. -- 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

19 years

5
7
0 / 0

[JBoss JIRA] Reopened: (JBRULES-231) add "not contains" constraint

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-231?page=all ] Edson Tirelli reopened JBRULES-231: ----------------------------------- "not contains" was not implemented, since we have "excludes". Do you want me to add "not contains" as a synonym for "excludes"? > add "not contains" constraint > ----------------------------- > > Key: JBRULES-231 > URL: http://jira.jboss.com/jira/browse/JBRULES-231 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Drl Parser/Builder > Reporter: Michael Neale > Assigned To: Michael Neale > Fix For: 4.0.0.MR2 > > > Person(addresses not_contains foo) > simple extension to the contains feature for collections. > Any other sytax ideas? > Person(something !contains foo) > Person(something !<< foo) > Person(something << foo) > I prefer as natural as possible... -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-22) Concurrency bug in JaasSecurityManager

by Alex Besogonov (JIRA)

Concurrency bug in JaasSecurityManager -------------------------------------- Key: SECURITY-22 URL: http://jira.jboss.com/jira/browse/SECURITY-22 Project: JBoss Security Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Alex Besogonov Assigned To: Anil Saldhana JaasSecurityManager$DomainInfo.destroy calls logout() when cached entry expires, even while it is used by another thread. Suppose we have two threads: Thread 1: 1. 'User1' authentication 2. 'User1' is added to auth cache 3. Doing some lengthy operation 4. Checking roles of User1 - WILL FAIL, another thread has called logout()! Thread 2 (when Thread1 is doing 'some lengthy operation' ): 1. 'User1' logs in. 2. Auth cache entry has expired. 3. Calling .logout() on stale entry -- 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

19 years

2
2
0 / 0

[JBoss JIRA] Created: (GPD-57) nullpointer while deleting start state

by Tom Baeyens (JIRA)

nullpointer while deleting start state -------------------------------------- Key: GPD-57 URL: http://jira.jboss.com/jira/browse/GPD-57 Project: JBoss jBPM GPD Issue Type: Bug Reporter: Tom Baeyens Assigned To: Koen Aers -- 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

19 years

3
7
0 / 0

[JBoss JIRA] Updated: (GPD-3) implement a generation mechanism for the new task forms

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/GPD-3?page=all ] Koen Aers updated GPD-3: ------------------------ Fix Version/s: (was: jBPM JPDL Designer 3.1.0.beta1) > implement a generation mechanism for the new task forms > ------------------------------------------------------- > > Key: GPD-3 > URL: http://jira.jboss.com/jira/browse/GPD-3 > Project: JBoss jBPM GPD > Issue Type: Task > Components: jpdl > Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 > Reporter: Koen Aers > Assigned To: Koen Aers > -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (GPD-71) Provide pluggability of assignment handlers

by Koen Aers (JIRA)

Provide pluggability of assignment handlers ------------------------------------------- Key: GPD-71 URL: http://jira.jboss.com/jira/browse/GPD-71 Project: JBoss jBPM GPD Issue Type: Feature Request Affects Versions: jBPM JPDL Designer 3.1.0.alpha3 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.beta1 It should be possible to plug in different types of assignment handlers and to enable/disable these through the preferences settings. -- 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

19 years

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-117) Breaking up the MC project and Mavenizing it

by Ales Justin (JIRA)

Breaking up the MC project and Mavenizing it -------------------------------------------- Key: JBMICROCONT-117 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-117 Project: JBoss MicroContainer Issue Type: Task Components: General Reporter: Ales Justin Assigned To: Ales Justin Priority: Minor Fix For: JBossMC_2_0_0_CR1 -- 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

19 years

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1387) Build (distrib.xml) should not force your source directory to be "jboss-portal-2.4"

by Galder Zamarreno (JIRA)

Build (distrib.xml) should not force your source directory to be "jboss-portal-2.4" ----------------------------------------------------------------------------------- Key: JBPORTAL-1387 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1387 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.1 SP1, 2.4.1 Final Reporter: Galder Zamarreno This is the path were I have retrieved the source code for Portal 2.4.1: /home/galder/jboss/code/portal/rel/2.4.1/ I have built portal with ./build.sh and I'm now trying to build an HA distribution with: ./build.sh -f distrib.xml source.build However, it fails with: /home/galder/jboss/code/portal/rel/2.4.1/build/distrib.xml:59: Basedir /home/galder/jboss/code/portal/rel/jboss-portal-2.4/build does not exist This comes from: <property name="source.dir" value="../../jboss-portal-2.4/"/> Any reason why this couldn't just be: <property name="source.dir" value="../"/> -- 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

19 years

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1382) Switching into, out of and back into Wizard Mode in the admin portlet doesn't reset the step state properly

by Chris DeLashmutt (JIRA)

Switching into, out of and back into Wizard Mode in the admin portlet doesn't reset the step state properly ----------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1382 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1382 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.CR2 Reporter: Chris DeLashmutt User switches into the Wizard mode of the admin portlet, navigates to a step after step one. User then clicks on "Switch to Advanced Mode", and then clicks on "Switch to Wizard Mode". The list on the screen is for Step 1, but the highlighted step at the top of the screen is the step the user first exited Wizard mode on. -- 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

19 years

3
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 May 2007