January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4959) Package name does not changes on copying of an existing package

by Nikos Tsekouras (Jira)

[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ] Nikos Tsekouras commented on DROOLS-4959: ----------------------------------------- Hi [~manstis]/[~Rikkola], Please be aware that same behavioral happens on project duplication. You can click on "duplicate" of a project but the inclusion remains the same as the original project. > Package name does not changes on copying of an existing package > --------------------------------------------------------------- > > Key: DROOLS-4959 > URL: https://issues.redhat.com/browse/DROOLS-4959 > Project: Drools > Issue Type: Bug > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Attachments: step1.PNG, step2.PNG, step3.PNG, step4.PNG > > > After copying a package to a new one, all copied resources will remain referencing the existing one. > This becomes a bigger issue once you use guided rules, which their source cannot be edited. > Due to that, duplication alerts will be raised. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11963) ejb3 thread-pool thread-factory should be shown deprecated in management api

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-11963?page=com.atlassian.jira.plugi... ] Moulali Shikalwadi reassigned WFLY-11963: ----------------------------------------- Assignee: Moulali Shikalwadi > ejb3 thread-pool thread-factory should be shown deprecated in management api > ---------------------------------------------------------------------------- > > Key: WFLY-11963 > URL: https://issues.redhat.com/browse/WFLY-11963 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 16.0.0.Final > Reporter: Chao Wang > Assignee: Moulali Shikalwadi > Priority: Major > > ejb3 thread-pool thread-factory should be shown deprecated in management api > The threads subsystem was deprecated and is not in the EAP 7.x configurations, so the thread-factory attribute on the ejb3 thread-pool configuration should indicate it is deprecated and should not be used. > {code} > /subsystem=ejb3/thread-pool=default:read-resource-description( > "thread-factory" => { > "type" => STRING, > "description" => "Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11963) ejb3 thread-pool thread-factory should be shown deprecated in management api

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-11963?page=com.atlassian.jira.plugi... ] Moulali Shikalwadi commented on WFLY-11963: ------------------------------------------- Thanks [~soul2zimate] > ejb3 thread-pool thread-factory should be shown deprecated in management api > ---------------------------------------------------------------------------- > > Key: WFLY-11963 > URL: https://issues.redhat.com/browse/WFLY-11963 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 16.0.0.Final > Reporter: Chao Wang > Assignee: Moulali Shikalwadi > Priority: Major > > ejb3 thread-pool thread-factory should be shown deprecated in management api > The threads subsystem was deprecated and is not in the EAP 7.x configurations, so the thread-factory attribute on the ejb3 thread-pool configuration should indicate it is deprecated and should not be used. > {code} > /subsystem=ejb3/thread-pool=default:read-resource-description( > "thread-factory" => { > "type" => STRING, > "description" => "Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12733) EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment

by Rhuan Rocha (Jira)

[ https://issues.redhat.com/browse/WFLY-12733?page=com.atlassian.jira.plugi... ] Rhuan Rocha commented on WFLY-12733: ------------------------------------ Hi, I think the option said by [~cfang] is a good option "The other option is to have getTimers() method always refresh internally before returning results." . I think it can be done, but it should provides a way to enable and disable this behavior via configuration file (domain.xml/standalone.xml) and CLI. What do you think [~brian.stansberry]? > EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment > -------------------------------------------------------------------------------------- > > Key: WFLY-12733 > URL: https://issues.redhat.com/browse/WFLY-12733 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Rhuan Rocha > Assignee: Cheng Fang > Priority: Major > Fix For: 20.0.0.Beta1 > > > The EJB Timer has a way to persist timers in a database using datasources. It is described [here|https://docs.jboss.org/author/display/WFLY10/EJB3+Clustered+Database...]. The database-data-store has an attribute called refresh-interval that define a time in milliseconds to refresh the timers reading the timers from database. Look this sample of configuration. > > {code:java} > <data-stores> > <file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/> > <database-data-store name="clustered-store" datasource-jndi-name="java:/jdbc/MyDataSource" partition="timer" refresh-interval="60000" allow-execution="true"/> > </data-stores> > {code} > The RFE is to Wildfly provide a way to force the refresh programmatically. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11963) ejb3 thread-pool thread-factory should be shown deprecated in management api

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-11963?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFLY-11963: ---------------------------------- [~mshikalw] No, I am not. You can take it. Thanks. > ejb3 thread-pool thread-factory should be shown deprecated in management api > ---------------------------------------------------------------------------- > > Key: WFLY-11963 > URL: https://issues.redhat.com/browse/WFLY-11963 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 16.0.0.Final > Reporter: Chao Wang > Priority: Major > > ejb3 thread-pool thread-factory should be shown deprecated in management api > The threads subsystem was deprecated and is not in the EAP 7.x configurations, so the thread-factory attribute on the ejb3 thread-pool configuration should indicate it is deprecated and should not be used. > {code} > /subsystem=ejb3/thread-pool=default:read-resource-description( > "thread-factory" => { > "type" => STRING, > "description" => "Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13015) Consolidate common instances of DiscardAttributeChecker that discard an attribute set to the default value

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13015?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13015: -------------------------------- Description: Follows up on WFCORE-4814. Replace DiscardAttributeChecker instances that discard an attribute whose value is the attribute's default value with a singleton instance. (was: Follows up on This common implementation can be implemented more concisely, such that a single instance can be used for any attribute.) > Consolidate common instances of DiscardAttributeChecker that discard an attribute set to the default value > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-13015 > URL: https://issues.redhat.com/browse/WFLY-13015 > Project: WildFly > Issue Type: Enhancement > Components: Management > Affects Versions: 19.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Follows up on WFCORE-4814. Replace DiscardAttributeChecker instances that discard an attribute whose value is the attribute's default value with a singleton instance. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13015) Consolidate common instances of DiscardAttributeChecker that discard an attribute set to the default value

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13015?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13015: -------------------------------- Description: Follows up on This common implementation can be implemented more concisely, such that a single instance can be used for any attribute. was: A common transformer pattern for newly added attributes is to discard the attribute if the value is the default value, and reject if otherwise defined. e.g. {code:java} builder.getAttributeBuilder() .setDiscard(new DiscardAttributeChecker.DiscardAttributeValueChecker(ATTRIBUTE.getDefaultValue()), ATTRIBUTE); .addRejectCheck(RejectAttributeChecker.DEFINED) ; {code} This common implementation can be implemented more concisely, such that a single instance can be used for any attribute. > Consolidate common instances of DiscardAttributeChecker that discard an attribute set to the default value > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-13015 > URL: https://issues.redhat.com/browse/WFLY-13015 > Project: WildFly > Issue Type: Enhancement > Components: Management > Affects Versions: 19.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Follows up on > This common implementation can be implemented more concisely, such that a single instance can be used for any attribute. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4814) Consolidate common instances of DiscardAttributeChecker that discard an attribute set to the default value

