June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5434) Incorrect warning about file declaring wrong package

by Magnus Larsson (Jira)

[ https://issues.redhat.com/browse/DROOLS-5434?page=com.atlassian.jira.plug... ] Magnus Larsson updated DROOLS-5434: ----------------------------------- Description: I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not. I have tracked it down to *KieBuilderImpl.java*, method *isFileInKieBase*. The last 2 lines in that method calls: {code:java} // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file ); // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded return isPackageInKieBase( kieBase, pkgNameForFile ); {code} As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded). Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed. was: I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not. I have tracked it down to KieBuilderImpl.java, method isFileInKieBase. The last 2 lines in that method calls: {code:java} // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file ); // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded return isPackageInKieBase( kieBase, pkgNameForFile ); {code} As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded). Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed. > Incorrect warning about file declaring wrong package > ---------------------------------------------------- > > Key: DROOLS-5434 > URL: https://issues.redhat.com/browse/DROOLS-5434 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Magnus Larsson > Assignee: Mario Fusco > Priority: Major > > I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not. > I have tracked it down to *KieBuilderImpl.java*, method *isFileInKieBase*. The last 2 lines in that method calls: > {code:java} > // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning > String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file ); > // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded > return isPackageInKieBase( kieBase, pkgNameForFile ); > {code} > As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded). > Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5434) Incorrect warning about file declaring wrong package

by Magnus Larsson (Jira)

Magnus Larsson created DROOLS-5434: -------------------------------------- Summary: Incorrect warning about file declaring wrong package Key: DROOLS-5434 URL: https://issues.redhat.com/browse/DROOLS-5434 Project: Drools Issue Type: Bug Components: core engine Reporter: Magnus Larsson Assignee: Mario Fusco I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not. I have tracked it down to KieBuilderImpl.java, method isFileInKieBase. The last 2 lines in that method calls: {code:java} // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file ); // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded return isPackageInKieBase( kieBase, pkgNameForFile ); {code} As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded). Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5433) DMN Strongly typed generate JSON Schema

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5433: -------------------------------------- Summary: DMN Strongly typed generate JSON Schema Key: DROOLS-5433 URL: https://issues.redhat.com/browse/DROOLS-5433 Project: Drools Issue Type: Feature Request Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-278) PeriodicRotatingFileHandler may fail to rotate a file with a security permission

by James Perkins (Jira)

[ https://issues.redhat.com/browse/LOGMGR-278?page=com.atlassian.jira.plugi... ] James Perkins closed LOGMGR-278. -------------------------------- Resolution: Rejected The actual issue is setting the file not rotating it which seems correct. > PeriodicRotatingFileHandler may fail to rotate a file with a security permission > -------------------------------------------------------------------------------- > > Key: LOGMGR-278 > URL: https://issues.redhat.com/browse/LOGMGR-278 > Project: JBoss Log Manager > Issue Type: Bug > Components: core > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 2.2.0.Final, 2.1.17.Final, 2.3.0.Beta1 > > > During rotate the {{File.lastModified()}} time is used to determine if the file is ready to rotate. In situations such as a deployment on WildFly the deployment itself may fail to log a message as the security context is that of the deployment. The reason for the failure is the deployment does not have read permissions for the file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5008) Upgrade WildFly maven-plugins to 2.2.0.Final

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-5008: ---------------------------------------- Summary: Upgrade WildFly maven-plugins to 2.2.0.Final Key: WFCORE-5008 URL: https://issues.redhat.com/browse/WFCORE-5008 Project: WildFly Core Issue Type: Bug Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 13.0.0.Beta1 Pick up [https://github.com/wildfly/maven-plugins/issues/10] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13589) Add support for configuring RHDG authentication over hotrod

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13589?page=com.atlassian.jira.plugi... ] Radoslav Husar reassigned WFLY-13589: ------------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > Add support for configuring RHDG authentication over hotrod > ----------------------------------------------------------- > > Key: WFLY-13589 > URL: https://issues.redhat.com/browse/WFLY-13589 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Critical > > Infinispan 11.0 requires authentication by default. Consequently, we need the ability to configure authentication for a remote-cache-container. > See: [https://infinispan.org/blog/2020/06/04/server-secure-by-default/] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5007) Make use of the SocketAddressCallbackServerMechanismFactory to set the peer's IP address during HTTP authentication

by Farah Juma (Jira)

Farah Juma created WFCORE-5007: ---------------------------------- Summary: Make use of the SocketAddressCallbackServerMechanismFactory to set the peer's IP address during HTTP authentication Key: WFCORE-5007 URL: https://issues.redhat.com/browse/WFCORE-5007 Project: WildFly Core Issue Type: Task Components: Security Reporter: Farah Juma Assignee: Farah Juma WFCORE-4725 added the ability to configure a {{source-address-role-decoder}} to make use of the client's IP address for authorization decisions. Currently, it's only possible to make use of the IP address of a remote client during SASL authentication. To be able to make use of the IP address of a client during HTTP authentication, we just need to make use of a {{SocketAddressCallbackServerMechanismFactory}} to inform the server's callback handler of the peer's address. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1177) Disconnected Cluster 4.4 Installation failed on UPI

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-1177: ---------------------------------------------- Summary: Disconnected Cluster 4.4 Installation failed on UPI Key: SWSQE-1177 URL: https://issues.redhat.com/browse/SWSQE-1177 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Assignee: Filip Brychta Jenkins Job Log: [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/install-ocp-upi...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-278) PeriodicRotatingFileHandler may fail to rotate a file with a security permission

by James Perkins (Jira)

James Perkins created LOGMGR-278: ------------------------------------ Summary: PeriodicRotatingFileHandler may fail to rotate a file with a security permission Key: LOGMGR-278 URL: https://issues.redhat.com/browse/LOGMGR-278 Project: JBoss Log Manager Issue Type: Bug Components: core Reporter: James Perkins Assignee: James Perkins Fix For: 2.2.0.Final, 2.1.17.Final, 2.3.0.Beta1 During rotate the {{File.lastModified()}} time is used to determine if the file is ready to rotate. In situations such as a deployment on WildFly the deployment itself may fail to log a message as the security context is that of the deployment. The reason for the failure is the deployment does not have read permissions for the file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5147) [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-5147?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-5147: -------------------------------------- Sprint: 2020 Week 25-27 (from Jun 15) > [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX) > -------------------------------------------------------------------------- > > Key: DROOLS-5147 > URL: https://issues.redhat.com/browse/DROOLS-5147 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Elizabeth Clayton > Priority: Minor > Labels: UXTeam, drools-tools > Attachments: prototype.png > > > Currently, the DMN Decision Tables input/output clauses work fine, but they have the following unpractical scenarios: > - When users have a structure input node "associated" with an input clause (input column), they frequently need to go back to the data types page and remember the name of some field. > - When users select a structure data type as the type of an output clause, they need to create sub-columns for each field manually. > The goal for this JIRA is to get input from UX to enhance interactions with input and output clauses. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 June 2020