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