July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-894) Support for .package files in IDE

by Kris Verlaenen (JIRA)

Support for .package files in IDE --------------------------------- Key: JBRULES-894 URL: http://jira.jboss.com/jira/browse/JBRULES-894 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.0.MR2 Reporter: Kris Verlaenen Assigned To: Kris Verlaenen The builder in the IDE should also look for .package files in the same directory and take them into account -- 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

17 years

2
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-140) Configurator should check that fields/methods exist before trying to use them

by Adrian Brock (JIRA)

Configurator should check that fields/methods exist before trying to use them ----------------------------------------------------------------------------- Key: JBMICROCONT-140 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-140 Project: JBoss MicroContainer Issue Type: Bug Components: Configurator Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Assigned To: Ales Justin Fix For: JBossMC_2_0_0_CR1 Make sure the configurator is throwing reasonable error messages (not NPE) when things are null. e.g. the following method needs to check for null method info meaning there is no getter public static TargettedJoinpoint getPropertyGetterJoinPoint(boolean trace, PropertyInfo info) throws Throwable { if (trace) log.trace("Get property setter join point info=" + info); if (info == null) throw new IllegalArgumentException("Null property info"); JoinpointFactory jpf = info.getBeanInfo().getJoinpointFactory(); MethodInfo minfo = info.getGetter(); + if (minfo == null) + throw new IllegalArgumentException("Property is write only"); return getMethodJoinpoint(null, jpf, minfo.getName(), null, null); } -- 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

17 years

2
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-135) Adding support of MC metadata to JBoss5 MBeans

by Ales Justin (JIRA)

Adding support of MC metadata to JBoss5 MBeans ---------------------------------------------- Key: JBMICROCONT-135 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-135 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Ales Justin Assigned To: Ales Justin Priority: Minor Fix For: JBossMC_2_0_0_CR1 There is already some support for mixing common mbean xml and MC's xml metadata. We can try to port all the MC's metadata features that don't break backcompatibility on common mbeans metadata. -- 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

17 years

2
4
0 / 0

[JBoss JIRA] Updated: (JBRULES-346) problem auto correct hints

by Kris Verlaenen (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-346?page=all ] Kris Verlaenen updated JBRULES-346: ----------------------------------- Fix Version/s: FUTURE (was: 4.0.0.MR4) > problem auto correct hints > -------------------------- > > Key: JBRULES-346 > URL: http://jira.jboss.com/jira/browse/JBRULES-346 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Eclipse IDE > Reporter: Mark Proctor > Assigned To: Kris Verlaenen > Fix For: FUTURE > > > When you have problems it should provide some auto correct hints Obvious ones are corrrect imports. -- 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

17 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBRULES-165) Expose Editor settings in preferences window

by Kris Verlaenen (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-165?page=all ] Kris Verlaenen updated JBRULES-165: ----------------------------------- Fix Version/s: FUTURE (was: 4.0.0.MR4) > Expose Editor settings in preferences window > -------------------------------------------- > > Key: JBRULES-165 > URL: http://jira.jboss.com/jira/browse/JBRULES-165 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Eclipse IDE > Reporter: Mark Proctor > Assigned To: Kris Verlaenen > Fix For: FUTURE > > > settings like tabs and spaces need to be configurable and exposed in window->preferences. -- 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

17 years

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-551) Editing long lines in DRL editor causes screen jumping

by Dirk Bergstrom (JIRA)

Editing long lines in DRL editor causes screen jumping ------------------------------------------------------ Key: JBRULES-551 URL: http://jira.jboss.com/jira/browse/JBRULES-551 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.0.3 Reporter: Dirk Bergstrom Assigned To: Mark Proctor Priority: Minor I have a line that extends past the right edge of the window. I scroll the window over and make a change to the right side of the line (say around character 100). About a second after I quit typing, the scrollbar jumps back to the left, and the cursor (and my work) is shoved off the right side. This doesn't happen if I just move the cursor, I have to make a change. -- 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

17 years

3
3
0 / 0

[JBoss JIRA] Closed: (JBMICROCONT-40) Add a warning for ambigous signatures.

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-40?page=all ] Ales Justin closed JBMICROCONT-40. ---------------------------------- Resolution: Done We added isAssignable and isProgression which should make this more flexible. > Add a warning for ambigous signatures. > -------------------------------------- > > Key: JBMICROCONT-40 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-40 > Project: JBoss MicroContainer > Issue Type: Task > Components: BeanInfo > Affects Versions: JBossMC_1_0_0M1 > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Minor > Fix For: JBossMC_2_0_0_CR1 > > > It should at least WARN the user when a method or constructor is overridden > and the positional format of the parameters is ambigous before choosing the first one. > e.g. > public class MyBean > { > public MyBean(String); > public MyBean(Integer); > } > <constructor> > <parameter>Some value</parameter> > </constructor> > should warn the user, which they can resolve with: > <constructor> > <parameter class="java.lang.String">Some value</parameter> > </constructor> -- 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

17 years

1
0
0 / 0

[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

17 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

17 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

17 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007