February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-140) Switch the build to Java 8

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-140: ------------------------------------ Summary: Switch the build to Java 8 Key: ELY-140 URL: https://issues.jboss.org/browse/ELY-140 Project: WildFly Elytron Issue Type: Task Components: Build Reporter: Darran Lofthouse Fix For: 1.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-528) ServerService and ServerShutdownHandler are not embedded-friendly

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-528: --------------------------------------- Summary: ServerService and ServerShutdownHandler are not embedded-friendly Key: WFCORE-528 URL: https://issues.jboss.org/browse/WFCORE-528 Project: WildFly Core Issue Type: Enhancement Reporter: Brian Stansberry Assignee: Brian Stansberry ServerService and ServerShutdownHandler are both unfriendly to embedding as they call System.exit (in the case of ServerService only in the case of critical boot failures.) Simplest fix is to use SystemExiter and have the embedded server code swap in an approproite Exiter. Only thing I don't like about that is SystemExiter is base on static fields and seems to have been written for testing. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-527) Embedded server is not graceful-shutdown friendly

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-527: --------------------------------------- Summary: Embedded server is not graceful-shutdown friendly Key: WFCORE-527 URL: https://issues.jboss.org/browse/WFCORE-527 Project: WildFly Core Issue Type: Enhancement Reporter: Brian Stansberry Assignee: Brian Stansberry The embedded server implements stop by stopping the service container. This is not graceful-shutdown friendly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3078) directory-grouping configuration is not getting persisted via CLI when no servers defined

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3078?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3078: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1073715|https://bugzilla.redhat.com/show_bug.cgi?id=1073715] from VERIFIED to CLOSED > directory-grouping configuration is not getting persisted via CLI when no servers defined > ----------------------------------------------------------------------------------------- > > Key: WFLY-3078 > URL: https://issues.jboss.org/browse/WFLY-3078 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.0.0.Final > Environment: All Operating System > Reporter: Jay Kumar SenSharma > Assignee: Emanuel Muckenhuber > Fix For: 8.1.0.CR1, 8.1.0.Final > > > - If none of the servers are defined in "host.xml" (means <servers></servers> empty tag is present) and if the user tries to run the following CLI command to change the "directory-grouping" to "by-type" then the value is not persisted in the configuration file (host.xml) and the <servers></servers> tag is also removed from the host.xml > {code} > /host=master/:write-attribute(name=directory-grouping,value=by-type) > {code} > - The value of "directory-grouping" is stored "in memory" so this change does not survive the host restart. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-703) Add ability to see more text in a text field using a textarea or other multi-line wrapping capability

by Stephen Slaboda (JIRA)

