[JBoss JIRA] (AG-134) Some issues in when use MSSQL SQLServerXADataSource
by bingo chen (Jira)
[ https://issues.redhat.com/browse/AG-134?page=com.atlassian.jira.plugin.sy... ]
bingo chen updated AG-134:
--------------------------
Description:
We use MSSQL as our data base server and use 'com.microsoft.sqlserver.jdbc.SQLServerXADataSource' as driver class.
Here some issues occured, the SQLServerXADataSource url property name is 'URL' not 'url', so we can't connect the data base server.
Environments:
1.JDBC driver is 'mssql-jdbc.7.2.2.jre8'
<dependency>
<groupId>com.microsoft.sqlserver</groupId>
<artifactId>mssql-jdbc</artifactId>
<version>7.2.2.jre8</version>
</dependency>
2.Agroal 1.7
<dependency>
<groupId>io.agroal</groupId>
<artifactId>agroal-api</artifactId>
<version>1.7</version>
</dependency>
<dependency>
<groupId>io.agroal</groupId>
<artifactId>agroal-pool</artifactId>
<version>1.7</version>
</dependency>
<dependency>
<groupId>io.agroal</groupId>
<artifactId>agroal-narayana</artifactId>
<version>1.7</version>
</dependency>
was:
We use MSSQL as our data base server and use 'com.microsoft.sqlserver.jdbc.SQLServerXADataSource' as driver class.
Here some issues occured, the SQLServerXADataSource url property name is 'dataSourceURL' not 'url', so we can't connect the data base server.
Environments:
1.JDBC driver is 'mssql-jdbc.7.2.2.jre8'
<dependency>
<groupId>com.microsoft.sqlserver</groupId>
<artifactId>mssql-jdbc</artifactId>
<version>7.2.2.jre8</version>
</dependency>
2.Agroal 1.7
<dependency>
<groupId>io.agroal</groupId>
<artifactId>agroal-api</artifactId>
<version>1.7</version>
</dependency>
<dependency>
<groupId>io.agroal</groupId>
<artifactId>agroal-pool</artifactId>
<version>1.7</version>
</dependency>
<dependency>
<groupId>io.agroal</groupId>
<artifactId>agroal-narayana</artifactId>
<version>1.7</version>
</dependency>
> Some issues in when use MSSQL SQLServerXADataSource
> ---------------------------------------------------
>
> Key: AG-134
> URL: https://issues.redhat.com/browse/AG-134
> Project: Agroal
> Issue Type: Enhancement
> Components: pool
> Affects Versions: 1.7
> Reporter: bingo chen
> Assignee: Luis Barreiro
> Priority: Major
>
> We use MSSQL as our data base server and use 'com.microsoft.sqlserver.jdbc.SQLServerXADataSource' as driver class.
> Here some issues occured, the SQLServerXADataSource url property name is 'URL' not 'url', so we can't connect the data base server.
> Environments:
> 1.JDBC driver is 'mssql-jdbc.7.2.2.jre8'
> <dependency>
> <groupId>com.microsoft.sqlserver</groupId>
> <artifactId>mssql-jdbc</artifactId>
> <version>7.2.2.jre8</version>
> </dependency>
> 2.Agroal 1.7
> <dependency>
> <groupId>io.agroal</groupId>
> <artifactId>agroal-api</artifactId>
> <version>1.7</version>
> </dependency>
> <dependency>
> <groupId>io.agroal</groupId>
> <artifactId>agroal-pool</artifactId>
> <version>1.7</version>
> </dependency>
> <dependency>
> <groupId>io.agroal</groupId>
> <artifactId>agroal-narayana</artifactId>
> <version>1.7</version>
> </dependency>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (AG-134) Some issues in when use MSSQL SQLServerXADataSource
by bingo chen (Jira)
[ https://issues.redhat.com/browse/AG-134?page=com.atlassian.jira.plugin.sy... ]
bingo chen updated AG-134:
--------------------------
Issue Type: Enhancement (was: Bug)
> Some issues in when use MSSQL SQLServerXADataSource
> ---------------------------------------------------
>
> Key: AG-134
> URL: https://issues.redhat.com/browse/AG-134
> Project: Agroal
> Issue Type: Enhancement
> Components: pool
> Affects Versions: 1.7
> Reporter: bingo chen
> Assignee: Luis Barreiro
> Priority: Major
>
> We use MSSQL as our data base server and use 'com.microsoft.sqlserver.jdbc.SQLServerXADataSource' as driver class.
> Here some issues occured, the SQLServerXADataSource url property name is 'dataSourceURL' not 'url', so we can't connect the data base server.
> Environments:
> 1.JDBC driver is 'mssql-jdbc.7.2.2.jre8'
> <dependency>
> <groupId>com.microsoft.sqlserver</groupId>
> <artifactId>mssql-jdbc</artifactId>
> <version>7.2.2.jre8</version>
> </dependency>
> 2.Agroal 1.7
> <dependency>
> <groupId>io.agroal</groupId>
> <artifactId>agroal-api</artifactId>
> <version>1.7</version>
> </dependency>
> <dependency>
> <groupId>io.agroal</groupId>
> <artifactId>agroal-pool</artifactId>
> <version>1.7</version>
> </dependency>
> <dependency>
> <groupId>io.agroal</groupId>
> <artifactId>agroal-narayana</artifactId>
> <version>1.7</version>
> </dependency>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (AG-134) Some issues in when use MSSQL SQLServerXADataSource
by bingo chen (Jira)
bingo chen created AG-134:
-----------------------------
Summary: Some issues in when use MSSQL SQLServerXADataSource
Key: AG-134
URL: https://issues.redhat.com/browse/AG-134
Project: Agroal
Issue Type: Bug
Components: pool
Affects Versions: 1.7
Reporter: bingo chen
Assignee: Luis Barreiro
We use MSSQL as our data base server and use 'com.microsoft.sqlserver.jdbc.SQLServerXADataSource' as driver class.
Here some issues occured, the SQLServerXADataSource url property name is 'dataSourceURL' not 'url', so we can't connect the data base server.
Environments:
1.JDBC driver is 'mssql-jdbc.7.2.2.jre8'
<dependency>
<groupId>com.microsoft.sqlserver</groupId>
<artifactId>mssql-jdbc</artifactId>
<version>7.2.2.jre8</version>
</dependency>
2.Agroal 1.7
<dependency>
<groupId>io.agroal</groupId>
<artifactId>agroal-api</artifactId>
<version>1.7</version>
</dependency>
<dependency>
<groupId>io.agroal</groupId>
<artifactId>agroal-pool</artifactId>
<version>1.7</version>
</dependency>
<dependency>
<groupId>io.agroal</groupId>
<artifactId>agroal-narayana</artifactId>
<version>1.7</version>
</dependency>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 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:
-------------------------------------
By the way, the RESTEasy testsuite has four relevant tests in the integration-tests submodule of the testsuite module:
* org.jboss.resteasy.test.microprofile.config.MicroProfileConfigFilterTest
* org.jboss.resteasy.test.microprofile.config.MicroProfileConfigServletContextListenerTest
* org.jboss.resteasy.test.microprofile.config.MicroProfileConfigServletTest
* org.jboss.resteasy.test.microprofile.config.MicroProfileConfigUseGlobalTest
> 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
>
> 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".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 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:
-------------------------------------
I've created a pull request (https://github.com/resteasy/Resteasy/pull/2250) with the necessary changes to RESTEasy for release 3.10.0.Final.
One thing I would like to reconsider is the proposal to implement the parameter "resteasy.config.resteasy.parameters.only". Thinking more about it, it seems awkward to restrict the scope of *some* ConfigSources when most of them, the default ConfigSources as well as those added in Wildfly, are out of RESTEasy's control. I'm thinking now that it makes more sense to allow any parameters to be retrieved in RESTEasy.
> 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
>
> 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".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JGRP-2425) RELAY2: new commands to print topology, site-masters, sites etc
by Bela Ban (Jira)
Bela Ban created JGRP-2425:
------------------------------
Summary: RELAY2: new commands to print topology, site-masters, sites etc
Key: JGRP-2425
URL: https://issues.redhat.com/browse/JGRP-2425
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.1.9
Add a bunch of utility commands, e.g. (from {{RelayDemo}}):
{noformat}
commands:
help
mbrs: prints the local members
site-masters (sm): prints the site masters of this site
sites: prints the configured sites
topo: prints the topology (site masters and local members of all sites)
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4894) DomainClassesMetadata java files are created under directories with dot separated name
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-4894?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi commented on DROOLS-4894:
-------------------------------------------
Yes, I see the issue on master (7.32.0-SNAPSHOT) with both kogito-examples and plain kie-maven-plugin (-DgenerateModel=YES).
> DomainClassesMetadata java files are created under directories with dot separated name
> --------------------------------------------------------------------------------------
>
> Key: DROOLS-4894
> URL: https://issues.redhat.com/browse/DROOLS-4894
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.31.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Luca Molteni
> Priority: Minor
>
> DomainClassesMetadataXXX java source files are created under directories with dot separated name instead of usual package hierarchy. It doesn't seem to cause issues though.
> For example, when I run kogito-examples/drools-quarkus-unit-example
> {noformat}
> $ mvn clean package
> ...
> $ tree target/generated-sources/
> target/generated-sources/
> ├── annotations
> └── kogito
> ├── org
> │ ├── drools
> │ │ └── project
> │ │ └── model
> │ │ ├── ProjectModel.java
> │ │ └── ProjectRuntime.java
> │ └── kie
> │ └── kogito
> │ ├── examples
> │ │ ├── ApplicationConfig.java
> │ │ └── Application.java
> │ ├── queries
> │ │ ├── AdultUnitDTO.java
> │ │ ├── AdultUnitQueryFindAdultNamesEndpoint.java
> │ │ ├── AdultUnitQueryFindAdultsEndpoint.java
> │ │ ├── AdultUnitQueryFindNotAdultNamesAndAgeEndpoint.java
> │ │ ├── AdultUnitRuleUnitInstance.java
> │ │ ├── AdultUnitRuleUnit.java
> │ │ ├── RulesF894883E1030542FEFCE9860F835B9B7_AdultUnit.java
> │ │ ├── RulesF894883E1030542FEFCE9860F835B9B7_AdultUnitRuleMethods0.java
> │ │ └── RulesF894883E1030542FEFCE9860F835B9B7.java
> │ └── rules
> │ └── alerting
> │ ├── LoggerServiceRuleUnitInstance.java
> │ ├── LoggerServiceRuleUnit.java
> │ ├── MonitoringServiceRuleUnitInstance.java
> │ ├── MonitoringServiceRuleUnit.java
> │ ├── Rules4723952D402A230BDB0E7081EBBA10E2.java
> │ ├── Rules4723952D402A230BDB0E7081EBBA10E2_LoggerService.java
> │ ├── Rules4723952D402A230BDB0E7081EBBA10E2_LoggerServiceRuleMethods0.java
> │ ├── Rules4723952D402A230BDB0E7081EBBA10E2_MonitoringService.java
> │ └── Rules4723952D402A230BDB0E7081EBBA10E2_MonitoringServiceRuleMethods0.java
> ├── org.kie.kogito.queries
> │ └── DomainClassesMetadataF894883E1030542FEFCE9860F835B9B7.java
> └── org.kie.kogito.rules.alerting
> └── DomainClassesMetadata4723952D402A230BDB0E7081EBBA10E2.java
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4895) Backport RuleUnitComponentFactory#createRuleUnitDescription( KiePackage, String );
by Edoardo Vacchi (Jira)
[ https://issues.redhat.com/browse/DROOLS-4895?page=com.atlassian.jira.plug... ]
Edoardo Vacchi updated DROOLS-4895:
-----------------------------------
Description:
add {{RuleUnitDescription createRuleUnitDescription( KiePackage pkg, String ruleUnitSimpleName );}} it should be a no-op because it is only used in Kogito
also {{RuleUnitDescriptionLoader}} may use this method in case {{createRuleUnitDescription( KiePackage pkg, Class<?> ruleUnit );} fails. However, this cannot happen in Drools 7, as the RuleUnit is always described by a Class, so it will always return null (it's a no-op after all). Reasons for backport are only code alignment.
was:add {{RuleUnitDescription createRuleUnitDescription( KiePackage pkg, String ruleUnitSimpleName );}} it should be a no-op because it is only used in Kogito
> Backport RuleUnitComponentFactory#createRuleUnitDescription( KiePackage, String );
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-4895
> URL: https://issues.redhat.com/browse/DROOLS-4895
> Project: Drools
> Issue Type: Bug
> Reporter: Edoardo Vacchi
> Assignee: Edoardo Vacchi
> Priority: Major
> Labels: drools-core
>
> add {{RuleUnitDescription createRuleUnitDescription( KiePackage pkg, String ruleUnitSimpleName );}} it should be a no-op because it is only used in Kogito
> also {{RuleUnitDescriptionLoader}} may use this method in case {{createRuleUnitDescription( KiePackage pkg, Class<?> ruleUnit );} fails. However, this cannot happen in Drools 7, as the RuleUnit is always described by a Class, so it will always return null (it's a no-op after all). Reasons for backport are only code alignment.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months