October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4697) Upgrade WildFly Elytron to 1.11.0.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4697?page=com.atlassian.jira.plugi... ] Ivo Studensky reassigned WFCORE-4697: ------------------------------------- Assignee: Darran Lofthouse > Upgrade WildFly Elytron to 1.11.0.Final > --------------------------------------- > > Key: WFCORE-4697 > URL: https://issues.jboss.org/browse/WFCORE-4697 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Ivo Studensky > Assignee: Darran Lofthouse > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4709) Upgrade Undertow to 2.0.27.Final

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4709?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4709: ------------------------------------- Priority: Blocker (was: Major) > Upgrade Undertow to 2.0.27.Final > -------------------------------- > > Key: WFCORE-4709 > URL: https://issues.jboss.org/browse/WFCORE-4709 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Ivo Studensky > Assignee: Flavia Rainone > Priority: Blocker > Labels: downstream_dependency > > Upgrade Undertow to 2.0.27.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12662) Update BouncyCastle from 1.60 to 1.64

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFLY-12662?page=com.atlassian.jira.plugin... ] Rostislav Svoboda updated WFLY-12662: ------------------------------------- Summary: Update BouncyCastle from 1.60 to 1.64 (was: Update BouncyCastle) > Update BouncyCastle from 1.60 to 1.64 > ------------------------------------- > > Key: WFLY-12662 > URL: https://issues.jboss.org/browse/WFLY-12662 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > > Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12662) Update BouncyCastle

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFLY-12662?page=com.atlassian.jira.plugin... ] Rostislav Svoboda commented on WFLY-12662: ------------------------------------------ 1.64 bits are now available for bcprov-jdk15on, bcmail and bcpkix > Update BouncyCastle > ------------------- > > Key: WFLY-12662 > URL: https://issues.jboss.org/browse/WFLY-12662 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > > Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4710) Wrong BufferPoolMXBean name used in lookup

by Andrew Dinn (Jira)

Andrew Dinn created WFCORE-4710: ----------------------------------- Summary: Wrong BufferPoolMXBean name used in lookup Key: WFCORE-4710 URL: https://issues.jboss.org/browse/WFCORE-4710 Project: WildFly Core Issue Type: Enhancement Components: JMX Affects Versions: 10.0.0.Final Reporter: Andrew Dinn Assignee: Kabir Khan Class BufferPoolMXBeanResource transforms the name of retrieved MXBeans to handle embedded spaces and other special characters by calling method escapeMBeanName. Later on class BufferPoolMXBeanResourceAttributeHandler uses the name to identify the corresponding bean. Unfortunately, when BufferPoolMXBeanResourceAttributeHandler checks that the bean is registered it does not reverse the transformation by calling unescapeMBeanName. This causes a lookup failure when the new buffer pool non-volatiel memory MXBean is encountered on JDK14. Although Wildlfy appears to continue running the error message appears to cause failures in some of the Wildfly tests, notably those that check error stream output. See the referenced forum thread for full details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4635) [DMN Designer] Canvas is scrolled when going trough search results

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4635?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4635: -------------------------------- Summary: [DMN Designer] Canvas is scrolled when going trough search results (was: [DMN Designer] Constraints shown just for original data type definition) > [DMN Designer] Canvas is scrolled when going trough search results > ------------------------------------------------------------------ > > Key: DROOLS-4635 > URL: https://issues.jboss.org/browse/DROOLS-4635 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.28.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Optional > Labels: drools-tools > Attachments: searching-result.webm > > > Issue found during DROOLS-3727 review however probably it is not related. Int he attached video there is shown, that when graph contains has just one match for the search query and user repeatedly press *next match*, the canvas is slowly scrolling. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12668) Bean validation is done twice in JAX-RS application

by Daniel Munzinger (Jira)

Daniel Munzinger created WFLY-12668: --------------------------------------- Summary: Bean validation is done twice in JAX-RS application Key: WFLY-12668 URL: https://issues.jboss.org/browse/WFLY-12668 Project: WildFly Issue Type: Bug Components: Bean Validation, EJB, REST Affects Versions: 18.0.0.Final, 17.0.1.Final Environment: OpenJDK 11, reproduced on Win10 and Ubuntu 18.x Reporter: Daniel Munzinger Assignee: Cheng Fang If a JAX-RS resource is implemented as a stateless session bean then the validation is done twice: first on the EJB proxy and on the real implementation. This results in two constraint errors although there is basically just one error. The interesting part: If you resend the request. Then you get a proper result with just one violation. If you do a valid request and then an invalid you get the two violations again (see also the reproduce section). I created the issue here because I think it is an integration issue with JAX-RS, bean validation and EJBs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12668) Bean validation is done twice in JAX-RS application

by Daniel Munzinger (Jira)

