May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AG-144) PreparedStatement setObject variations are missing from wrapper

by Kevin Wooten (Jira)

Kevin Wooten created AG-144: ------------------------------- Summary: PreparedStatement setObject variations are missing from wrapper Key: AG-144 URL: https://issues.redhat.com/browse/AG-144 Project: Agroal Issue Type: Bug Components: pool Affects Versions: 1.8, 1.7 Reporter: Kevin Wooten Assignee: Luis Barreiro `PreparedStatementWrapper` doesn't implement the following variations of `PreparedStatement.setObject`.: void setObject(int parameterIndex, Object x, SQLType targetSqlType) void setObject(int parameterIndex, Object x, SQLType targetSqlType, int scaleOrLength) NOTE: These are the `SQLType` variations and not the `JDBCType` variations (which are implemented) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12779) Incorporate MicroProfile Config in RESTEasy

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-12779?page=com.atlassian.jira.plugi... ] Ronald Sigal commented on WFLY-12779: ------------------------------------- Ah. Thanks, [~jamezp]. > Incorporate MicroProfile Config in RESTEasy > ------------------------------------------- > > Key: WFLY-12779 > URL: https://issues.redhat.com/browse/WFLY-12779 > Project: WildFly > Issue Type: Feature Request > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > Fix For: 20.0.0.Beta1 > > > Currently, RESTEasy 3.x (targeted to Wildfly) uses servlet context-params to obtain configuration information. In RESTEasy 4.x, we have updated configuration to access all standard MicroProfile Config sources. Also, we have added three additional ConfigSources: > * servlet init-params (ordinal 60) > * filter init-params (ordinal 50) > * servlet context-params (ordinal 40) > In this feature request, we propose to port the relevant changes from RESTEasy 4.x to RESTEasy 3.x. > -In RESTEasy 4.x, all parameters, both RESTEasy parameters and application parameters, are available from all ConfigSources to both RESTEasy and application code. In RESTEasy 3.x, we propose to add a RESTEasy parameter, "resteasy.config.resteasy.parameters.only", which, when set to "true", will limit the three RESTEasy ConfigSources to returning RESTEasy parameters only. It will default to "true".- \[Ignore that.\] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13540) Ensure DefaultJMSConnection factory is first in the list to avoid null jndi bindings

by Ken Wills (Jira)

