February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14272) Upgrade to RestEasy 3.15.0.Final

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-14272?page=com.atlassian.jira.plugi... ] Ronald Sigal updated WFLY-14272: -------------------------------- Summary: Upgrade to RestEasy 3.15.0.Final (was: Upgrade to RestEasy 3.15) > Upgrade to RestEasy 3.15.0.Final > -------------------------------- > > Key: WFLY-14272 > URL: https://issues.redhat.com/browse/WFLY-14272 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Kabir Khan > Assignee: Alessio Soldano > Priority: Major > Labels: merged-to-feature-branch > Fix For: 23.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14453) Upgrade RESTEasy to 3.15.0.Final

by James Perkins (Jira)

James Perkins created WFLY-14453: ------------------------------------ Summary: Upgrade RESTEasy to 3.15.0.Final Key: WFLY-14453 URL: https://issues.redhat.com/browse/WFLY-14453 Project: WildFly Issue Type: Component Upgrade Components: MP REST Client, REST Reporter: James Perkins Assignee: James Perkins Upgrade RESTEasy to 3.15.0.Final which includes support for the Eclipse MicroProfile Rest Client 2.0. Diff: https://github.com/resteasy/Resteasy/compare/3.14.0.Final...3.15.0.Final -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14272) Upgrade to RestEasy 3.15

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-14272?page=com.atlassian.jira.plugi... ] Ronald Sigal updated WFLY-14272: -------------------------------- Fix Version/s: 23.0.0.Beta1 > Upgrade to RestEasy 3.15 > ------------------------ > > Key: WFLY-14272 > URL: https://issues.redhat.com/browse/WFLY-14272 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Kabir Khan > Assignee: Alessio Soldano > Priority: Major > Labels: merged-to-feature-branch > Fix For: 23.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14272) Upgrade to RestEasy 3.15

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-14272?page=com.atlassian.jira.plugi... ] Ronald Sigal commented on WFLY-14272: ------------------------------------- RESTEasy 3.15.0.Final is now tagged and uploaded. > Upgrade to RestEasy 3.15 > ------------------------ > > Key: WFLY-14272 > URL: https://issues.redhat.com/browse/WFLY-14272 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Kabir Khan > Assignee: Alessio Soldano > Priority: Major > Labels: merged-to-feature-branch > -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14312) Implement MicroProfile REST Client 2.0 additions

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-14312?page=com.atlassian.jira.plugi... ] Ronald Sigal commented on WFLY-14312: ------------------------------------- RESTEasy 3.15.0.Final, which incorporates RESTEASY-2750, is now tagged and uploaded. > Implement MicroProfile REST Client 2.0 additions > ------------------------------------------------ > > Key: WFLY-14312 > URL: https://issues.redhat.com/browse/WFLY-14312 > Project: WildFly > Issue Type: Feature Request > Reporter: r searls > Assignee: James Perkins > Priority: Major > Fix For: 23.0.0.Beta1 > > > Umbrella Jira for MP-rest-client 2.0 additions -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-12614) Duplicated ConstraintViolation message

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-12614?page=com.atlassian.jira.plugi... ] Ronald Sigal resolved WFLY-12614. --------------------------------- Resolution: Done > Duplicated ConstraintViolation message > -------------------------------------- > > Key: WFLY-12614 > URL: https://issues.redhat.com/browse/WFLY-12614 > Project: WildFly > Issue Type: Bug > Components: Bean Validation, REST > Affects Versions: 17.0.1.Final, 18.0.0.Beta1 > Reporter: Robin Schimpf > Assignee: Ronald Sigal > Priority: Major > Fix For: 19.0.0.Final > > Attachments: wildfly-bug.zip > > > We currently are upgrading our application from Wildfly 13 to Wildfly 17.0.1 and are receiving duplicated constraint violations in the response of an invalid request. > Interestingly Wildfly 13 also seems to be not behaving correctly on the third request but in another way. There is the violation exception returned in the response instead of the duplicated value Wildfly 17 is returning now. > I also tested this on the currently available Wildfly 18 Beta 1 and the issue is also reproducible. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-12614) Duplicated ConstraintViolation message

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-12614?page=com.atlassian.jira.plugi... ] Ronald Sigal updated WFLY-12614: -------------------------------- Fix Version/s: 19.0.0.Final > Duplicated ConstraintViolation message > -------------------------------------- > > Key: WFLY-12614 > URL: https://issues.redhat.com/browse/WFLY-12614 > Project: WildFly > Issue Type: Bug > Components: Bean Validation, REST > Affects Versions: 17.0.1.Final, 18.0.0.Beta1 > Reporter: Robin Schimpf > Assignee: Ronald Sigal > Priority: Major > Fix For: 19.0.0.Final > > Attachments: wildfly-bug.zip > > > We currently are upgrading our application from Wildfly 13 to Wildfly 17.0.1 and are receiving duplicated constraint violations in the response of an invalid request. > Interestingly Wildfly 13 also seems to be not behaving correctly on the third request but in another way. There is the violation exception returned in the response instead of the duplicated value Wildfly 17 is returning now. > I also tested this on the currently available Wildfly 18 Beta 1 and the issue is also reproducible. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14452) Refactor key affinity service factory implementation into wildfly-clustering-infinispan-spi module

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-14452: ----------------------------------- Summary: Refactor key affinity service factory implementation into wildfly-clustering-infinispan-spi module Key: WFLY-14452 URL: https://issues.redhat.com/browse/WFLY-14452 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 22.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro For re-use by wildfly-clustering-spring-session. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14312) Implement MicroProfile REST Client 2.0 additions

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-14312?page=com.atlassian.jira.plugi... ] James Perkins reassigned WFLY-14312: ------------------------------------ Assignee: James Perkins (was: r searls) > Implement MicroProfile REST Client 2.0 additions > ------------------------------------------------ > > Key: WFLY-14312 > URL: https://issues.redhat.com/browse/WFLY-14312 > Project: WildFly > Issue Type: Feature Request > Reporter: r searls > Assignee: James Perkins > Priority: Major > Fix For: 23.0.0.Beta1 > > > Umbrella Jira for MP-rest-client 2.0 additions -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-11638) MP Metrics - sort alphabetically /metrics output

by Jason Lee (Jira)

[ https://issues.redhat.com/browse/WFLY-11638?page=com.atlassian.jira.plugi... ] Jason Lee commented on WFLY-11638: ---------------------------------- [~rsvoboda], I just tested this with a MP metrics app, and all of the wildfly_* metrics were group together, and seem to be in alphabetical order. I'm inclined to close this with $RELEVANT_STATUS, but wanted to double check with you first. > MP Metrics - sort alphabetically /metrics output > ------------------------------------------------ > > Key: WFLY-11638 > URL: https://issues.redhat.com/browse/WFLY-11638 > Project: WildFly > Issue Type: Enhancement > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jason Lee > Priority: Major > > MP Metrics - sort alphabetically /metrics output > When playing with https://github.com/wildfly/wildfly/pull/11949 I got upset about metrics not being sorted alphabetically or at least grouped together. > My use case was to look at wildfly_undertow_** metrics via browser. > base: and vendor: metrics are grouped together, WF subsystem metrics not - e.g. wildfly_undertow_** metrics were listed on 4 different places. > If alphabetical order is not easy to be achieved, subsystem metrics should be at least grouped together. > I know machines do not care about the order, but people have to look at /metrics too (from time to time ...). -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 3 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 February 2021