September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-395) drools-repository API

by Michael Neale (JIRA)

drools-repository API --------------------- Key: JBRULES-395 URL: http://jira.jboss.com/jira/browse/JBRULES-395 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale This is the parent task for the drools-repository module and API. This covers the back end storage, using JCR, and the API over it (not the front end). All specific tasks should be sub tasks of this. -- 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-456) Nested field accessor - contributions from Patrick Niemeyer

by Michael Neale (JIRA)

Nested field accessor - contributions from Patrick Niemeyer ----------------------------------------------------------- Key: JBRULES-456 URL: http://jira.jboss.com/jira/browse/JBRULES-456 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Affects Versions: 3.0.4 Reporter: Michael Neale Assigned To: Mark Proctor Priority: Critical Fix For: 3.1-m3 Attachments: jboss-nested-asm.jar This is from Patrick Niemeyer <pat(a)pat.net>. Provides Foo(a.b.c etc). We are hoping for some more enhancements that can also do map/array access like javascript. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBAOP-287) Tighten integration with MC 2.0 once it is released

by Kabir Khan (JIRA)

Tighten integration with MC 2.0 once it is released --------------------------------------------------- Key: JBAOP-287 URL: http://jira.jboss.com/jira/browse/JBAOP-287 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha2 -- 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
10
0 / 0

[JBoss JIRA] Created: (JBCACHE-713) PojoCache when it has been detached remotely, accessing it again will throw PojoCacheAlreadyDetachedException

by Ben Wang (JIRA)

PojoCache when it has been detached remotely, accessing it again will throw PojoCacheAlreadyDetachedException ------------------------------------------------------------------------------------------------------------- Key: JBCACHE-713 URL: http://jira.jboss.com/jira/browse/JBCACHE-713 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 This is the use case here: cacheA.attach(id, pojo); p = cacheB.find(id); cacheA.detach(id); p.getName(); // this will throw PojoCacheAlreadyDetachedException -- 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: (JBMESSAGING-467) Sort out JBoss AS dependencies

by Ovidiu Feodorov (JIRA)

Sort out JBoss AS dependencies ------------------------------ Key: JBMESSAGING-467 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-467 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 Currently we've imported JBossAS in the lib area of our project to keep the project compiling. This is hardly an acceptable solution. The proper solution involves: 1) Deciding what JBossAS depenencies we need and getting rid of arificially dependencies 2) Work with AS team to identifiy the AS interfaces that need to be isolated and exposed in the repository. -- 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
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-455) CVS to SVN repository migration

by Ovidiu Feodorov (JIRA)

CVS to SVN repository migration ------------------------------- Key: JBMESSAGING-455 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-455 Project: JBoss Messaging Issue Type: Task Components: Build System Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 -- 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
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-557) Possible failure to correctly recover persistent messages on crash

by Ovidiu Feodorov (JIRA)

Possible failure to correctly recover persistent messages on crash ------------------------------------------------------------------ Key: JBMESSAGING-557 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-557 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Persistence Affects Versions: 1.0.1.CR5, 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta1 Created based a forum report that describes failure to correctly recover persistent messages after server failure. Need to create a specialized test and investigate. Forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974282 -- 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, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (JBRULES-439) Feature request for the rule parser / compiler that would make the code in the eclipse IDE easier

by Kris Verlaenen (JIRA)