[ https://issues.redhat.com/browse/WFLY-13540?page=com.atlassian.jira.plugi... ] Ken Wills updated WFLY-13540: ----------------------------- Description: See: WFLY-13424 for underlying cause. > Ensure DefaultJMSConnection factory is first in the list to avoid null jndi bindings > ------------------------------------------------------------------------------------ > > Key: WFLY-13540 > URL: https://issues.redhat.com/browse/WFLY-13540 > Project: WildFly > Issue Type: Bug > Reporter: Ken Wills > Assignee: Ken Wills > Priority: Critical > > See: WFLY-13424 for underlying cause. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13540) Ensure DefaultJMSConnection factory is first in the list to avoid null jndi bindings

by Ken Wills (Jira)

Ken Wills created WFLY-13540: -------------------------------- Summary: Ensure DefaultJMSConnection factory is first in the list to avoid null jndi bindings Key: WFLY-13540 URL: https://issues.redhat.com/browse/WFLY-13540 Project: WildFly Issue Type: Bug Reporter: Ken Wills Assignee: Ken Wills -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13531) wildfly-cekit-modules: Remoting subsytem not present prevents full configuration of external message broker

by Ken Wills (Jira)

[ https://issues.redhat.com/browse/WFLY-13531?page=com.atlassian.jira.plugi... ] Ken Wills reassigned WFLY-13531: -------------------------------- Assignee: Ken Wills (was: Jeff Mesnil) > wildfly-cekit-modules: Remoting subsytem not present prevents full configuration of external message broker > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-13531 > URL: https://issues.redhat.com/browse/WFLY-13531 > Project: WildFly > Issue Type: Bug > Reporter: Ken Wills > Assignee: Ken Wills > Priority: Major > > See here: > https://github.com/wildfly/wildfly-cekit-modules/blob/master/jboss/contai... > When this returns 1 (remoting not present): > https://github.com/wildfly/wildfly-cekit-modules/blob/master/jboss/contai... > and once DISABLE_EMBEDDED_BROKER is set to always: > https://github.com/wildfly/wildfly-cekit-modules/blob/master/jboss/contai... > Will fail and /subsystem=ee/service=default-bindings:undefine-attribute(name=jms-connection-factory) will be executed instead, of the expected /subsystem=ee/service=default-bindings:write-attribute(name=jms-connection-factory, value=\"${defaultJmsConnectionFactoryJndi}\")" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12779) Incorporate MicroProfile Config in RESTEasy

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12779?page=com.atlassian.jira.plugi... ] James Perkins commented on WFLY-12779: -------------------------------------- I went ahead and resolved it Ron. It looks like the EAP7 JIRA needed to be resolved and proposal needed to be merged anyway. > Incorporate MicroProfile Config in RESTEasy > ------------------------------------------- > > Key: WFLY-12779 > URL: https://issues.redhat.com/browse/WFLY-12779 > Project: WildFly > Issue Type: Feature Request > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > Fix For: 20.0.0.Beta1 > > > Currently, RESTEasy 3.x (targeted to Wildfly) uses servlet context-params to obtain configuration information. In RESTEasy 4.x, we have updated configuration to access all standard MicroProfile Config sources. Also, we have added three additional ConfigSources: > * servlet init-params (ordinal 60) > * filter init-params (ordinal 50) > * servlet context-params (ordinal 40) > In this feature request, we propose to port the relevant changes from RESTEasy 4.x to RESTEasy 3.x. > -In RESTEasy 4.x, all parameters, both RESTEasy parameters and application parameters, are available from all ConfigSources to both RESTEasy and application code. In RESTEasy 3.x, we propose to add a RESTEasy parameter, "resteasy.config.resteasy.parameters.only", which, when set to "true", will limit the three RESTEasy ConfigSources to returning RESTEasy parameters only. It will default to "true".- \[Ignore that.\] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12779) Incorporate MicroProfile Config in RESTEasy

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12779?page=com.atlassian.jira.plugi... ] James Perkins resolved WFLY-12779. ---------------------------------- Fix Version/s: 20.0.0.Beta1 Resolution: Done > Incorporate MicroProfile Config in RESTEasy > ------------------------------------------- > > Key: WFLY-12779 > URL: https://issues.redhat.com/browse/WFLY-12779 > Project: WildFly > Issue Type: Feature Request > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > Fix For: 20.0.0.Beta1 > > > Currently, RESTEasy 3.x (targeted to Wildfly) uses servlet context-params to obtain configuration information. In RESTEasy 4.x, we have updated configuration to access all standard MicroProfile Config sources. Also, we have added three additional ConfigSources: > * servlet init-params (ordinal 60) > * filter init-params (ordinal 50) > * servlet context-params (ordinal 40) > In this feature request, we propose to port the relevant changes from RESTEasy 4.x to RESTEasy 3.x. > -In RESTEasy 4.x, all parameters, both RESTEasy parameters and application parameters, are available from all ConfigSources to both RESTEasy and application code. In RESTEasy 3.x, we propose to add a RESTEasy parameter, "resteasy.config.resteasy.parameters.only", which, when set to "true", will limit the three RESTEasy ConfigSources to returning RESTEasy parameters only. It will default to "true".- \[Ignore that.\] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13445) Upgrade RESTEasy to 3.12.0.Final

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-13445?page=com.atlassian.jira.plugi... ] Ronald Sigal commented on WFLY-13445: ------------------------------------- Hi [~ivassile], Here's the Release Notes for RESTEasy 3.12.0.Final: https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310560&vers... There's one Feature Request, https://issues.redhat.com/browse/RESTEASY-2406, in 3.12.0.Final. I'm not really sure what the rules are about backporting a feature, but I'm guessing it's ... problematic. As for FasterXML jackson, I was asked to include the upgrade with the RESTEasy upgrade because 1) FaxterXML jackson was upgraded in RESTEasy, and 2) RESTEasy is the main consumer of jackson in WildFly. As for WFLY-12779, it's complete by way of the upgrade of RESTEasy to 3.12.0.Final. I'm not sure who is supposed to resolve the issue. Anyway, I ran the RESTEasy 3.11.2.Final testsuite with jackson FasterXml set to 2.10.4, and it didn't make any difference. -Ron > Upgrade RESTEasy to 3.12.0.Final > -------------------------------- > > Key: WFLY-13445 > URL: https://issues.redhat.com/browse/WFLY-13445 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > Upgrade from 3.11.2.Final to 3.12.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13499) WildFly 20 Release Graphic

by James Cobb (Jira)

[ https://issues.redhat.com/browse/WFLY-13499?page=com.atlassian.jira.plugi... ] James Cobb commented on WFLY-13499: ----------------------------------- Added mockups to the design JIRA. > WildFly 20 Release Graphic > -------------------------- > > Key: WFLY-13499 > URL: https://issues.redhat.com/browse/WFLY-13499 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Brian Stansberry > Assignee: James Perkins > Priority: Blocker > Fix For: 20.0.0.Final > > > Get a graphic for wildfly.org for the WF 20 release. > This won't be needed if we will have cut over to the new site by the release date, but I think there's a good chance that will not be done. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13538) Add Java 9+ version of ConcurrentDirectDeque

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13538?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13538: -------------------------------- Description: The clustering code uses ConcurrentDirectDeque for its local scheduler implementation. While a portable implementation exists, a faster implementation that relies on sun.misc.Unsafe will be used when running with a compatible JVM. Now that jboss-parent includes profiles for multi-release jars, we can add a fast implementation (ported from Undertow) that uses VarHandle that will work on all Java9+ JVMs. was: The clustering code uses ConcurrentDirectDeque for its local scheduler implementation. While a portable implementation exists, there is also a faster version that relies on sun.misc.Unsafe. However, this only works in Java 8. Now that jboss-parent includes profiles for multi-release jars, we can add a variant (found in Undertow) that uses VarHandle to use on Java9+. > Add Java 9+ version of ConcurrentDirectDeque > -------------------------------------------- > > Key: WFLY-13538 > URL: https://issues.redhat.com/browse/WFLY-13538 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 20.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > The clustering code uses ConcurrentDirectDeque for its local scheduler implementation. While a portable implementation exists, a faster implementation that relies on sun.misc.Unsafe will be used when running with a compatible JVM. > Now that jboss-parent includes profiles for multi-release jars, we can add a fast implementation (ported from Undertow) that uses VarHandle that will work on all Java9+ JVMs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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