May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMICROCONT-126) ProxyMapCreator does not handle default annotation values

by Adrian Brock (JIRA)

ProxyMapCreator does not handle default annotation values --------------------------------------------------------- Key: JBMICROCONT-126 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-126 Project: JBoss MicroContainer Issue Type: Task Components: General Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Assigned To: Kabir Khan There is a fixme in ProxyMapCreator that says "//TODO: Need to handle default values for annotations in jdk 1.5" -- 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: (JBMICROCONT-124) Fixme in test org.jboss.test.classinfo.support.AnnotatedSubClass

by Adrian Brock (JIRA)

Fixme in test org.jboss.test.classinfo.support.AnnotatedSubClass ---------------------------------------------------------------- Key: JBMICROCONT-124 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-124 Project: JBoss MicroContainer Issue Type: Task Components: General Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Assigned To: Kabir Khan Priority: Minor There is a FIXME in the above class. Kabir can you update this task to describe the problem. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-154) Improved lifecycle events

by Kabir Khan (JIRA)

Improved lifecycle events ------------------------- Key: JBMICROCONT-154 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-154 Project: JBoss MicroContainer Issue Type: Task Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: JBossMC_2_0_0 Beta3 -- 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: (JBMICROCONT-109) Support direct registration of beans without a StandardMBean wrapper

by Brian Stansberry (JIRA)

Support direct registration of beans without a StandardMBean wrapper -------------------------------------------------------------------- Key: JBMICROCONT-109 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-109 Project: JBoss MicroContainer Issue Type: Sub-task Components: General Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossMC_2_0_0 Beta If a bean is already a valid MBean, it should be possible to directly register it in JMX without wrapping it in a StandardMBean. Otherwise beans that implement things like MBeanRegistration, NotificationBroadcaster, NotificationEmitter will not expose that API to the mbean server. To support this, @JMX will add an attribute: boolean registerDirectly() default false; JMXIntroduction will check the attribute; if true the target bean will be registered directly; otherwise a StandardMBean will be created and registered. -- 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

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

19 years

4
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1091) CMS UI : order : for lists of languages, folders, files names

by Antoine Herzog (JIRA)

CMS UI : order : for lists of languages, folders, files names ------------------------------------------------------------- Key: JBPORTAL-1091 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1091 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Environment: JBoss Portal 2.4, WXP, CMS repository in filesystem, Reporter: Antoine Herzog Assigned To: Roy Russo Priority: Minor In the CMS UI, the ordering of the folders and the files names is "Date of creation". Wish : the ordering by names (more convenient to work). even better : feature to choose the ordering on name, dates, description (second priority). In the list of languages, when you use it with another user language than english, the list is in a very messy order : I guess it is the order of the languages names in english, but showed in the "other language". example : "english" is written "anglais" and can be found after "grec" (greek) and before "esperanto". solution : order the list with the i18n label of each items. even better : propose in top of list the few languages that are supported by the portal. propose a one (or a few) strategie(s) of ordering. -- 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

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-753) Engine allows more than one rule with same name

by Marcos Tengelmann (JIRA)

Engine allows more than one rule with same name ----------------------------------------------- Key: JBRULES-753 URL: http://jira.jboss.com/jira/browse/JBRULES-753 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.5 Environment: Any OS. Reporter: Marcos Tengelmann Assigned To: Mark Proctor Engine allows more than one rule with same name. This leads to unpredicatable behavior, but one thing for sure. Wrong resutls. This is not an easy problem to identify, althrought is quite simple to solve once it is found. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBRULES-549) Better support for linebreaks in LHS

by Dirk Bergstrom (JIRA)

Better support for linebreaks in LHS ------------------------------------ Key: JBRULES-549 URL: http://jira.jboss.com/jira/browse/JBRULES-549 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 have some rules with very long LHS expressions. I'd like to split them across multiple lines for readability. However, the parser has limited support for breaks. These work: when ObjectTypeName( p0_exit_epoch > (RUM.now()), p0_exit_epoch > (RUM.daysAgo(7)) ) variable : OtherObjectType($rlis : rlis -> (RUM.countFieldsMatching($rlis, "state", "dev-maybe") > 0)) These don't: variable : OtherObjectType($rlis : rlis -> (RUM.countFieldsMatching($rlis, "state", "dev-maybe") > 0)) variable : OtherObjectType(($rlis : rlis -> (RUM.countFieldsMatching($rlis, "state", "dev-maybe") > 0)) variable : OtherObjectType($rlis : rlis -> (RUM.countFieldsMatching($rlis, "state", "dev-maybe") > 0)) While I'm at it, I'd love to have support for multiline expressions in DSL files, but I can imagine that would be a bit harder... -- 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

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-782) Bug if you modify a fact without notifying the engine and then call workingmemory getFactHandle

by Mark Proctor (JIRA)

Bug if you modify a fact without notifying the engine and then call workingmemory getFactHandle ----------------------------------------------------------------------------------------------- Key: JBRULES-782 URL: http://jira.jboss.com/jira/browse/JBRULES-782 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.1-m1 Reporter: Mark Proctor Assigned To: Mark Proctor If a pojo is modified and working memory .getFactHandle() is called which causes the hashcode to change, then we won't be able to retrieve the fact handle. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBRULES-859) Switching off alpha node sharing changes rule behaviour

by Shahad Ahmed (JIRA)

Switching off alpha node sharing changes rule behaviour ------------------------------------------------------- Key: JBRULES-859 URL: http://jira.jboss.com/jira/browse/JBRULES-859 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 4.0.0.MR2 Environment: Windows XP SP2, Intel x86 Pentium 4 3.0MHz, 1Gb RAM Reporter: Shahad Ahmed Assigned To: Mark Proctor In release 4.0MR2, switching off alpha node sharing appears to change the results produced by a set of rules. I'll illustrate the behaviour with the two rules "First" and Second" defined below. Both rules work with a class Customer, which is a simple object with an attribute age. rule "First" salience 10 when c: Customer(age <= 10) then System.out.println("First - Customer age less than 10"); end rule "Second" salience 5 when c: Customer(age <= 10) then System.out.println("Second - Customer age less than 10"); end For the default case where alpha node sharing is on, I assert a customer with age 5 and fireAllRules to get the following (hopefully, correct) output: First - Customer age less than 10 Second - Customer age less than 10 However, if I call setShareAlphaNodes(false) in RuleBaseConfiguration to turn off alpha node sharing I get the following output: First - Customer age less than 10 Alpha node sharing is an optimization and switching it on or off should give the same output for a set of rules. I've tried switching off alpha node sharing both directly via the API method, and using the system property option, but the behaviour is the same in both cases. Shahad -- 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
3
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