May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9856) [JDK9+] org.jboss.security.negotiation package is exported by two jars

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-9856?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFLY-9856: -------------------------------------- Assignee: Darran Lofthouse > [JDK9+] org.jboss.security.negotiation package is exported by two jars > ---------------------------------------------------------------------- > > Key: WFLY-9856 > URL: https://issues.redhat.com/browse/WFLY-9856 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Tomaž Cerar > Assignee: Darran Lofthouse > Priority: Major > > Currently if you have > jboss-negotiation-common-3.0.4.Final.jar and jboss-negotiation-extras-3.0.4.Final.jar > on your module path, jvm complains as both jars export package org.jboss.security.negotiation package > which violates the modules contract where only one module (jar) can provide single package. > example error that jvm prints > {noformat} > Error: Modules jboss.negotiation.common and jboss.negotiation.extras export package org.jboss.security.negotiation to module wildfly.clustering.common > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-958) JASPIC implementation in JBoss EAP 7.0.0 seems to contradict the javadoc of the ServerAuthModule interface

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/SECURITY-958?page=com.atlassian.jira.plu... ] Darran Lofthouse reassigned SECURITY-958: ----------------------------------------- Assignee: (was: Darran Lofthouse) > JASPIC implementation in JBoss EAP 7.0.0 seems to contradict the javadoc of the ServerAuthModule interface > ---------------------------------------------------------------------------------------------------------- > > Key: SECURITY-958 > URL: https://issues.redhat.com/browse/SECURITY-958 > Project: PicketBox > Issue Type: Bug > Reporter: Enrique González Martínez > Priority: Major > > The EAP 7.0.0 JASPIC ServerAuthModule framework passes the request policy and response policy objects as null into the initialize() method. The spec and java docs say that both must not be null. > http://docs.oracle.com/javaee/6/api/javax/security/auth/message/module/Se... > https://docs.oracle.com/javaee/7/api/javax/security/auth/message/module/S... > The javadoc and spec says: "The request policy and the response policy must not both be null". > Wildfly 10.0.0.Final has the same issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-182) Add support to JASPI for integration with WildFly Elytron

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/JBEE-182?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved JBEE-182. ----------------------------------- Resolution: Rejected In the end no specific changes were needed and this was handled within the application server. > Add support to JASPI for integration with WildFly Elytron > --------------------------------------------------------- > > Key: JBEE-182 > URL: https://issues.redhat.com/browse/JBEE-182 > Project: JBoss Enterprise Spec APIs > Issue Type: Feature Request > Components: jboss-jaspi-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-83) The remoting-jmx 2.0.0.Final artifact's dependencies are not available in Maven Central

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/REMJMX-83?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved REMJMX-83. ------------------------------------ Resolution: Out of Date > The remoting-jmx 2.0.0.Final artifact's dependencies are not available in Maven Central > --------------------------------------------------------------------------------------- > > Key: REMJMX-83 > URL: https://issues.redhat.com/browse/REMJMX-83 > Project: Remoting JMX > Issue Type: Bug > Components: Build > Affects Versions: 2.0.0.Final > Reporter: Tomas Repel > Assignee: Darran Lofthouse > Priority: Major > Fix For: 2.0.2.CR1 > > > The org.jboss.remotingjmx:remoting-jmx:2.0.0.Final artifact is available in Maven Central but it has dependencies that are not available in Maven Central, for instance org.jboss.remoting:jboss-remoting:jar:4.0.0.Beta3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13465) Issues in readme for microprofile-rest-client QS

by Martin Stefanko (Jira)

Martin Stefanko created WFLY-13465: -------------------------------------- Summary: Issues in readme for microprofile-rest-client QS Key: WFLY-13465 URL: https://issues.redhat.com/browse/WFLY-13465 Project: WildFly Issue Type: Bug Components: Quickstarts Affects Versions: 19.1.0.Final Reporter: Martin Stefanko Assignee: Martin Stefanko (1) WF BOM is used instead of EAP one: {code} <groupId>org.wildfly.bom</groupId> <artifactId>wildfly-microprofile</artifactId> <version>${version.server.bom}</version> {code} (2) References to WF instead of EAP, e.g.: {code}  {code} These references are used in pom.xml as well. (3) QS contains tests but the readme does not mention them. (4) Consider using standard sections: * Use of the EAP_HOME and QUICKSTART_HOME Variables * Undeploy the Quickstart * Run the Arquillian Tests * Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4966) Upgrade WildFly OpenSSL to 1.1.0.Final

by Farah Juma (Jira)

Farah Juma created WFCORE-4966: ---------------------------------- Summary: Upgrade WildFly OpenSSL to 1.1.0.Final Key: WFCORE-4966 URL: https://issues.redhat.com/browse/WFCORE-4966 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13464) Usage of wildfly maven plugin in microprofile-openapi QS should reference JBOSS_HOME

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13464?page=com.atlassian.jira.plugi... ] Paul Ferraro moved JBEAP-19486 to WFLY-13464: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13464 (was: JBEAP-19486) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Affects Version/s: 19.1.0.Final (was: EAP-XP-1.0.0.GA-CR1) > Usage of wildfly maven plugin in microprofile-openapi QS should reference JBOSS_HOME > ------------------------------------------------------------------------------------ > > Key: WFLY-13464 > URL: https://issues.redhat.com/browse/WFLY-13464 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 19.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Blocker > > The QS is included in EAP XP 1.0.0.GA-CR1 Quickstarts ZIP, but its instructions are WildFly specific. > (1) Use of WildFly instead of EAP on several places, e.g. title "Using MicroProfile OpenAPI in WildFly", introduction "This guide demonstrate how to use the MicroProfile OpenAPI functionality in WildFly" etc. > (2) Starting the server with unsupported method "mvn wildfly:run &". Please use standard section {{Start the JBoss EAP Standalone Server}} or use a similar steps to start the server. The same applies for {{mvn wildfly:execute-commands}}, {{mvn wildfly:shutdown -Dwildfly.reload=true}} and {{mvn wildfly:shutdown}} commands. > (3) When trying the WF commands with EAP XP1 server, they fail: > {code} > [nziakova@laptop microprofile-openapi]$ export JBOSS_HOME > [nziakova@laptop microprofile-openapi]$ mvn wildfly:run & > ... > [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:2.0.0.Final:run (default-cli) on project microprofile-openapi-quickstart: Execution default-cli of goal org.wildfly.plugins:wildfly-maven-plugin:2.0.0.Final:run failed: Failure to find org.wildfly:wildfly-dist:zip:7.3.1.GA-redhat-SNAPSHOT > {code} > (4) When trying standard server start, the QS works fine without the step {{Add support for MicroProfile OpenAPI by adding the requisite extension and subsystem.}} - is it needed for EAP? > {code} > EAP_HOME/bin/standalone.sh -c standalone-microprofile.xml > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1133) Mirror operators from quay.io/maistra and redhat-operators

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1133?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1133. ---------------------------------- Resolution: Done New job added https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job... > Mirror operators from quay.io/maistra and redhat-operators > ---------------------------------------------------------- > > Key: SWSQE-1133 > URL: https://issues.redhat.com/browse/SWSQE-1133 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > When the disconnected OCP cluster is provisioned there is nothing in operator hub. It's necessary to mirror required catalog. > We will need redhat-operators and operators from quay.io/maistra -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5327) Multiselect dropdown for enumerated values - numbers

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5327?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5327: -------------------------------- Steps to Reproduce: # Open the attached project # Open the guided rule template # Click to *Data* tab # Try to edit *$Numero* column values Current: Changes will be lost, 0 is shown in cell Expected: All selected numbers are kept and shown in cell , delimited by comma > Multiselect dropdown for enumerated values - numbers > ---------------------------------------------------- > > Key: DROOLS-5327 > URL: https://issues.redhat.com/browse/DROOLS-5327 > Project: Drools > Issue Type: Bug > Components: Guided Template Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > Attachments: MySpace_project.zip > > > During verification of DROOLS-5011 was spotted corner case that was not fixed. > In the original issue customer user attached project with enumeration for *String* field and used that field in guided rule template. > The issue is if user follow the same scenario but instead of *String* field, some number type is used, for example *Integer*. In such case, when user added data to rule template, multiselect dropdown was shown correctly, however in the grid was always shown 0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5327) Multiselect dropdown for enumerated values - numbers

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5327?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5327: -------------------------------- Attachment: MySpace_project.zip > Multiselect dropdown for enumerated values - numbers > ---------------------------------------------------- > > Key: DROOLS-5327 > URL: https://issues.redhat.com/browse/DROOLS-5327 > Project: Drools > Issue Type: Bug > Components: Guided Template Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > Attachments: MySpace_project.zip > > > During verification of DROOLS-5011 was spotted corner case that was not fixed. > In the original issue customer user attached project with enumeration for *String* field and used that field in guided rule template. > The issue is if user follow the same scenario but instead of *String* field, some number type is used, for example *Integer*. In such case, when user added data to rule template, multiselect dropdown was shown correctly, however in the grid was always shown 0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 May 2020