September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-278) Make AbstractAnnotationMetaData use correct classloader for loading annotation class

by Kabir Khan (JIRA)

Make AbstractAnnotationMetaData use correct classloader for loading annotation class ------------------------------------------------------------------------------------ Key: JBAOP-278 URL: http://jira.jboss.com/jira/browse/JBAOP-278 Project: JBoss AOP Issue Type: Sub-task Reporter: Kabir Khan -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-701) PojoCache to revisit usage of get with gravitation

by Ben Wang (JIRA)

PojoCache to revisit usage of get with gravitation -------------------------------------------------- Key: JBCACHE-701 URL: http://jira.jboss.com/jira/browse/JBCACHE-701 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache Currently we have in couple places to trigger data gravitation (for buddy replication) in PojoCache. But this is still prone to error (and may be inefficient as well) becuase of the possibility of recursive call. Is it possible that we do this from the user code instead? That is, before we go to PojoCache, can we do get(region, dataGravitation) to gravitate all data to this node first? Let's check this with Brian. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-758) Add some docs for JBCACHE-77

by Brian Stansberry (JIRA)

Add some docs for JBCACHE-77 ---------------------------- Key: JBCACHE-758 URL: http://jira.jboss.com/jira/browse/JBCACHE-758 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Daniel Huang Fix For: 2.0.0 We need to add some docs for the ElementSizePolicy to the eviction policy section of the docs. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-379) function with another drools function call won't compile (either with eclipse compiler or janino)

by Thierry R (JIRA)

function with another drools function call won't compile (either with eclipse compiler or janino) ------------------------------------------------------------------------------------------------- Key: JBRULES-379 URL: http://jira.jboss.com/jira/browse/JBRULES-379 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.1 Environment: Debian linux JDK 5 Reporter: Thierry R Assigned To: Mark Proctor function with another drools function call won't compile (either with eclipse compiler or janino) with the error msg : "Function Compilation error " I wrote a DroolsHelper class to work around. -- 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, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBRULES-450) Remove testLogicalAssertionsModifyEqual() from org.drools.integrationtests.IntegrationCases, no logicalAssertMap field with new TMS

by Juergen none (JIRA)

Remove testLogicalAssertionsModifyEqual() from org.drools.integrationtests.IntegrationCases, no logicalAssertMap field with new TMS ----------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-450 URL: http://jira.jboss.com/jira/browse/JBRULES-450 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.0.4 Reporter: Juergen none Assigned To: Mark Proctor Priority: Trivial With modified reteoo working memory class, testLogicalAssertionsModifyEqual() got obsolete/invalid, always throwing NoSuchFieldException. method+drl should be removed. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-446) Support rulebase configuration via jsr94 registerRuleExecutionSet properties

by Juergen none (JIRA)

Support rulebase configuration via jsr94 registerRuleExecutionSet properties ---------------------------------------------------------------------------- Key: JBRULES-446 URL: http://jira.jboss.com/jira/browse/JBRULES-446 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JSR94 Affects Versions: 3.0.4 Reporter: Juergen none Assigned To: Mark Proctor Priority: Minor Is it possible to support rulebase configuration via jsr94 registerRuleExecutionSet properties? Suggestion: - new property in org.drools.jsr94.rules.Constants.java:41: //jh: added to support handing a rulebase config via jsr94 /** <code>RuleExecutionSet</code> rulebase config constant. */ public static final String RES_CONFIG = "javax.rules.admin.RuleExecutionSet.config"; - modification of method (probably secure against ClassCastException) org.drools.jsr94.rules.admin.RuleExecutionSetImpl.java:118:RuleExecutionSetImpl(...): //jh: support rulebase configuration via jsr94 final org.drools.reteoo.ReteooRuleBase ruleBase = new org.drools.reteoo.ReteooRuleBase((org.drools.RuleBaseConfiguration)properties.get(org.drools.jsr94.rules.Constants.RES_CONFIG), new Jsr94FactHandleFactory() ); /* final org.drools.reteoo.ReteooRuleBase ruleBase = new org.drools.reteoo.ReteooRuleBase( new Jsr94FactHandleFactory() ); */ -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-501) DRL -> decision table (round trip)

by Scott Reed (JIRA)

DRL -> decision table (round trip) ---------------------------------- Key: JBRULES-501 URL: http://jira.jboss.com/jira/browse/JBRULES-501 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Scott Reed Assigned To: Mark Proctor It would be extremely useful to be able to convert existing rules to decision tables. The educational value alone would make it worth while, but it would speed up development as well since the DRL -> decision table mapping is not straight forward and cell merging and coloring is fairly tedious. Users would probably want to be able to select the rules and functions to be mapped. If so, then the results of the mapping would have to be one or more decision table files and a new DRL file containing the rules and functions that were not converted. -- 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, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-502) Add binding semantics for decision table authors

by Scott Reed (JIRA)

Add binding semantics for decision table authors ------------------------------------------------ Key: JBRULES-502 URL: http://jira.jboss.com/jira/browse/JBRULES-502 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Scott Reed Assigned To: Mark Proctor The expressive capability of decision tables for non-programmer authors is limited. Especially, the author has no way to tell the developer to use the value of a property from one column in the condition for another. I can think of two ways that binding semantics could be added: Use the comment cells (i.e. "Age: Person's Age") - this is simple and expressive but would cause problems if an author wants to use the '<word>:' construct in a comment without intending it to be a binding. Add a designated row above or below the comment row. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-451) Allow optional trailing comma "," for field constraint list

by Juergen none (JIRA)

Allow optional trailing comma "," for field constraint list ----------------------------------------------------------- Key: JBRULES-451 URL: http://jira.jboss.com/jira/browse/JBRULES-451 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.4 Reporter: Juergen none Assigned To: Mark Proctor Priority: Optional With frequently re-arranging / adding / removing field constraints, I more than once forgot to add / remove trailing/separating commas in the field constraint list. would it be possible to extend the drools drl syntax to allow an optional trailing comma? e.g. A( a == 1, b == 2, // optional trailing comma, should not yield the syntax error ) A( a == 1, b == 2 // no (optional) trailing comma, like currently required, is also valid ) -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-427) Language Level Default to Java Specification

by Geoffrey Wiseman (JIRA)

Language Level Default to Java Specification -------------------------------------------- Key: JBRULES-427 URL: http://jira.jboss.com/jira/browse/JBRULES-427 Project: JBoss Rules Issue Type: Patch Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Geoffrey Wiseman Assigned To: Mark Proctor Attachments: drools-compiler-languageLevel.txt See the attached patch for drools-compiler that sets the language level to the same one as the runtime environment, if it's viable. Can still be overridden in code or with a system property. -- 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, 3 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006