by Paul Ferraro (Jira)

Paul Ferraro created WFCORE-4814: ------------------------------------ Summary: Consolidate common instances of DiscardAttributeChecker that discard an attribute set to the default value Key: WFCORE-4814 URL: https://issues.redhat.com/browse/WFCORE-4814 Project: WildFly Core Issue Type: Enhancement Components: Management Affects Versions: 11.0.0.Beta7 Reporter: Paul Ferraro Assignee: Paul Ferraro A common transformer pattern for newly added attributes is to discard the attribute if the value is the default value, and reject if otherwise defined. e.g. {code:java} builder.getAttributeBuilder() .setDiscard(new DiscardAttributeChecker.DiscardAttributeValueChecker(ATTRIBUTE.getDefaultValue()), ATTRIBUTE); .addRejectCheck(RejectAttributeChecker.DEFINED) ; {code} This common implementation can be implemented more concisely, such that a single instance can be used for any attribute. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4815) Consolidate common instances of DiscardAttributeChecker that discard an attribute set to the default value

by Paul Ferraro (Jira)

Paul Ferraro created WFCORE-4815: ------------------------------------ Summary: Consolidate common instances of DiscardAttributeChecker that discard an attribute set to the default value Key: WFCORE-4815 URL: https://issues.redhat.com/browse/WFCORE-4815 Project: WildFly Core Issue Type: Enhancement Components: Management Affects Versions: 11.0.0.Beta7 Reporter: Paul Ferraro Assignee: Paul Ferraro A common transformer pattern for newly added attributes is to discard the attribute if the value is the default value, and reject if otherwise defined. e.g. {code:java} builder.getAttributeBuilder() .setDiscard(new DiscardAttributeChecker.DiscardAttributeValueChecker(ATTRIBUTE.getDefaultValue()), ATTRIBUTE); .addRejectCheck(RejectAttributeChecker.DEFINED) ; {code} This common implementation can be implemented more concisely, such that a single instance can be used for any attribute. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13015) Consolidate common instances of DiscardAttributeChecker that discard an attribute set to the default value

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13015?page=com.atlassian.jira.plugi... ] Paul Ferraro moved WFCORE-4815 to WFLY-13015: --------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-13015 (was: WFCORE-4815) Component/s: Management (was: Management) Affects Version/s: 19.0.0.Beta1 (was: 11.0.0.Beta7) > Consolidate common instances of DiscardAttributeChecker that discard an attribute set to the default value > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-13015 > URL: https://issues.redhat.com/browse/WFLY-13015 > Project: WildFly > Issue Type: Enhancement > Components: Management > Affects Versions: 19.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > A common transformer pattern for newly added attributes is to discard the attribute if the value is the default value, and reject if otherwise defined. > e.g. > {code:java} > builder.getAttributeBuilder() > .setDiscard(new DiscardAttributeChecker.DiscardAttributeValueChecker(ATTRIBUTE.getDefaultValue()), ATTRIBUTE); > .addRejectCheck(RejectAttributeChecker.DEFINED) > ; > {code} > This common implementation can be implemented more concisely, such that a single instance can be used for any attribute. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 January 2020