April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-158) Constant fields that are not final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-158?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-158: ---------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 926050|https://bugzilla.redhat.com/show_bug.cgi?id=926050] Removing blocker flag based on Brian's comment. > Constant fields that are not final > ---------------------------------- > > Key: WFLY-158 > URL: https://issues.jboss.org/browse/WFLY-158 > Project: WildFly > Issue Type: Bug > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > Attachments: non-final-fields.txt > > > Analysis by Stephan Mueller shows that the AS codebase includes a significant number of public constant fields that are missing the "final" keyword, which could allow incorrect or nefarious code to change them. This task is to fix these. > As part of the work for a few cases I'll reduce the field visibility. > I'll attach file listing the cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1154) Allow the server to ignore files or groups of files at deployment time

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-1154?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-1154: --------------------------------- Assignee: (was: Stuart Douglas) Fix Version/s: Awaiting Volunteers > Allow the server to ignore files or groups of files at deployment time > ---------------------------------------------------------------------- > > Key: WFLY-1154 > URL: https://issues.jboss.org/browse/WFLY-1154 > Project: WildFly > Issue Type: Feature Request > Components: Server > Reporter: Marius Bogoevici > Fix For: Awaiting Volunteers > > > Legacy and migrated applications may occasionally contain files which are incompatible with the Java EE specification and can cause the application to fail the deployment. The difference between those cases and really faulty Java EE applications lies in the intent of the developer - whether they wish for those files to be picked up by the server and processed, or not. > In such cases, it may be useful to expand the deployment specification and to be able to instruct the server to ignore particular files at deployment time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-730) Special Characters in User Names

by Guillaume Grossetie (JIRA)

