April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1126) CMS needs to store contributing version for new versions of pages

by Alex Pinkin (JIRA)

CMS needs to store contributing version for new versions of pages ----------------------------------------------------------------- Key: JBPORTAL-1126 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1126 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Reporter: Alex Pinkin Assigned To: Roy Russo -CMS needs to store contributing version for new versions of pages (1.1 was created from 1.0, etc). To prevent locking the edit of a content item, it is useful to allow multiple drafts to be created of a content item. This situation can cause problems for approvers if there are multiple drafts needing approval. It would be helpful if approvers could see what version was the contributing version for a particular content item version. -- 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

[JBoss JIRA] Created: (JBMICROCONT-166) If bean name, dependency, demands, supplies looks like an object name, the register its canonical form

by Bill Burke (JIRA)

If bean name, dependency, demands, supplies looks like an object name, the register its canonical form ------------------------------------------------------------------------------------------------------ Key: JBMICROCONT-166 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-166 Project: JBoss MicroContainer Issue Type: Feature Request Components: Dependency Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Bill Burke Assigned To: Ales Justin Priority: Critical Fix For: JBossMC_2_0_0_CR1 See forum reference. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBRULES-573) EqualityAssertMapComparator does not work with JSR94 Fact Handles

by Juergen none (JIRA)

EqualityAssertMapComparator does not work with JSR94 Fact Handles ----------------------------------------------------------------- Key: JBRULES-573 URL: http://jira.jboss.com/jira/browse/JBRULES-573 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.5 Environment: java 1.5.0_09 Reporter: Juergen none Assigned To: Mark Proctor Equal objects are asserted multiple times via jsr94 interface Using jsr94 interface to use drools stateful rule session Assert behaviour set to equality: PROPERTY_ASSERT_BEHAVIOR = RuleBaseConfiguration.WM_BEHAVIOR_EQUALITY fact handle factory creates org.drools.jsr94.rules.Jsr94FactHandle objects BUT: org.drools.common.EqualityAssertMapComparator::hashCodeOf() obj.getClass() == this.factHandleClass is false because this.factHandleClass is DefaultFactHandle and obj.getClass() is Jsr94FactHandle --> so instead of hashcode of object wrapped by handle, hashcode of facthandle object is used --> equal objects are asserted multiple times GUESS: either - obj.getClass() instanceof this.factHandleClass or - this.factHandleClass should be set to Jsr94FactHandle? -- 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
5
0 / 0

[JBoss JIRA] Created: (JGRP-458) NAKACK: REBROADCAST_MSGS blocks forever

by Bela Ban (JIRA)

NAKACK: REBROADCAST_MSGS blocks forever --------------------------------------- Key: JGRP-458 URL: http://jira.jboss.com/jira/browse/JGRP-458 Project: JGroups Issue Type: Bug Affects Versions: 2.4.1 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 If max_rebroadcast_timeout is high, then that event never returns. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBRULES-570) Problem compiling package from xml

by Javier Prieto (JIRA)

Problem compiling package from xml ---------------------------------- Key: JBRULES-570 URL: http://jira.jboss.com/jira/browse/JBRULES-570 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: xml Affects Versions: 3.0.4 Environment: Windows XP, Eclipse 3.2, JBoss Rules IDE 3.0.4 Reporter: Javier Prieto Assigned To: Mark Proctor There is a problem compiling package from an xml rule file with rules calling functions in the rhs body. This is an example of an xml rule file that fails: <?xml version="1.0" encoding="UTF-8"?> <package name="com.sample" xmlns="http://drools.org/drools-3.0" xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" xs:schemaLocation="http://drools.org/drools-3.0 drools-3.0.xsd"> <function return-type="void" name="manageAlert"> <parameter identifier="alert" type="String"/> <body>System.out.println(alert);</body> </function> <function return-type="void" name="manageRuleFired"> <parameter identifier="ruleName" type="String"/> <body>System.out.println(ruleName + " fired");</body> </function> <rule name="Impossible Rule"> <lhs> <eval>1 == 2</eval> </lhs> <rhs>manageAlert("impossibleRule!!!"); manageRuleFired("Impossible Rule");</rhs> </rule> </package> I've found a workaround. If you insert a blank char anywhere in the first sentence of the rhs body (manageAlert(...);), it works well: <rhs>manageAlert ("impossibleRule!!!"); manageRuleFired("Impossible Rule");</rhs> (blank after manageAlert) or, <rhs>manageAlert( "impossibleRule!!!"); manageRuleFired("Impossible Rule");</rhs> (blank after '(' ) or, <rhs> manageAlert("impossibleRule!!!"); manageRuleFired("Impossible Rule");</rhs> (blank at the begining) or, <rhs>manageAlert("impossible Rule!!!"); manageRuleFired("Impossible Rule");</rhs> (blank in the string) ... If you call a Java method just before or after 'manageAlert("impossible Rule!!!");' with a blank between them, it works well too: <rhs>System.out.println("Hello"); manageAlert("impossibleRule!!!"); manageRuleFired("Impossible Rule");</rhs> <rhs>manageAlert("impossibleRule!!!"); System.out.println("Hello"); manageRuleFired("Impossible Rule");</rhs> ... I attach a test case with the xml rule file that cause the rule compilation error and the main class to test it. -- 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-553) Add newlines in parser error messages

by Dirk Bergstrom (JIRA)

Add newlines in parser error messages ------------------------------------- Key: JBRULES-553 URL: http://jira.jboss.com/jira/browse/JBRULES-553 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Reporter: Dirk Bergstrom Assigned To: Mark Proctor Priority: Minor Some kinds of parser errors get strung together on a single very long line, which makes it irritating to debug problems. This doozy is 332 characters long: org.drools.rule.InvalidRulePackage: Rule Compilation error Class "net.juniper.dash.RUM" has no method named "countPicklistFieldsComparingxTo" Instance method "countPicklistFieldsComparingxTo" cannot be invoked in static context Exception:2 errors while compiling unit "net/juniper/dash/Rule_RLIs_with_missing_func_specs_0.java" That's a lot of side-scrolling to figure out what happened. Breaking it up into four or five lines would greatly increase readability. -- 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

[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

19 years

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

19 years

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

19 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-754) For each added package coming from a DRL , ALL previously loaded rules are compiled again

by Marcos Tengelmann (JIRA)

For each added package coming from a DRL , ALL previously loaded rules are compiled again ----------------------------------------------------------------------------------------- Key: JBRULES-754 URL: http://jira.jboss.com/jira/browse/JBRULES-754 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 For each file we add to rule base using addPackageFromDRL, all previously added rules are compiled again. If we use the same pacjage builder the problem(? Is it a problem or a expected behavior?) reported happens. If we use a different packageBuilder for each file, it does not happen. -- 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 April 2007