January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4961) User / Role Permissions on package level

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4961?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4961: --------------------------------- Labels: drools-tools (was: ) > User / Role Permissions on package level > ---------------------------------------- > > Key: DROOLS-4961 > URL: https://issues.redhat.com/browse/DROOLS-4961 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > It will be amazingly helpful to have the ability to minimize the access / permissions of a user / group on package level. > Within a project you can define several packages - for different purposes - and you need each team to be able to work on / view a specific package. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4960) Reference a data object from one project to another one.

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4960?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-4960: ------------------------------------ Assignee: Toni Rikkola (was: Mario Fusco) > Reference a data object from one project to another one. > -------------------------------------------------------- > > Key: DROOLS-4960 > URL: https://issues.redhat.com/browse/DROOLS-4960 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Currently, nothing can be referenced from one project to another one. > Using a common area to create the Data Objects etc. and reference them on several projects will be very helpful. > Java-wise is like we are creating two projects and we reference the first one in the second one, in order to use some classes in our code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4961) User / Role Permissions on package level

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4961?page=com.atlassian.jira.plug... ] Mario Fusco reassigned DROOLS-4961: ----------------------------------- Assignee: Toni Rikkola (was: Mario Fusco) > User / Role Permissions on package level > ---------------------------------------- > > Key: DROOLS-4961 > URL: https://issues.redhat.com/browse/DROOLS-4961 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > It will be amazingly helpful to have the ability to minimize the access / permissions of a user / group on package level. > Within a project you can define several packages - for different purposes - and you need each team to be able to work on / view a specific package. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

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

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ] Mario Fusco reassigned DROOLS-4959: ----------------------------------- Assignee: Toni Rikkola (was: Mario Fusco) > 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 > Labels: drools-tools > > 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] (DROOLS-4960) Reference a data object from one project to another one.

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4960?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4960: --------------------------------- Labels: drools-tools (was: ) > Reference a data object from one project to another one. > -------------------------------------------------------- > > Key: DROOLS-4960 > URL: https://issues.redhat.com/browse/DROOLS-4960 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Currently, nothing can be referenced from one project to another one. > Using a common area to create the Data Objects etc. and reference them on several projects will be very helpful. > Java-wise is like we are creating two projects and we reference the first one in the second one, in order to use some classes in our code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

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

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4959: --------------------------------- Labels: drools-tools (was: ) > 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: Mario Fusco > Priority: Major > Labels: drools-tools > > 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] (WFCORE-4809) Allow composite operation to read the model without need to acquired the write lock in domain mode

by Yeray Borges (Jira)

Yeray Borges created WFCORE-4809: ------------------------------------ Summary: Allow composite operation to read the model without need to acquired the write lock in domain mode Key: WFCORE-4809 URL: https://issues.redhat.com/browse/WFCORE-4809 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Yeray Borges Assignee: Yeray Borges Currently, the web console is highly affected by the write lock acquisition. Most of the read operations done by the web console are translated into composite operations, that under some circumstances (target to a single host, non-wildcards..), require the DC write lock. This write lock acquisition has a huge impact on the web console since each operation is queued until the lock is released. As an example, if we have a deployment that takes some minutes in the middle the user is clicking to see the server status, soon the web console gets unresponsible. This issue tries to reduce the write lock acquisition in these cases and allow read operations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4791) HttpManagementConstantHeadersTestCase causes tests failures

by Tomas Terem (Jira)

[ https://issues.redhat.com/browse/WFCORE-4791?page=com.atlassian.jira.plug... ] Tomas Terem commented on WFCORE-4791: ------------------------------------- Hi [~ropalka], I've created a PR: https://github.com/wildfly/wildfly-core/pull/4063. Can you execute tests on your laptop (since that was the only place where issue could be observed) and verify if it's fixed? > HttpManagementConstantHeadersTestCase causes tests failures > ----------------------------------------------------------- > > Key: WFCORE-4791 > URL: https://issues.redhat.com/browse/WFCORE-4791 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Richard Opalka > Assignee: Tomas Terem > Priority: Major > Fix For: 11.0.0.Beta8 > > Attachments: testsuite.log > > > Commit 68928b0b in WildFly-Core introduced new regression. > High probably test doesn't do proper test environment clean up > and some tests following it are thus failing. The issue isn't visible > in our CI environment so it probably depends on actual tests ordering. > I am able to reproduce this issue on my laptop always. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1056) Try OCP 4.4 on IPv6 in PSI

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1056: ------------------------------------ Summary: Try OCP 4.4 on IPv6 in PSI Key: SWSQE-1056 URL: https://issues.redhat.com/browse/SWSQE-1056 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13007) New subsystem for configuring clustering API implementations

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13007: ----------------------------------- Summary: New subsystem for configuring clustering API implementations Key: WFLY-13007 URL: https://issues.redhat.com/browse/WFLY-13007 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 19.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, WildFly creates services for the following objects for every JGroups channel: * CommandDispatcherFactory * Group ... and creates services the following objects for every Infinispan cache: * SingletonServiceConfiguratorFactory * ServiceProviderRegistry * Registry * Group Only some of these services are ever started. If we instead created a separate subsystem that configures these objects, we could significantly reduce the number of services created (but never started) by the jgroups and infinispan subsystems. This has a number of benefits for users as well: * Increases overall visibility of the public clustering API * Simplifies the current mysterious state of service wiring by establishing explicit capability requirements where necessary -- 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