[ https://issues.jboss.org/browse/WFLY-12668?page=com.atlassian.jira.plugin... ] Daniel Munzinger updated WFLY-12668: ------------------------------------ Steps to Reproduce: I created a basic examle at https://github.com/bender316/wildfly-validation-bug You can either download the wildfly-validation-bug.war or clone the repository and do "gradle war" and deploy the war in build/libs to the WildFly. Steps: 1. Deploy war 2. Do a valid POST request against http://localhost:9080/wildfly-validation-bug/rest/test with the body: {{ \{ "value": "123" \} }} 3. Do an invalid POST request with four characters (e.g. "1234" in the value field. 4. Check result. There should be two error messages with the same content. 5. Do 3. and 4. again. There should now be only 1 error message. 6. Repeat 2. to 5. was: I created a basic examle at https://github.com/bender316/wildfly-validation-bug You can either download the wildfly-validation-bug.war or clone the repository and do "gradle war" and deploy the war in build/libs to the WildFly. Steps: 1. Deploy war 2. Do a valid POST request against http://localhost:9080/wildfly-validation-bug/rest/test with the body: {{\{ "value": "123" \}}} 3. Do an invalid POST request with four characters (e.g. "1234" in the value field. 4. Check result. There should be two error messages with the same content. 5. Do 3. and 4. again. There should now be only 1 error message. 6. Repeat 2. to 5. > Bean validation is done twice in JAX-RS application > --------------------------------------------------- > > Key: WFLY-12668 > URL: https://issues.jboss.org/browse/WFLY-12668 > Project: WildFly > Issue Type: Bug > Components: Bean Validation, EJB, REST > Affects Versions: 17.0.1.Final, 18.0.0.Final > Environment: OpenJDK 11, reproduced on Win10 and Ubuntu 18.x > Reporter: Daniel Munzinger > Assignee: Cheng Fang > Priority: Major > > If a JAX-RS resource is implemented as a stateless session bean then the validation is done twice: first on the EJB proxy and on the real implementation. This results in two constraint errors although there is basically just one error. > The interesting part: If you resend the request. Then you get a proper result with just one violation. If you do a valid request and then an invalid you get the two violations again (see also the reproduce section). > I created the issue here because I think it is an integration issue with JAX-RS, bean validation and EJBs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12668) Bean validation is done twice in JAX-RS application

by Daniel Munzinger (Jira)

[ https://issues.jboss.org/browse/WFLY-12668?page=com.atlassian.jira.plugin... ] Daniel Munzinger updated WFLY-12668: ------------------------------------ Steps to Reproduce: I created a basic examle at https://github.com/bender316/wildfly-validation-bug You can either download the wildfly-validation-bug.war or clone the repository and do "gradle war" and deploy the war in build/libs to the WildFly. Steps: 1. Deploy war 2. Do a valid POST request against http://localhost:9080/wildfly-validation-bug/rest/test with the body: \{ "value": "123" \} 3. Do an invalid POST request with four characters (e.g. "1234" in the value field. 4. Check result. There should be two error messages with the same content. 5. Do 3. and 4. again. There should now be only 1 error message. 6. Repeat 2. to 5. was: I created a basic examle at https://github.com/bender316/wildfly-validation-bug You can either download the wildfly-validation-bug.war or clone the repository and do "gradle war" and deploy the war in build/libs to the WildFly. Steps: 1. Deploy war 2. Do a valid POST request against http://localhost:9080/wildfly-validation-bug/rest/test with the body: {{ \{ "value": "123" \} }} 3. Do an invalid POST request with four characters (e.g. "1234" in the value field. 4. Check result. There should be two error messages with the same content. 5. Do 3. and 4. again. There should now be only 1 error message. 6. Repeat 2. to 5. > Bean validation is done twice in JAX-RS application > --------------------------------------------------- > > Key: WFLY-12668 > URL: https://issues.jboss.org/browse/WFLY-12668 > Project: WildFly > Issue Type: Bug > Components: Bean Validation, EJB, REST > Affects Versions: 17.0.1.Final, 18.0.0.Final > Environment: OpenJDK 11, reproduced on Win10 and Ubuntu 18.x > Reporter: Daniel Munzinger > Assignee: Cheng Fang > Priority: Major > > If a JAX-RS resource is implemented as a stateless session bean then the validation is done twice: first on the EJB proxy and on the real implementation. This results in two constraint errors although there is basically just one error. > The interesting part: If you resend the request. Then you get a proper result with just one violation. If you do a valid request and then an invalid you get the two violations again (see also the reproduce section). > I created the issue here because I think it is an integration issue with JAX-RS, bean validation and EJBs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12621) Upgrade Hibernate ORM from 5.3.12 to 5.3.13

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFLY-12621?page=com.atlassian.jira.plugin... ] Ivo Studensky reassigned WFLY-12621: ------------------------------------ Assignee: Ivo Studensky (was: Gail Badner) > Upgrade Hibernate ORM from 5.3.12 to 5.3.13 > ------------------------------------------- > > Key: WFLY-12621 > URL: https://issues.jboss.org/browse/WFLY-12621 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 October 2019