[JBoss JIRA] (WFLY-11242) Provide builtin ParamConverter* classes for multi valued params
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11242?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11242:
---------------------------------
Fix Version/s: 15.0.0.CR1
(was: 15.0.0.Beta1)
> Provide builtin ParamConverter* classes for multi valued params
> ---------------------------------------------------------------
>
> Key: WFLY-11242
> URL: https://issues.jboss.org/browse/WFLY-11242
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Marek Kopecký
> Assignee: Ron Sigal
> Priority: Major
> Fix For: 15.0.0.CR1
>
>
> This is follow up for RESTEASY-1746 and RESTEASY-1566. In these feature jiras, users needs to prepare custom ParamConverter* classes in deployment.
> This feature should provide builtin ParamConverter* universal classes.
> Some PoC is in [this commit|https://github.com/marekkopecky/Resteasy/commit/08e0eb6de206085593...]
> Suitable annotations for end-point can parametrize converter behaviour. [~ron_sigal]'s proposal:
> {noformat}Maybe annotations in
> > public <T> ParamConverter<T> getConverter(Class<T> rawType, Type genericType, Annotation[] annotations;
> could be used to generalize. E.g.,
> public Response conversion1(@QueryParam @Separator("&") List<MultiValueParamBuiltinMyObject1> q);
> Even more general could be something like
> public Response conversion1(@QueryParam @MultiSyntax(<regular expression/>) List<MultiValueParamBuiltinMyObject1> q) {{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11352) WildFly registers multiple distinct drivers for current MySQL driver jar
by Stephen Fikes (Jira)
[ https://issues.jboss.org/browse/WFLY-11352?page=com.atlassian.jira.plugin... ]
Stephen Fikes commented on WFLY-11352:
--------------------------------------
Workarounds are:
# Run once then use the name reported at startup to reference the driver in the datasource (e.g. {{mysql-connector-java-5.1.44-bin.jar_com.mysql.jdbc.Driver_5_1}})
# Edit the MySQL driver's {{META-INF/services/java.sql.Driver}} file and remove the second entry (i.e. the entry for {{com.mysql.fabric.jdbc.FabricMySQLDriver}})
# Deploy the driver as a module
> WildFly registers multiple distinct drivers for current MySQL driver jar
> ------------------------------------------------------------------------
>
> Key: WFLY-11352
> URL: https://issues.jboss.org/browse/WFLY-11352
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 14.0.1.Final
> Reporter: Stephen Fikes
> Assignee: Stefano Maestri
> Priority: Major
>
> When MySQL drivers are deployed as jars (rather than [modules|https://issues.jboss.org/browse/WFLY-3218]), multiple named drivers:
> ... INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
> ... INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
> ... INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.jdbc.Driver_5_1
> ... INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
> Consequently, references to the driver by name (such as the below) fail to resolve
> {code}
> <datasource jndi-name="java:jboss/datasources/mysql" pool-name="MySQL" enabled="true">
> ...
> <driver>mysql-connector-java-5.1.44-bin.jar</driver>
> ...
> </datasource>
> {code}
> This issue was [already resolved|https://issues.jboss.org/browse/WFLY-3218] for the case where a module was used to deploy the driver.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11352) WildFly registers multiple distinct drivers for current MySQL driver jar
by Stephen Fikes (Jira)
Stephen Fikes created WFLY-11352:
------------------------------------
Summary: WildFly registers multiple distinct drivers for current MySQL driver jar
Key: WFLY-11352
URL: https://issues.jboss.org/browse/WFLY-11352
Project: WildFly
Issue Type: Bug
Components: JCA
Affects Versions: 14.0.1.Final
Reporter: Stephen Fikes
Assignee: Stefano Maestri
When MySQL drivers are deployed as jars (rather than [modules|https://issues.jboss.org/browse/WFLY-3218]), multiple named drivers:
... INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
... INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
... INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.jdbc.Driver_5_1
... INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
Consequently, references to the driver by name (such as the below) fail to resolve
{code}
<datasource jndi-name="java:jboss/datasources/mysql" pool-name="MySQL" enabled="true">
...
<driver>mysql-connector-java-5.1.44-bin.jar</driver>
...
</datasource>
{code}
This issue was [already resolved|https://issues.jboss.org/browse/WFLY-3218] for the case where a module was used to deploy the driver.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (SWSQE-502) Traffic Generator Not Working Properly On B06
by Matt Mahoney (Jira)
Matt Mahoney created SWSQE-502:
----------------------------------
Summary: Traffic Generator Not Working Properly On B06
Key: SWSQE-502
URL: https://issues.jboss.org/browse/SWSQE-502
Project: Kiali QE
Issue Type: Bug
Reporter: Matt Mahoney
Assignee: Michael Foley
Attachments: image-2018-11-14-15-53-30-017.png
on new cluster b06, the traffic generator appears not to be working properly. The symptom is that there Graphs have no node connections/edges.
!image-2018-11-14-15-53-30-017.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months