September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1874) Fix for checking max-cert-path specified in X509RevocationTrustManager

by Ashley Abdel-Sayed (Jira)

Ashley Abdel-Sayed created ELY-1874: --------------------------------------- Summary: Fix for checking max-cert-path specified in X509RevocationTrustManager Key: ELY-1874 URL: https://issues.jboss.org/browse/ELY-1874 Project: WildFly Elytron Issue Type: Bug Reporter: Ashley Abdel-Sayed Assignee: Darran Lofthouse Currently, the maxCertPath is added as a parameter to PXIXBuilderParameters to be checked only when building the path. It should be updated to create a new PKIXConstraint to be checked when validating the path as well. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1874) Fix for checking max-cert-path specified in X509RevocationTrustManager

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/ELY-1874?page=com.atlassian.jira.plugin.s... ] Ashley Abdel-Sayed reassigned ELY-1874: --------------------------------------- Assignee: Ashley Abdel-Sayed (was: Darran Lofthouse) > Fix for checking max-cert-path specified in X509RevocationTrustManager > ---------------------------------------------------------------------- > > Key: ELY-1874 > URL: https://issues.jboss.org/browse/ELY-1874 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > > Currently, the maxCertPath is added as a parameter to PXIXBuilderParameters to be checked only when building the path. It should be updated to create a new PKIXConstraint to be checked when validating the path as well. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] James Perkins resolved WFLY-2859. --------------------------------- Fix Version/s: 18.0.0.Beta1 Resolution: Done > Treating all JAX-RS components as CDI Beans has some negative consequences > -------------------------------------------------------------------------- > > Key: WFLY-2859 > URL: https://issues.jboss.org/browse/WFLY-2859 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 8.0.0.CR1, 16.0.0.Beta1 > Reporter: Matt Drees > Assignee: Ronald Sigal > Priority: Major > Fix For: 18.0.0.Beta1 > > > It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class. > See the forum link for a specific instance of this. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences

by Ronald Sigal (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] Ronald Sigal commented on WFLY-2859: ------------------------------------ [~jamezp], I believe that https://issues.jboss.org/browse/RESTEASY-2315 solves the remaining issue, and it's incorporated into RESTEasy 3.9.0.Final. So, I'm going to say "yes". -Ron > Treating all JAX-RS components as CDI Beans has some negative consequences > -------------------------------------------------------------------------- > > Key: WFLY-2859 > URL: https://issues.jboss.org/browse/WFLY-2859 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 8.0.0.CR1, 16.0.0.Beta1 > Reporter: Matt Drees > Assignee: Ronald Sigal > Priority: Major > > It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class. > See the forum link for a specific instance of this. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-2859: ------------------------------------- [~ron_sigal] Does that mean this should be resolved? > Treating all JAX-RS components as CDI Beans has some negative consequences > -------------------------------------------------------------------------- > > Key: WFLY-2859 > URL: https://issues.jboss.org/browse/WFLY-2859 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 8.0.0.CR1, 16.0.0.Beta1 > Reporter: Matt Drees > Assignee: Ronald Sigal > Priority: Major > > It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class. > See the forum link for a specific instance of this. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12304) Upgrade Apache Artemis from 2.9.0 to 2.10.0

by Emmanuel Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-12304?page=com.atlassian.jira.plugin... ] Emmanuel Hugonnet updated WFLY-12304: ------------------------------------- Description: Upgrade Apache Artemis from 2.9.0.Final to 2.10.0.Final. Due to HA issue with Apache Artemis 2.10.0 this may not be the final version upgrade was: Upgrade Apache Artemis from 2.8.1.Final to 2.10.0.Final. Due to HA issue with Apache Artemis 2.10.0 this may not be the final version upgrade > Upgrade Apache Artemis from 2.9.0 to 2.10.0 > ------------------------------------------- > > Key: WFLY-12304 > URL: https://issues.jboss.org/browse/WFLY-12304 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Martin Stefanko > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: blocker-WF18, downstream_dependency > > Upgrade Apache Artemis from 2.9.0.Final to 2.10.0.Final. > Due to HA issue with Apache Artemis 2.10.0 this may not be the final version upgrade -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12304) Upgrade Apache Artemis from 2.8.1 to 2.10.0