[ https://issues.jboss.org/browse/WFLY-730?page=com.atlassian.jira.plugin.s... ] Guillaume Grossetie commented on WFLY-730: ------------------------------------------ Ok cool :) > Special Characters in User Names > -------------------------------- > > Key: WFLY-730 > URL: https://issues.jboss.org/browse/WFLY-730 > Project: WildFly > Issue Type: Feature Request > Components: Scripts > Reporter: Fernando Ribeiro > Fix For: Awaiting Volunteers > > > When working with domains, I've noticed that having special characters that are valid in host names (like "-") in user names should be supported to prevent having "fake" host names configured in host.xml files and displayed in the management interfaces. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-730) Special Characters in User Names

by Fernando Ribeiro (JIRA)

[ https://issues.jboss.org/browse/WFLY-730?page=com.atlassian.jira.plugin.s... ] Fernando Ribeiro commented on WFLY-730: --------------------------------------- Yes it is, and after realizing that is the only special character valid in host names missing in that list, just submitted a pull request myself. http://tools.ietf.org/html/rfc952 > Special Characters in User Names > -------------------------------- > > Key: WFLY-730 > URL: https://issues.jboss.org/browse/WFLY-730 > Project: WildFly > Issue Type: Feature Request > Components: Scripts > Reporter: Fernando Ribeiro > Fix For: Awaiting Volunteers > > > When working with domains, I've noticed that having special characters that are valid in host names (like "-") in user names should be supported to prevent having "fake" host names configured in host.xml files and displayed in the management interfaces. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3288) Sliding time window ignored when using @timestamp and pseudo clock

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3288?page=com.atlassian.jira.plug... ] Davide Sottara commented on JBRULES-3288: ----------------------------------------- You're welcome! and I know, sometimes it takes quite some time before tickets are considered. Reasking questions on the user list also helps :) In any case, I'm trying to push the team to fix as many bugs as possible for an imminent 5.6 release > Sliding time window ignored when using @timestamp and pseudo clock > ------------------------------------------------------------------ > > Key: JBRULES-3288 > URL: https://issues.jboss.org/browse/JBRULES-3288 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (fusion) > Affects Versions: 5.3.0.Final > Environment: Mac OSX 10.6.8 > Reporter: Colin Webber > Assignee: Edson Tirelli > Labels: @timestamp, drools, fusion, pseudoclock > > When using a custom @timestamp together with PSEUDO clock, all events are accumulated rather than just those within the window:time period. I have tried using long (millisecond) and java.util.Date without success. > ================================== > declare SimpleObject > @role(event) > @timestamp(customTime) > @expires(10m) > end; > rule "honour custom timestamp" > when > $avgVal : Number (longValue > 0) from accumulate ( SimpleObject($valueLng : valueLong ) over window:time (10s) from entry-point "SimpleEP", average ( $valueLng ) ) > then > System.out.println("avg: " + $avgVal); > end > --------------------------------------- > import java.util.Date; > public class SimpleObject { > > private long customTime; > public long valueLong; > > public SimpleObject(Date customTime, long valueLong) { > this.customTime = customTime.getTime(); > this.valueLong = valueLong; > } > > public long getCustomTime() { > return customTime; > } > public void setCustomTime(long customTime) { > this.customTime = customTime; > } > public long getValueLong() { > return valueLong; > } > public void setValueLong(long valueLong) { > this.valueLong = valueLong; > } > > } > ------------ Trivial Spock/Groovy unit test ---------------- > @IgnoreRest > def "should honour custom timestamp"() { > when: > use (TimeCategory) { > def now = new Date() > simpleEp.insert(new SimpleObject(now, 100)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(5.seconds.from.now, 90)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(10.seconds.from.now, 80)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(15.seconds.from.now, 70)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(20.seconds.from.now, 60)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(25.seconds.from.now, 50)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > } > then: > 1 == 1 // no assertions - we're examining the stdout. > } > ================================== > OUTPUT (INCORRECT - all values are included for each evalutation): > avg: 100.0 > avg: 95.0 > avg: 90.0 > avg: 85.0 > avg: 80.0 > avg: 75.0 > Note that when commenting out the @timestamp tag the output changes to the following (correct) output: > avg: 100.0 > avg: 95.0 > avg: 90.0 > avg: 85.0 > avg: 80.0 > avg: 75.0 > avg: 70.0 > avg: 65.0 > avg: 60.0 > avg: 55.0 > avg: 50.0 > Also note that when using the REALTIME clock with Thread.sleep the output is correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3288) Sliding time window ignored when using @timestamp and pseudo clock

by Colin Webber (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3288?page=com.atlassian.jira.plug... ] Colin Webber commented on JBRULES-3288: --------------------------------------- Thanks for taking the time to reply Davide - much appreciated. Even a year later your advice is still useful! > Sliding time window ignored when using @timestamp and pseudo clock > ------------------------------------------------------------------ > > Key: JBRULES-3288 > URL: https://issues.jboss.org/browse/JBRULES-3288 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (fusion) > Affects Versions: 5.3.0.Final > Environment: Mac OSX 10.6.8 > Reporter: Colin Webber > Assignee: Edson Tirelli > Labels: @timestamp, drools, fusion, pseudoclock > > When using a custom @timestamp together with PSEUDO clock, all events are accumulated rather than just those within the window:time period. I have tried using long (millisecond) and java.util.Date without success. > ================================== > declare SimpleObject > @role(event) > @timestamp(customTime) > @expires(10m) > end; > rule "honour custom timestamp" > when > $avgVal : Number (longValue > 0) from accumulate ( SimpleObject($valueLng : valueLong ) over window:time (10s) from entry-point "SimpleEP", average ( $valueLng ) ) > then > System.out.println("avg: " + $avgVal); > end > --------------------------------------- > import java.util.Date; > public class SimpleObject { > > private long customTime; > public long valueLong; > > public SimpleObject(Date customTime, long valueLong) { > this.customTime = customTime.getTime(); > this.valueLong = valueLong; > } > > public long getCustomTime() { > return customTime; > } > public void setCustomTime(long customTime) { > this.customTime = customTime; > } > public long getValueLong() { > return valueLong; > } > public void setValueLong(long valueLong) { > this.valueLong = valueLong; > } > > } > ------------ Trivial Spock/Groovy unit test ---------------- > @IgnoreRest > def "should honour custom timestamp"() { > when: > use (TimeCategory) { > def now = new Date() > simpleEp.insert(new SimpleObject(now, 100)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(5.seconds.from.now, 90)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(10.seconds.from.now, 80)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(15.seconds.from.now, 70)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(20.seconds.from.now, 60)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(25.seconds.from.now, 50)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > } > then: > 1 == 1 // no assertions - we're examining the stdout. > } > ================================== > OUTPUT (INCORRECT - all values are included for each evalutation): > avg: 100.0 > avg: 95.0 > avg: 90.0 > avg: 85.0 > avg: 80.0 > avg: 75.0 > Note that when commenting out the @timestamp tag the output changes to the following (correct) output: > avg: 100.0 > avg: 95.0 > avg: 90.0 > avg: 85.0 > avg: 80.0 > avg: 75.0 > avg: 70.0 > avg: 65.0 > avg: 60.0 > avg: 55.0 > avg: 50.0 > Also note that when using the REALTIME clock with Thread.sleep the output is correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3288) Sliding time window ignored when using @timestamp and pseudo clock

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3288?page=com.atlassian.jira.plug... ] Davide Sottara commented on JBRULES-3288: ----------------------------------------- This is not a bug.. there is a mismatch between the clock and the timestamps. now() is based on the system clock and starts from "epoch", the pseudo-clock starts at 0. You are not seeing the final activations because the engine is waiting to expire the events, i.e. the pseudo-clock to advance to now()+10... When you use the realtime clock, instead, the times are aligned as you would expect > Sliding time window ignored when using @timestamp and pseudo clock > ------------------------------------------------------------------ > > Key: JBRULES-3288 > URL: https://issues.jboss.org/browse/JBRULES-3288 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (fusion) > Affects Versions: 5.3.0.Final > Environment: Mac OSX 10.6.8 > Reporter: Colin Webber > Assignee: Edson Tirelli > Labels: @timestamp, drools, fusion, pseudoclock > > When using a custom @timestamp together with PSEUDO clock, all events are accumulated rather than just those within the window:time period. I have tried using long (millisecond) and java.util.Date without success. > ================================== > declare SimpleObject > @role(event) > @timestamp(customTime) > @expires(10m) > end; > rule "honour custom timestamp" > when > $avgVal : Number (longValue > 0) from accumulate ( SimpleObject($valueLng : valueLong ) over window:time (10s) from entry-point "SimpleEP", average ( $valueLng ) ) > then > System.out.println("avg: " + $avgVal); > end > --------------------------------------- > import java.util.Date; > public class SimpleObject { > > private long customTime; > public long valueLong; > > public SimpleObject(Date customTime, long valueLong) { > this.customTime = customTime.getTime(); > this.valueLong = valueLong; > } > > public long getCustomTime() { > return customTime; > } > public void setCustomTime(long customTime) { > this.customTime = customTime; > } > public long getValueLong() { > return valueLong; > } > public void setValueLong(long valueLong) { > this.valueLong = valueLong; > } > > } > ------------ Trivial Spock/Groovy unit test ---------------- > @IgnoreRest > def "should honour custom timestamp"() { > when: > use (TimeCategory) { > def now = new Date() > simpleEp.insert(new SimpleObject(now, 100)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(5.seconds.from.now, 90)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(10.seconds.from.now, 80)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(15.seconds.from.now, 70)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(20.seconds.from.now, 60)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > simpleEp.insert(new SimpleObject(25.seconds.from.now, 50)) > ksession.fireAllRules() > clock.advanceTime( 5, TimeUnit.SECONDS ); > ksession.fireAllRules() > } > then: > 1 == 1 // no assertions - we're examining the stdout. > } > ================================== > OUTPUT (INCORRECT - all values are included for each evalutation): > avg: 100.0 > avg: 95.0 > avg: 90.0 > avg: 85.0 > avg: 80.0 > avg: 75.0 > Note that when commenting out the @timestamp tag the output changes to the following (correct) output: > avg: 100.0 > avg: 95.0 > avg: 90.0 > avg: 85.0 > avg: 80.0 > avg: 75.0 > avg: 70.0 > avg: 65.0 > avg: 60.0 > avg: 55.0 > avg: 50.0 > Also note that when using the REALTIME clock with Thread.sleep the output is correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-122) RuleML Resource Type and Importer

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-122?page=com.atlassian.jira.plugin... ] Davide Sottara moved JBRULES-3273 to DROOLS-122: ------------------------------------------------ Project: Drools (was: JBRULES) Key: DROOLS-122 (was: JBRULES-3273) Workflow: GIT Pull Request workflow (was: jira) > RuleML Resource Type and Importer > --------------------------------- > > Key: DROOLS-122 > URL: https://issues.jboss.org/browse/DROOLS-122 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3558) Odd rules execution for expired events

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3558?page=com.atlassian.jira.plug... ] Davide Sottara updated JBRULES-3558: ------------------------------------ Priority: Blocker (was: Major) > Odd rules execution for expired events > -------------------------------------- > > Key: JBRULES-3558 > URL: https://issues.jboss.org/browse/JBRULES-3558 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (fusion) > Affects Versions: 5.4.0.Final > Environment: Windows Vista 64, JRE6 (x86) > Reporter: Karol Sobczak > Assignee: Mark Proctor > Priority: Blocker > Attachments: expiredrules.zip > > > I have declared two types: > declare Motion > @role( event ) > @expires( 5s ) > @timestamp( eventTime ) > eventTime : long > end > declare Recording > end > and following rules: > rule "StartRecording" > when > Motion() > not Recording() > then > insert(new Recording()) > end > the problem is that when I put a lot of "Motions", sleep (so "Motions" become expired) and then do fireAllRules(), I got "StartRecording" executed multiple times (and not only once), event though "Recording" is inserted every time. > Another issue would be when instead of "StartRecording" rule I would have "StopRecording" rule: > rule "StopRecording" > when > $m : Motion() > $r : Recording() > then > System.err.println("Recording: " + $r); > retract($r); > end > then when there is a "Recording" fact inserted and multiple expired "Motions", the rule would be executed multiple times (when "Motions" expire) and $r would be null after the first "StopRecording" rule execution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1292) Eclipse instructions in README.md are obsolete

by Stephen Coy (JIRA)

Stephen Coy created WFLY-1292: --------------------------------- Summary: Eclipse instructions in README.md are obsolete Key: WFLY-1292 URL: https://issues.jboss.org/browse/WFLY-1292 Project: WildFly Issue Type: Patch Components: Documentation Affects Versions: 8.0.0.Alpha1 Environment: n/a Reporter: Stephen Coy Assignee: Tom Wells Priority: Minor The "Using Eclipse" instructions refer to the obsolete Sonatype m2Eclipse plugin, which has been replaced by the Eclipse m2e plugin. Also, there's no way the WildFly project can be loaded in a 512m heap. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013