July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-973) Add code completion support for new 4.0 features

by Kris Verlaenen (JIRA)

Add code completion support for new 4.0 features ------------------------------------------------ Key: JBRULES-973 URL: http://jira.jboss.com/jira/browse/JBRULES-973 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.0.MR3 Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Add support in code completion for the following new features: - the use of 'this' in pattern constraints - the use of '[ ]' for maps - nested properties in pattern constraints (e.g. person.name.firstname) - new accumulate functions - forall - complex use of && and || in pattern constraints -- 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: (JBRULES-567) Rules View

by Kris Verlaenen (JIRA)

Rules View ---------- Key: JBRULES-567 URL: http://jira.jboss.com/jira/browse/JBRULES-567 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kris Verlaenen Assigned To: Kris Verlaenen A rules view shows all known rules / queries / functions / globals in the workspace, structured in packages, and it allows filtering and navigation by double clicking a rule. -- 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] Resolved: (JBRULES-14) AuditEventListener

by Kris Verlaenen (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-14?page=all ] Kris Verlaenen resolved JBRULES-14. ----------------------------------- Fix Version/s: 3.0.6 (was: 4.0.0.MR4) Resolution: Done > AuditEventListener > ------------------ > > Key: JBRULES-14 > URL: http://jira.jboss.com/jira/browse/JBRULES-14 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Eclipse IDE, Reteoo > Reporter: Mark Proctor > Assigned To: Kris Verlaenen > Fix For: 3.0.6 > > Attachments: screenshot-1.jpg > > > The event model is split into 3. WorkingMemory, Reteoo, Agenda. > The WorkingMemory has three events > ObjectAsserted > ObjectRetracted > ObjectModified > The Agenda has 4 events > BeforeActivationFire > AfterActivationfired > ActivationCreated > ActivationCancelled > All events take a PropagationContext - this tells you if the event was the result of an assertion, retraction or modification, it also tells you what the parent rule/activation was. > You can use all this information to display a very useful tree. > We create two new listeners AgendaAuditListener and WorkingMemoryAuditListener - a WorkingMemory listener is useless without the Agenda one being added. Each time when BeforeActivationFired fires we attach the event to the tree, as we know the parent from the PropagationContext. If the parent is null then we know there was a WorkingMemory action (assert, retract, modify) from outside of a rule. So this allows us to create a tree view of activation firing. > Second to this we should make it possible to record all asserted, retracted and mofied objects during the evaluation of the Consequence. This is simply a matter of hooking into each WM event and attaching it to the Activation in the tree, or possibly the WM action in the tree. > If users just add the AgendaAuditView all it does is record the activation firing, if they add the WorkingMemoryAuditListener it by default captures all three events - but we allow users to specify which ones it captures, if they want. Secondly to this the view itself should allow users to hide and show some events, ofcourse if that event was not captured they should not be able to show it. > To create the Activation Tree I would do the following. + shows it has children - shows it doesn't. > +ActivationFired > + Assertion > -ActivationCreated > +ActivationCreated > +ActivationFired ..... > ..... > -Assertion > +Retraction > -ActivationCancelled > -ActivationCancelled > When users select the ActivationCancelled event it can show where the ActivationCreated was added, and vice versa. > However if we do not capture WM events then the activations should just be attached to the parent Activation > ActiationFired > +ActivationCreated > -ActivationFired > -ActivationCreated > -ActivationCancelled > Secondly we will need to implement a system to capture the relevant info. A range of options are possible here, a simple "toString" capture, using the cloneable interface, serialisation, the Memento snapshop pattern or maybe some sort of JavaBean wrapper around a hashmap. -- 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
0
0 / 0

[JBoss JIRA] Commented: (JBMICROCONT-25) Configurator tidyup

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=comments#action_123... ] Ales Justin commented on JBMICROCONT-25: ---------------------------------------- One existing FIXME: The isAssignable and isProgression currently needs a classloader to work properly, use the bean's classloader if there isn't one provided. > Configurator tidyup > ------------------- > > Key: JBMICROCONT-25 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25 > Project: JBoss MicroContainer > Issue Type: Task > Components: Configurator > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Minor > Fix For: JBossMC_2_0_0_CR1 > > > The Configurator api is largely being replaced by the JoinPointFactory api. > There is still a usecase for some of the Configurator api as a convenience mechanism > on top of the JoinPointFactory. > This needs cleaning up. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBRULES-711) Ruleflow IDE integration

by Kris Verlaenen (JIRA)

Ruleflow IDE integration ------------------------ Key: JBRULES-711 URL: http://jira.jboss.com/jira/browse/JBRULES-711 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Fix For: 3.1-m2 -- 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: (JBRULES-712) Rule Flow Compiler Implementation

by Kris Verlaenen (JIRA)

Rule Flow Compiler Implementation --------------------------------- Key: JBRULES-712 URL: http://jira.jboss.com/jira/browse/JBRULES-712 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Fix For: 3.1-m2 -- 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-699) syntactically correct rule files are marked with errors

by Dr. Gernot Starke (JIRA)

syntactically correct rule files are marked with errors ------------------------------------------------------- Key: JBRULES-699 URL: http://jira.jboss.com/jira/browse/JBRULES-699 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.0.5, 3.0.4 Environment: Eclipse 3.2, both on Mac OS X and Windows XP Reporter: Dr. Gernot Starke Assigned To: Mark Proctor Although rule-files are syntactically correct (tutorial example), parser within Eclipse plugin marks them as erroneous. Deleting the rule, re-typing it in editor resolves the problem. Example (displays error in eclipse package explorer): #created on: 14.02.2007 package com.sample.business #list any import classes here. import com.sample.Person; import java.util.ArrayList; #declare any global variables here global ArrayList zorglist; rule "erwachsene Person bekommt Kredit" when person: Person( age >= 18 ) then System.out.println("Erwachsener in Sicht: " + person.getName()); zorglist.add( person.getName()); end rule "no credit" when Person( personName : name, age < 18) then System.out.println( "denied for " + personName ); end -- 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] Closed: (JBMICROCONT-24) Glossary of terms

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-24?page=all ] Ales Justin closed JBMICROCONT-24. ---------------------------------- Resolution: Done Added a section 'glossary' in the User Guide which will cover the basic terms, buzz words, ... > Glossary of terms > ----------------- > > Key: JBMICROCONT-24 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-24 > Project: JBoss MicroContainer > Issue Type: Task > Components: General > Reporter: Adrian Brock > Assigned To: Ales Justin > Fix For: JBossMC_2_0_0_CR1 > > > Need to create a glossary of terms to avoid confusion between developers with overloaded > terms. e.g. what does container mean, what is a join point, etc. > The api should also be examined so the names are natural, expressing immediatley > to somebody who knows java beans, annotations, etc. what is happening. > e.g. attribute should be property (the java bean term rather than the jmx term) -- 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
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-127) Create Docbook for @Consumer

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-127?page=all ] Dimitris Andreadis updated EJBTHREE-127: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > Create Docbook for @Consumer > ---------------------------- > > Key: EJBTHREE-127 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-127 > Project: EJB 3.0 > Issue Type: Task > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: AS 4.2.2.GA > > -- 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
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-124) @PersistenceContext(EXTENDED) should follow new Spec defined rules

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ] Dimitris Andreadis updated EJBTHREE-124: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > @PersistenceContext(EXTENDED) should follow new Spec defined rules > ------------------------------------------------------------------ > > Key: EJBTHREE-124 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-124 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: Preview 5 > Reporter: Bill Burke > Fix For: AS 4.2.2.GA > > > I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED) -- 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
0
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 July 2007