August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-259) Named filters throw an IllegalArgumentException if they are embedded in an expression

by James Perkins (Jira)

James Perkins created LOGMGR-259: ------------------------------------ Summary: Named filters throw an IllegalArgumentException if they are embedded in an expression Key: LOGMGR-259 URL: https://issues.jboss.org/browse/LOGMGR-259 Project: JBoss Log Manager Issue Type: Bug Reporter: James Perkins Assignee: James Perkins A named filter, one that was added via the configuration API, will throw an {{IllegalArgumentException}} if they are embedded in a filter expression. The following should be a valid expression as "all" is a changed filter and "test" is the manually created filter. {code} logContextConfiguration.addFilterConfiguration(null, "org.jboss.filter.Test", "test"); logContextConfiguration.getLoggerConfiguration("").setFilter("all(test)"); {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12347?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12347: ---------------------------------- Fix Version/s: 18.0.0.Beta1 > Upgrade jgroups-kubernetes to 1.0.12.Final > ------------------------------------------ > > Key: WFLY-12347 > URL: https://issues.jboss.org/browse/WFLY-12347 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 18.0.0.Beta1 > > > Adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. > Tag/changelog > https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12347?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12347: ---------------------------------- Issue Type: Component Upgrade (was: Bug) > Upgrade jgroups-kubernetes to 1.0.12.Final > ------------------------------------------ > > Key: WFLY-12347 > URL: https://issues.jboss.org/browse/WFLY-12347 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 18.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12347?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12347: ---------------------------------- Description: Adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. Tag/changelog https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final was:https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. > Upgrade jgroups-kubernetes to 1.0.12.Final > ------------------------------------------ > > Key: WFLY-12347 > URL: https://issues.jboss.org/browse/WFLY-12347 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 18.0.0.Beta1 > > > Adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. > Tag/changelog > https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12347?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12347: ---------------------------------- Description: https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. > Upgrade jgroups-kubernetes to 1.0.12.Final > ------------------------------------------ > > Key: WFLY-12347 > URL: https://issues.jboss.org/browse/WFLY-12347 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 18.0.0.Beta1 > > > https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-12347: ------------------------------------- Summary: Upgrade jgroups-kubernetes to 1.0.12.Final Key: WFLY-12347 URL: https://issues.jboss.org/browse/WFLY-12347 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 17.0.1.Final Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4304) UX design: Keyboard shortcuts for Find feature in GDST/DMN 7.5

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4304?page=com.atlassian.jira.plugi... ] Guilherme Gomes commented on DROOLS-4304: ----------------------------------------- [~uxdlc] The slide 10 is enough. We can mark the JIRA as Done. Thank you! > UX design: Keyboard shortcuts for Find feature in GDST/DMN 7.5 > -------------------------------------------------------------- > > Key: DROOLS-4304 > URL: https://issues.jboss.org/browse/DROOLS-4304 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Elizabeth Clayton > Assignee: Sarah Rambacher > Priority: Major > Labels: UX, UXTeam, drools-tools > > This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation. > h1. Requirements > See referenced document: https://docs.google.com/document/d/1VX_KhMhPgs2ZoOv7_jpfbl2o2-Y528UEImGk9... > h1. Documentation > Keyboard recommendations to be documented at: https://docs.google.com/presentation/d/1itceVe225mMtR55pqB-llpLNdU6kq4TBi... > h1. Acceptance test > - Enter to large amount of data in search box > - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed. > - Searching for non-existing result > - Result appearing once > - Result appearing multiple times > - Set of inputs: > *- A-Z > *- a-z > *- 0-9 > *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - + > *- Blank spaces -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3244) [DMN Designer] Reuse Workbench Data Objects as DMN Data Types

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3244?page=com.atlassian.jira.plugi... ] Guilherme Gomes closed DROOLS-3244. ----------------------------------- Resolution: Duplicate Issue Closing this JIRA, since it's duplicated (https://issues.jboss.org/browse/DROOLS-2572). > [DMN Designer] Reuse Workbench Data Objects as DMN Data Types > ------------------------------------------------------------- > > Key: DROOLS-3244 > URL: https://issues.jboss.org/browse/DROOLS-3244 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12301) CallerPrincipal will be anonymous (randomly) if EJB2 is called

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-12301?page=com.atlassian.jira.plugin... ] Farah Juma commented on WFLY-12301: ----------------------------------- I was able to reproduce this locally and found the following: * When the caller principal for the EJB2 bean is correct, the corresponding {{EJBComponentDescription}} always has {{securityRequired}} set to {{true}}. * When the caller principal for the EJB2 bean is anonymous, the corresponding {{EJBComponentDescription}} always has {{securityRequired}} set to {{false}}. * Whether or not security is required for the {{EJBComponentDescription}} gets set in [EJBSecurityViewConfigurator|https://github.com/wildfly/wildfly/blob/1bf99...]. * The {{EJBSecurityViewConfigurator}} gets called for each view that is associated with the {{EJBComponentDescription}}. * For EJB2, unlike EJB3, there are actually two views associated with the {{EJBComponentDescription}}: {{server.SomeEJB2}} and {{server.SomeEJBHome}}. Currently, whether or not security is required for the {{EJBComponentDescription}} associated with the EJB2 bean depends on the order in which these two views are processed. If {{server.SomeEJB2}} is processed last, {{securityRequired}} will be set to {{true}} since it has method level security metadata. However, if {{server.SomeEJBHome}} is processed last, {{securityRequired}} will be set to {{false}} since it does not have method level security metadata. The following PR fixes this by ensuring that {{EJBComponentDescription#setSecurityRequired}} only gets called in {{EJBSecurityViewConfigurator}} if security is actually required to avoid resetting the value when there are multiple views: https://github.com/wildfly/wildfly/pull/12468 > CallerPrincipal will be anonymous (randomly) if EJB2 is called > -------------------------------------------------------------- > > Key: WFLY-12301 > URL: https://issues.jboss.org/browse/WFLY-12301 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Affects Versions: 17.0.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Darran Lofthouse > Priority: Major > Labels: EJB2, security > Attachments: reproducer.zip > > > An EJB application which call an EJB2 SLSB will fail (randomly) to show the correct user if getCallerPrincipal is used inside. Also the roles are not set. > The EJB2 Bean is secured by ejb-jar.xml so it is not expected that it will be called without role > <assembly-descriptor> > <method-permission> > <role-name>testRole</role-name> > <method> > <ejb-name>simpleejb.server.SomeEJB2Bean</ejb-name> > <method-intf>Remote</method-intf> > <method-name>*</method-name> > </method> > </method-permission> > This error is constant seen if the server is up and running but each restart will change the behaviour randomly. > Note that an EJB3 bean of the same EAR file will work always correctly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3713) [DMN Designer] Automatic layout is reordering nodes inside Decision Service

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3713?page=com.atlassian.jira.plugi... ] Guilherme Gomes reassigned DROOLS-3713: --------------------------------------- Assignee: Daniel José dos Santos (was: Mario Fusco) > [DMN Designer] Automatic layout is reordering nodes inside Decision Service > --------------------------------------------------------------------------- > > Key: DROOLS-3713 > URL: https://issues.jboss.org/browse/DROOLS-3713 > Project: Drools > Issue Type: Enhancement > Affects Versions: 7.20.0.Final > Reporter: Daniel José dos Santos > Assignee: Daniel José dos Santos > Priority: Major > Attachments: screenshot_from_2019-02-28_09-28-58.png > > > The automatic layout is reordering nodes inside decision service, which shouldn't happen. The entire Decision Service should be considered as a "single node". -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2019