February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-613) Can't use dollar ($) char in Rule Name with Janino compiler

by Bree VanOss (JIRA)

Can't use dollar ($) char in Rule Name with Janino compiler ----------------------------------------------------------- Key: JBRULES-613 URL: http://jira.jboss.com/jira/browse/JBRULES-613 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.5 Environment: Verified on WinXP and OS X Reporter: Bree VanOss Assigned To: Mark Proctor Priority: Minor Essentially it appears that any rule using the U.S. Dollar character ($) in the rule name fails when compiled with Janino. I was able to reproduce the issue using the "default" new JBoss-rules project wizard in Eclipse. The stack trace follows, though it may not be much help. I tried tracking it down and it looks like the problem is actually caused in the parse/compilation step (i.e. builder.addPackageFromDrl( source );). After this step the rule in question has a null "consequence", which causes the "AbstractRuleBase.addRule(...)" method to fail when it does the isValid() check. <code> java.lang.IllegalArgumentException: The rule called Show me da $ is not valid. Check for compile errors reported. at org.drools.common.AbstractRuleBase.addRule(Unknown Source) at org.drools.reteoo.ReteooRuleBase.addRule(Unknown Source) at org.drools.common.AbstractRuleBase.addPackage(Unknown Source) at com.sample.DroolsTest.readRule(DroolsTest.java:89) at com.sample.DroolsTest.main(DroolsTest.java:29) </code> -- 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 month

3
5
0 / 0

[JBoss JIRA] Created: (SECURITY-23) NullPointerException in JaasSecurityManager.getPrincipal()

by Alex Besogonov (JIRA)

NullPointerException in JaasSecurityManager.getPrincipal() ---------------------------------------------------------- Key: SECURITY-23 URL: http://jira.jboss.com/jira/browse/SECURITY-23 Project: JBoss Security Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Alex Besogonov Assigned To: Anil Saldhana JaasSecurityManager.getPrincipal() does not check for empty domainCache. This method is called, for example, when JAAS is used from web layer. Trivial fix, add in the start of the method: if( domainCache == null ) return principal; -- 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 month

2
5
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, 1 month

5
7
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, 1 month

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, 1 month

3
7
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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-495) Allows for automatic meta data gathering during rule/rule package saves to repository

by Marcos Tengelmann (JIRA)

Allows for automatic meta data gathering during rule/rule package saves to repository ------------------------------------------------------------------------------------- Key: JBRULES-495 URL: http://jira.jboss.com/jira/browse/JBRULES-495 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Reporter: Marcos Tengelmann Assigned To: Mark Proctor Priority: Optional In order to make search easy as possible, we would like to have automatic meta data collected during the process of importing rules from files or during the save process from UI, to repository back end. The whole idea here is to keep the concept of Category only for business purposes. Besides the category concept , we could have attributes set into the repository attached with its components. With that we mean, that we could automatically (The saver to repository is a suggesiton on doing this), to extract Columns (Could be OTN also?) from rules, and create lists of all column types a given rule uses and even other type of data could be extracted from rule files and definitions With that we could be able to link in searches, business desciptions and categories to real implementation, giving very usefull results (A Better search engine than Google).... -- 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 month

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-955) Use globally unique (i.e. prefixed by org.jboss.portal for ex.) session/invocation attribute names to avoid collisions.

by Chris Laprun (JIRA)

Use globally unique (i.e. prefixed by org.jboss.portal for ex.) session/invocation attribute names to avoid collisions. ----------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-955 URL: http://jira.jboss.com/jira/browse/JBPORTAL-955 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.6 Final -- 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 month

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1161) Attempting to logout if the session has expired prompts you to log in...

by Chris Laprun (JIRA)

Attempting to logout if the session has expired prompts you to log in... ------------------------------------------------------------------------ Key: JBPORTAL-1161 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1161 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6.DR1 Reporter: Chris Laprun Fix For: 2.6 Final -- 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 month

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-471) Add support for "from" keyword

by Kris Verlaenen (JIRA)

Add support for "from" keyword ------------------------------ Key: JBRULES-471 URL: http://jira.jboss.com/jira/browse/JBRULES-471 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Content completion should be able to handle the from keyword. -- 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 month

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 February 2007