2025

January

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2014

jboss-jira@lists.jboss.org

1 participants
1208 discussions

Start a nNew thread

[JBoss JIRA] (WFLY-3362) Properly cancel active mgmt operation on channel close

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3362?page=com.atlassian.jira.plugin.... ] Brian Stansberry reopened WFLY-3362: ------------------------------------ Fix introduces a client-side race during ops like reload or shutdown that result in closing the channel. > Properly cancel active mgmt operation on channel close > ------------------------------------------------------ > > Key: WFLY-3362 > URL: https://issues.jboss.org/browse/WFLY-3362 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: 9.0.0.Alpha1 > > > Active mgmt operation don't get properly cancelled if there is no associated pending request and the remoting channel gets closed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-112) Allow join constraints in sliding windows

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-112?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-112: ------------------------------------------ Fix Version/s: 6.1.0.CR1 (was: 6.1.0.Beta4) > Allow join constraints in sliding windows > ----------------------------------------- > > Key: DROOLS-112 > URL: https://issues.jboss.org/browse/DROOLS-112 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.Alpha9, 6.0.0.Beta1 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 6.1.0.CR1 > > > When using a sliding window, alpha constraints are evaluated before the window is considered, but beta (join) constraints are evaluated afterwards. > While it does not usually make a difference when time windows are concerned, > it DOES make a difference with length windows. > Imho, a clear warning should be added in the documentation to clarify > the current behavior. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-88) Support generics in declared types' fields

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-88?page=com.atlassian.jira.plugin.... ] Michael Biarnes Kiefer updated DROOLS-88: ----------------------------------------- Fix Version/s: 6.1.0.CR1 (was: 6.1.0.Beta4) > Support generics in declared types' fields > ------------------------------------------ > > Key: DROOLS-88 > URL: https://issues.jboss.org/browse/DROOLS-88 > Project: Drools > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Minor > Fix For: 5.5.1.Final, 6.1.0.CR1 > > > It should be possible to write: > declare Foo > list : List<String> > end > While not supported in rules using the mvel dialect, it makes declared types much more readable, and adds some type-safety to java rules. > Notice that this ticket is NOT related to the possibility of declaring generic classes, such as Foo<T>. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-316) Arbitrary Conflict Resolution can be confusing use LoadOrder

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-316?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-316: ------------------------------------------ Fix Version/s: 6.1.0.CR1 (was: 6.1.0.Beta4) > Arbitrary Conflict Resolution can be confusing use LoadOrder > ------------------------------------------------------------ > > Key: DROOLS-316 > URL: https://issues.jboss.org/browse/DROOLS-316 > Project: Drools > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-201) Improve Rule Removal

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-201?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-201: ------------------------------------------ Fix Version/s: 6.1.0.CR1 (was: 6.1.0.Beta4) > Improve Rule Removal > -------------------- > > Key: DROOLS-201 > URL: https://issues.jboss.org/browse/DROOLS-201 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-198) Separate Rete and Phreak

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-198?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-198: ------------------------------------------ Fix Version/s: 6.1.0.CR1 (was: 6.1.0.Beta4) > Separate Rete and Phreak > ------------------------ > > Key: DROOLS-198 > URL: https://issues.jboss.org/browse/DROOLS-198 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-115) Add support for strong negation

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-115?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-115: ------------------------------------------ Fix Version/s: 6.1.0.CR1 (was: 6.1.0.Beta4) > Add support for strong negation > ------------------------------- > > Key: DROOLS-115 > URL: https://issues.jboss.org/browse/DROOLS-115 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Minor > Fix For: 6.1.0.CR1 > > > Drools "not" operator implements a type of "negation by failure", i.e. not X() behaves as the negation of "exists" or, in other words, translates as "it is NOT asserted that ...". > However, another form of stronger negation is needed to express conditionals such as "it is asserted that NOT ..." > It should be possible, then, to assert facts both in a "positive" and "negative" way, to assert THAT and THAT NOT. > The language should also support a "neg" CE to create "negative" patterns which will match with negative facts. I.e. it should be possible to write rules such as: > when $p : Person() and Car( owner == $p ) then > // a positive, matching Car is present in the WM > when $p : Person() and neg Car( owner == $p ) then > // a negative, matching Car is present in the WM > when $p : Person() and not Car( owner == $p ) then > // neither a positive nor a negative fact exists in the WM > For a more detailed description and motivation see e.g.: > https://oxygen.informatik.tu-cottbus.de/publications/wagner/WebRules2Neg.pdf -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-432) Types declared in a foreign package are processed one at a time

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-432?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-432: ------------------------------------------ Fix Version/s: 6.1.0.CR1 (was: 6.1.0.Beta4) > Types declared in a foreign package are processed one at a time > --------------------------------------------------------------- > > Key: DROOLS-432 > URL: https://issues.jboss.org/browse/DROOLS-432 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mark Proctor > Fix For: 6.1.0.CR1 > > > The following snippet has two issues > {code} > package a; > declare b.X field : b.Y end > declare b.Y end > {code} > While processing package a, the packageBuilder will infer the existence of package b and create the appropriate typeDeclarations. > However, a partial, independent package b is created for X and Y: > - it is inefficient > - internal dependencies cannot be resolved : b.X does not (yet) see b.Y -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-332) Space Invaders and Number Guess Game

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-332?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-332: ------------------------------------------ Fix Version/s: 6.1.0.CR1 (was: 6.1.0.Beta4) > Space Invaders and Number Guess Game > ------------------------------------ > > Key: DROOLS-332 > URL: https://issues.jboss.org/browse/DROOLS-332 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3185) Strip cluster name from node names

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-3185?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-3185: ------------------------------------ Including the cluster name in the node name will become especially redundant when we integrate fork channels and allow each cache container to share the same channel. > Strip cluster name from node names > ---------------------------------- > > Key: WFLY-3185 > URL: https://issues.jboss.org/browse/WFLY-3185 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > Currently, we generate cluster node names using the following format: > node-name/cluster-name > Including the cluster-name in the node name is redundant and only serves to add unnecessary bytes to messages. > We just need to make sure to include the cluster name in any log messages that refer to the node name. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

Jump to page: