June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13553) Upgrade JBoss JSF API from 3.0.0.SP02 to 3.0.0.SP03

by Chao Wang (Jira)

Chao Wang created WFLY-13553: -------------------------------- Summary: Upgrade JBoss JSF API from 3.0.0.SP02 to 3.0.0.SP03 Key: WFLY-13553 URL: https://issues.redhat.com/browse/WFLY-13553 Project: WildFly Issue Type: Component Upgrade Components: JSF Affects Versions: 20.0.0.Beta1 Reporter: Chao Wang Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1148) Mirror openshift pipeline operator from community operators

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1148?page=com.atlassian.jira.plugi... ] Filip Brychta commented on SWSQE-1148: -------------------------------------- [~gbaufake] looking at the latest CSV it's not using sha, so the operator is not supported in disconnected mode yet - https://github.com/openshift/tektoncd-pipeline-operator/blob/master/deplo... Postponing this task > Mirror openshift pipeline operator from community operators > ----------------------------------------------------------- > > Key: SWSQE-1148 > URL: https://issues.redhat.com/browse/SWSQE-1148 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1166) Add support for OCP 4.5 disconnected when the RC is available

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1166: ------------------------------------ Summary: Add support for OCP 4.5 disconnected when the RC is available Key: SWSQE-1166 URL: https://issues.redhat.com/browse/SWSQE-1166 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta When RC for ocp 4.5 is available - https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags we need to add it to the disconnected provisioning job. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13424) External pooled connection factory won't be properly injected if it has several JNDI entries

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13424?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13424: ------------------------------------------ Yes :) > External pooled connection factory won't be properly injected if it has several JNDI entries > -------------------------------------------------------------------------------------------- > > Key: WFLY-13424 > URL: https://issues.redhat.com/browse/WFLY-13424 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 19.1.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 20.0.0.Beta1 > > > If the default JNDI name for MDB to get the resource adapter is not the first entry of the JNDI names bound for a pooled-connection-factory then the injection fails. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13424) External pooled connection factory won't be properly injected if it has several JNDI entries

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13424?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFLY-13424: ------------------------------------ thanks for the explanation, that was not clear to me that `pcf instanceof ContextListAndJndiViewManagedReferenceFactory` means it is an alias. iiuc, that means that when we integrate a version of WildFly with WFLY-13424 to build our images, CLOUD-3625 will not be required. Is that correct? > External pooled connection factory won't be properly injected if it has several JNDI entries > -------------------------------------------------------------------------------------------- > > Key: WFLY-13424 > URL: https://issues.redhat.com/browse/WFLY-13424 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 19.1.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 20.0.0.Beta1 > > > If the default JNDI name for MDB to get the resource adapter is not the first entry of the JNDI names bound for a pooled-connection-factory then the injection fails. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5402) [Scesim Editor] Fit error reason to the popup

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-5402?page=com.atlassian.jira.plug... ] Daniele Zonca reassigned DROOLS-5402: ------------------------------------- Assignee: Yeser Amer (was: Daniele Zonca) > [Scesim Editor] Fit error reason to the popup > --------------------------------------------- > > Key: DROOLS-5402 > URL: https://issues.redhat.com/browse/DROOLS-5402 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.38.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Attachments: image-2020-06-03-09-20-34-662.png > > > When package name is long then error reason gets out of the inline section of the popup > !image-2020-06-03-09-20-34-662.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5397) Data object containing at least one enum fails to be opend in Data model editor

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-5397?page=com.atlassian.jira.plug... ] Anna Dupliak closed DROOLS-5397. -------------------------------- Resolution: Done Could not reproduce anymore > Data object containing at least one enum fails to be opend in Data model editor > ------------------------------------------------------------------------------- > > Key: DROOLS-5397 > URL: https://issues.redhat.com/browse/DROOLS-5397 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation > Attachments: EnumFieldOnlyObject.java, EnumTest.java, model view with enum types.webm > > > It is possible to manage enum types in scenario simulation to do so in Rule based test scenario it is possible to have data object enum. But including at least one field that implements Enumeration interface breaks the model editor and fails to show fields on the UI See: [^model view with enum types.webm] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1979) Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1979?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on ELY-1979: --------------------------------------- Elytron requires Java 11 to build so as you say looks like it should just be a case of adding the missing methods and passing then through to a delegate when appropriate. We don't expect users of these classes to access them using any approach other than the standard API they expose so as for example SSLEngine doesn't contain those methods on the older releases if anyone bypasses that it will be expected to fail. > Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package > --------------------------------------------------------------------------- > > Key: ELY-1979 > URL: https://issues.redhat.com/browse/ELY-1979 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.12.0.Final > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.12.1.CR1 > > > JEPS 244, available in JDK 9 or later and in JDK 8 since the 251 release[1] has added new methods to some of the javax.net.ssl classes that elytron wraps in org.wildfly.security.ssl. But the elytron classes do not handle those new methods. I believe the relevant change is at [2] and updates the SSLEngine, SSLParameters and SSLSocket classes (plus various non-javax classes.) > If Elytron were to require 251 or later to build perhaps this could be a simple matter of adding new methods to the wrappers and calling the delegate, under the expectation that at runtime the wrapper methods would not be invoked in a JVM < 251. Or the wrappers could use reflection and throw a UOE if the methods are not available. > [1] https://www.oracle.com/technetwork/java/javase/8u251-relnotes-5972664.htm... > [2] https://hg.openjdk.java.net/jdk8u/jdk8u41/jdk/rev/b26b096d4c89 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5402) [Scesim Editor] Fit error reason to the popup

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-5402: ------------------------------------ Summary: [Scesim Editor] Fit error reason to the popup Key: DROOLS-5402 URL: https://issues.redhat.com/browse/DROOLS-5402 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Affects Versions: 7.38.0.Final Reporter: Anna Dupliak Assignee: Daniele Zonca Attachments: image-2020-06-03-09-20-34-662.png When package name is long then error reason gets out of the inline section of the popup !image-2020-06-03-09-20-34-662.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1979) Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1979?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1979: ---------------------------------- Fix Version/s: 1.12.1.CR1 > Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package > --------------------------------------------------------------------------- > > Key: ELY-1979 > URL: https://issues.redhat.com/browse/ELY-1979 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.12.0.Final > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.12.1.CR1 > > > JEPS 244, available in JDK 9 or later and in JDK 8 since the 251 release[1] has added new methods to some of the javax.net.ssl classes that elytron wraps in org.wildfly.security.ssl. But the elytron classes do not handle those new methods. I believe the relevant change is at [2] and updates the SSLEngine, SSLParameters and SSLSocket classes (plus various non-javax classes.) > If Elytron were to require 251 or later to build perhaps this could be a simple matter of adding new methods to the wrappers and calling the delegate, under the expectation that at runtime the wrapper methods would not be invoked in a JVM < 251. Or the wrappers could use reflection and throw a UOE if the methods are not available. > [1] https://www.oracle.com/technetwork/java/javase/8u251-relnotes-5972664.htm... > [2] https://hg.openjdk.java.net/jdk8u/jdk8u41/jdk/rev/b26b096d4c89 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020