Feature request for the rule parser / compiler that would make the code in the eclipse IDE easier ------------------------------------------------------------------------------------------------- Key: JBRULES-439 URL: http://jira.jboss.com/jira/browse/JBRULES-439 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Kris Verlaenen Assigned To: Mark Proctor This JIRA explains what improvements to the DRL parser could be very useful in the IDE. Currently, the eclipse IDE uses the rule parser to - create an outline view based on the PackageDescr returned when parsing the DRL file - retrieve all imports, all functions, all queries, all templates and the package of a DRL file (so they can be used later, for example when performing auto-completion) - determine the location of the cursor when requesting auto-completion (the part of the rule before the cursor is parsed, and based on the (unsually partically incomplete) PackageDescr returned by the parser, I try to determine in what kind of location the cursor is situation, e.g. the beginning of a column constraint, or inside an eval statement) - retrieve all parameters defined in a rule (possibly before a certain location) when auto-completion has been requested - retrieve errors and warnings that signal certain syntax errors in the DRL file Other places were the results of the DRL parser could be used: - determine which element is selected based on a character selection range - provide real-time syntax checking - determine what has changed after the DRL has been changed - do refactoring - automatic error solving Although the info returned by the parser is very useful, I think we are kind of reaching the boundary of what we can do with the info that is currently returned. I'll try to describe possible enhancements that could allow us to do more advanced IDE features as well. * Use of character number in addition with line number + column Eclipse uses character numbers instead of line + column numbers in almost all situations. A character number describes at which location a certain character occurs since the beginning of the file (and not like column since the beginning of the line). Although we could try to create a mapping between character number and line + column number, this has resulted in some annoying errors related to the newline character which is different on different platforms. Using character numbers would eliminate this problem. * All elements in the PackageDescr should have a start location Currently, most do (PatternDescr has a getLine() and getColumn()), but some elements in the PackageDescr returned by the parser still don't: - FunctionDescr has no line and column - imports are just strings - the package has no location To be able to use this information for more advanced features, it would be necessary that all elements contain a start location (now the IDE usually does additional parsing to determine the location of these elements). * All elements should also have an end location Although PatternDescr has a getEndLine() and getEndColumn(), currently, only the end location of ColumnDescr is stored (thx mic for adding this already since it was necessary for code completion). To be able to use this information for more advanced features, it would be necessary that all elements contain an end location (now the IDE usually does additional parsing to determine the end location of these elements). * For nested elements, this should be the same as much as possible Like RuleDescr contains ColumnDescr contains FieldConstraintDescrs, each of these elements should contain a start and end location (where the start and end of the sub-descriptions are of course located inside the start and end location of its parent. I believe that this is already working quite well in the current implementation for the start location of elements. * The parser should return as much info as possible, even if the rule is incomplete This is very important since the DrlParser is used a lot when the DRL is not yet completely finished (for example when performing auto-completion). It would be crucial that the parser does not just return an error when it encounters an error, but tries to parse the remainder of the file as well, and tries to return as much info as possible. For example, when trying to parse the following incomplete rule: rule MyRule MyClass ( the parser should ideally return a RuleDescr with name MyRule, containing as lhs one ColumnDescr, with name MyClass, a start location, but no end location (since the end of the ColumnDescr has not been reached yet, since the closing bracket is missing). This used to work like this in the 3.0.x release. I have noticed though that the 3.1 branch now returns null as only sub-description. Similarly, when using an eval, currently the EvalDescr is only added to the RuleDescr once the eval has been closed. As a result, the IDE has to redo a lot of parsing to check for these situations as well. If the parser always returns as much info as available (by for example adding subdescr once they are started, not only when they are finished), the IDE would not have to do as much parsing itself. * All errors and warnings try to give exact locations in the drl Although previous improvements have made the errors returned by the parser already very useful, more precise feedback could be given when the exact location of the errors could be returned, preferably as character start and end, but line numbers can be used here as well. Currently, the error is mostly indicated on the start line of the rule that contains the error. More precise error determination is necessary for more precise error visualization, automatic error solving, etc. I hope this kind of explains what improvements to the parser could be very useful to the IDE and why. -- 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, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-372) QueryResult.get fires ClassCastException when using the string argument

by Giovanni Cuccu (JIRA)

QueryResult.get fires ClassCastException when using the string argument ----------------------------------------------------------------------- Key: JBRULES-372 URL: http://jira.jboss.com/jira/browse/JBRULES-372 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss Rules 3.0.1 and JBoss Rules as downloaded from svn trunk as of 12/07/06 Reporter: Giovanni Cuccu Assigned To: Mark Proctor here is the simple test case: package simpletest; public class AssertedObject { private String value; public String getValue() { return value; } public void setValue(String value) { this.value = value; } public AssertedObject(String value) { // TODO Auto-generated constructor stub this.value = value; } } package simpletest; import simpletest.AssertedObject; rule rule1 when then assert( new AssertedObject( "value1") ); assert( new AssertedObject( "value2") ); end query "assertedobjquery" assertedobj : AssertedObject( value=="value1" ) end package simpletest; import java.io.InputStreamReader; import java.util.HashMap; import java.util.Iterator; import java.util.Map; import mit.rules.test.Prestazione; import mit.rules.test.StrutturaErogante; import mit.rules.test.TempiAttesa; import mit.rules.test.TestRules; import org.drools.QueryResult; import org.drools.QueryResults; import org.drools.RuleBase; import org.drools.RuleBaseFactory; import org.drools.WorkingMemory; import org.drools.audit.WorkingMemoryFileLogger; import org.drools.compiler.PackageBuilder; public class TestQuery { public static void main(String[] args) throws Exception { // TODO Auto-generated method stub final PackageBuilder builder = new PackageBuilder(); builder.addPackageFromDrl( new InputStreamReader( TestQuery.class.getResourceAsStream( "testquery.drl" ) ) ); final RuleBase ruleBase = RuleBaseFactory.newRuleBase(); ruleBase.addPackage( builder.getPackage() ); final WorkingMemory workingMemory = ruleBase.newWorkingMemory(); fireRules(workingMemory); } public static void fireRules(WorkingMemory workingMemory) { final WorkingMemoryFileLogger logger = new WorkingMemoryFileLogger( workingMemory ); logger.setFileName( "log/testquery" ); workingMemory.fireAllRules(); QueryResults results = workingMemory.getQueryResults( "assertedobjquery" ); if (results==null || !results.iterator().hasNext()) { System.err.println("Empty list"); } else { for ( Iterator it = results.iterator(); it.hasNext(); ) { QueryResult result = ( QueryResult )it.next();; AssertedObject assertedObject=(AssertedObject)result.get( "assertedobj" ); System.out.println("AssertedObject with value " + assertedObject.getValue()); } } logger.writeToDisk(); } } -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-700) add ability to add descriptions to jmx operations in Service beans

by William DeCoste (JIRA)

add ability to add descriptions to jmx operations in Service beans ------------------------------------------------------------------ Key: EJBTHREE-700 URL: http://jira.jboss.com/jira/browse/EJBTHREE-700 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC8 - FD Reporter: William DeCoste Assigned To: William DeCoste -- 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, 4 months

2
1
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