May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13541) Wrong behaviour in JSF UIInput's component

by Chao Wang (Jira)

Chao Wang created WFLY-13541: -------------------------------- Summary: Wrong behaviour in JSF UIInput's component Key: WFLY-13541 URL: https://issues.redhat.com/browse/WFLY-13541 Project: WildFly Issue Type: Bug Components: JSF Affects Versions: 19.1.0.Final Reporter: Chao Wang Assignee: Farah Juma If context parameter {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} set to True, then an empty value from UIInput component is not set to null any more. reproducer: https://github.com/soul2zimate/quickstart/tree/jsf-wrong-behaviour/hellow... -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5391) DMN external Java fn parameter resolution

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5391: -------------------------------------- Summary: DMN external Java fn parameter resolution Key: DROOLS-5391 URL: https://issues.redhat.com/browse/DROOLS-5391 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari When calling from DMN(BKM) an external static Java function, and the java function parameters type is coming from an external (maven) dependencies, the classloader used to resolve the type is not always the correct one. This JIRA fixes this problem -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13503) Websphere MQ Resource Adapter Configuration Does Not Take Effect Until Reboot

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-13503?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-13503: --------------------------------- Summary: Websphere MQ Resource Adapter Configuration Does Not Take Effect Until Reboot (was: [GSS](7.3.z) Websphere MQ Resource Adapter Configuration Does Not Take Effect Until Reboot) > Websphere MQ Resource Adapter Configuration Does Not Take Effect Until Reboot > ----------------------------------------------------------------------------- > > Key: WFLY-13503 > URL: https://issues.redhat.com/browse/WFLY-13503 > Project: WildFly > Issue Type: Bug > Components: Naming > Reporter: Parul Sharma > Assignee: Parul Sharma > Priority: Major > Labels: downstream_dependency > > When configuring the IBM Websphere Resource Adapter in JBoss 7.2.4 via the jboss-cli according to the directions in: > {code} > https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... > {code} > No JNDI entries are created for the connection factory and destination objects until the container is restarted. The documentation does not mention a restart being required to initialize the adapter and associated objects. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 3 months

1
0
0 / 0

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

by Kevin Wooten (Jira)

[ https://issues.redhat.com/browse/AG-144?page=com.atlassian.jira.plugin.sy... ] Kevin Wooten updated AG-144: ---------------------------- Description: `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 `int targetSqlType` variations (which are implemented) was: `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) > 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.7, 1.8 > Reporter: Kevin Wooten > Assignee: Luis Barreiro > Priority: Major > > `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 `int targetSqlType` variations (which are implemented) -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 3 months

1
0
0 / 0

[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)

2 years, 3 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)

2 years, 3 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)

2 years, 3 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)

2 years, 3 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)

2 years, 3 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)

2 years, 3 months

1
0
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2020