Stephen Slaboda created DROOLS-703: -------------------------------------- Summary: Add ability to see more text in a text field using a textarea or other multi-line wrapping capability Key: DROOLS-703 URL: https://issues.jboss.org/browse/DROOLS-703 Project: Drools Issue Type: Enhancement Affects Versions: 6.1.0.Final Environment: RedHat 6.3 Linux x86_64; Firefox 10.0.5 Reporter: Stephen Slaboda Assignee: Mark Proctor Currently, if we want to assemble a string in a formula text field using various bound variables, the full text being constructed does not display all at once. The size of the box forces you to scroll around or copy/paste to see all the text after you get to a few dozen characters. We like to be somewhat verbose in our naming of variables to offer more clarity, so in some cases the text field may do this even when using a single variable name. Perhaps there could be a way to wrap the text into a multi-line display so that it is easier to edit these fields? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-702) Rule Inheritance fired the sub rule even the condition doen't match

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-702?page=com.atlassian.jira.plugin... ] Davide Sottara edited comment on DROOLS-702 at 2/1/15 12:42 PM: ---------------------------------------------------------------- Yacine, "from" leads to this situation: {code} $p : Person( ... ) Person( ... ) from $p {code} This ensures that both patterns are applied to the same object. In fact, the second will only be applied id an object passes the first. unification is effectively an equality constraint: {code} $p Person( ... ) Person( this == $p, ... ) {code} so it may even match two different objects that are equal to each other. Pick the one that you prefer based on your actual use case was (Author: dsotty): Yacine, "from" leads to this situation: {code} $p : Person( ... ) Person( ... ) from $p {code} This ensures that both patterns are applied to the same object. In fact, the second will only be applied id an object passes the first. unification is effectively an equality constraint: {code} $p Person() Person( this == $p ) {code} so it may even match two different objects that are equal to each other. Pick the one that you prefer based on your actual use case > Rule Inheritance fired the sub rule even the condition doen't match > ------------------------------------------------------------------- > > Key: DROOLS-702 > URL: https://issues.jboss.org/browse/DROOLS-702 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Environment: Windows, Java6.0.29 > Reporter: Yacine Jaber > Assignee: Davide Sottara > Priority: Critical > Attachments: wod-drools-test.7z > > > You can find the attached a simple maven project that shows this error. > You can run ExampleDrools class as main java application. > The sub rules are fired even if the condition is not matched. > There are a work arround by using <from $fact> into a sub rule to avoid firing this one. > This simple project shows the failed and work arround test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-702) Rule Inheritance fired the sub rule even the condition doen't match

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-702?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-702: --------------------------------------- Yacine, "from" leads to this situation: {code} $p : Person( ... ) Person( ... ) from $p {code} This ensures that both patterns are applied to the same object. In fact, the second will only be applied id an object passes the first. unification is effectively an equality constraint: {code} $p Person() Person( this == $p ) {code} so it may even match two different objects that are equal to each other. Pick the one that you prefer based on your actual use case > Rule Inheritance fired the sub rule even the condition doen't match > ------------------------------------------------------------------- > > Key: DROOLS-702 > URL: https://issues.jboss.org/browse/DROOLS-702 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Environment: Windows, Java6.0.29 > Reporter: Yacine Jaber > Assignee: Davide Sottara > Priority: Critical > Attachments: wod-drools-test.7z > > > You can find the attached a simple maven project that shows this error. > You can run ExampleDrools class as main java application. > The sub rules are fired even if the condition is not matched. > There are a work arround by using <from $fact> into a sub rule to avoid firing this one. > This simple project shows the failed and work arround test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-702) Rule Inheritance fired the sub rule even the condition doen't match

by Yacine Jaber (JIRA)

[ https://issues.jboss.org/browse/DROOLS-702?page=com.atlassian.jira.plugin... ] Yacine Jaber commented on DROOLS-702: ------------------------------------- Hi David, Thank you for your answer. I though that even if we use the same fact on the parent & child rule, the evaluation will be made on these two rules. It's could be interesting to mention this case on documentation (7.8.5. Conditional named consequences). The unification works as expected. Can you tell me which solution is strong (Unification or from)? > Rule Inheritance fired the sub rule even the condition doen't match > ------------------------------------------------------------------- > > Key: DROOLS-702 > URL: https://issues.jboss.org/browse/DROOLS-702 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Environment: Windows, Java6.0.29 > Reporter: Yacine Jaber > Assignee: Davide Sottara > Priority: Critical > Attachments: wod-drools-test.7z > > > You can find the attached a simple maven project that shows this error. > You can run ExampleDrools class as main java application. > The sub rules are fired even if the condition is not matched. > There are a work arround by using <from $fact> into a sub rule to avoid firing this one. > This simple project shows the failed and work arround test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1909) Add an AZURE_PING protocol

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1909?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1909: --------------------------- Fix Version/s: 3.6.2 > Add an AZURE_PING protocol > -------------------------- > > Key: JGRP-1909 > URL: https://issues.jboss.org/browse/JGRP-1909 > Project: JGroups > Issue Type: Feature Request > Reporter: Tristan Tarrant > Assignee: Bela Ban > Fix For: 3.6.2 > > > Similar to the existing S3_PING and GOOGLE_PING, add an AZURE_PING which suppors node discovery using Azure's blob storage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1909) Add an AZURE_PING protocol

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1909?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1909: -------------------------------- Do we have an Azure account that we can use to test a new discovery protocol ? > Add an AZURE_PING protocol > -------------------------- > > Key: JGRP-1909 > URL: https://issues.jboss.org/browse/JGRP-1909 > Project: JGroups > Issue Type: Feature Request > Reporter: Tristan Tarrant > Assignee: Bela Ban > Fix For: 3.6.2 > > > Similar to the existing S3_PING and GOOGLE_PING, add an AZURE_PING which suppors node discovery using Azure's blob storage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

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 February 2015