by Emmanuel Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-12304?page=com.atlassian.jira.plugin... ] Emmanuel Hugonnet updated WFLY-12304: ------------------------------------- Description: Upgrade Apache Artemis from 2.8.1.Final to 2.10.0.Final. Due to HA issue with Apache Artemis 2.10.0 this may not be the final version upgrade was:Upgrade Apache Artemis from 2.8.1.Final to 2.10.0.Final. > Upgrade Apache Artemis from 2.8.1 to 2.10.0 > ------------------------------------------- > > Key: WFLY-12304 > URL: https://issues.jboss.org/browse/WFLY-12304 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Martin Stefanko > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: blocker-WF18, downstream_dependency > > Upgrade Apache Artemis from 2.8.1.Final to 2.10.0.Final. > Due to HA issue with Apache Artemis 2.10.0 this may not be the final version upgrade -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12304) Upgrade Apache Artemis from 2.9.0 to 2.10.0

by Emmanuel Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-12304?page=com.atlassian.jira.plugin... ] Emmanuel Hugonnet updated WFLY-12304: ------------------------------------- Summary: Upgrade Apache Artemis from 2.9.0 to 2.10.0 (was: Upgrade Apache Artemis from 2.8.1 to 2.10.0) > Upgrade Apache Artemis from 2.9.0 to 2.10.0 > ------------------------------------------- > > Key: WFLY-12304 > URL: https://issues.jboss.org/browse/WFLY-12304 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Martin Stefanko > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: blocker-WF18, downstream_dependency > > Upgrade Apache Artemis from 2.8.1.Final to 2.10.0.Final. > Due to HA issue with Apache Artemis 2.10.0 this may not be the final version upgrade -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12290) Class java.net.HttpClient not found in Wildfly 17

by Jaikiran Pai (Jira)

[ https://issues.jboss.org/browse/WFLY-12290?page=com.atlassian.jira.plugin... ] Jaikiran Pai commented on WFLY-12290: ------------------------------------- Just a FYI - this will need a new release of jboss-modules to bring in the change that was done as part of https://issues.jboss.org/browse/MODULES-392 > Class java.net.HttpClient not found in Wildfly 17 > ------------------------------------------------- > > Key: WFLY-12290 > URL: https://issues.jboss.org/browse/WFLY-12290 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 17.0.1.Final > Environment: Development: Win 10, JDK 11, Eclipse 2019-06 > Reporter: André Kornetzky > Assignee: Richard Opalka > Priority: Minor > Labels: Modules, jdk11 > > When I deploy my war module, I get the following error: > Caused by: java.lang.ClassNotFoundException: java.net.http.HttpClient from [Module "deployment.webservice-impl-1-3.0.0.war" from Service Module Loader] > In the same environment is also a Wildfly 16.0.0 installed. There the war module starts without errors. > In the discussion on https://developer.jboss.org/message/990207?et=watches.email.thread#990207 it was said that this was not considered by the upgrading of the JBoss module: > https://github.com/wildfly/wildfly-core/commit/fc649ab01eff81c55084d241fb... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3003) Enhance performance of PMML using decision trees

by Lance Leverich (Jira)

[ https://issues.jboss.org/browse/DROOLS-3003?page=com.atlassian.jira.plugi... ] Lance Leverich updated DROOLS-3003: ----------------------------------- Labels: PMMLRefactor (was: ) > Enhance performance of PMML using decision trees > ------------------------------------------------ > > Key: DROOLS-3003 > URL: https://issues.jboss.org/browse/DROOLS-3003 > Project: Drools > Issue Type: Enhancement > Components: PMML > Affects Versions: 7.12.0.Final > Reporter: Lance Leverich > Assignee: Lance Leverich > Priority: Major > Labels: PMMLRefactor > > Refactor the generation of rules and classes by the PMMLCompiler, for PMML resources containing Tree models. > # Replace any remaining instances of types declared in rules files with POJOs > # Reduce and/or remove the usage of rules in the process of generating rules and classes > # Expose/make available the POJO that is generated from the MiningSchema, so that it can be used as input, instead of PMMLRequestData type > # Update rules to make direct use of the input POJO -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 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 September 2019