[JBoss JIRA] (WFLY-11221) Agroal datasource cannot be used as DefaultDataSource without connector subsystem
by Martin Simka (Jira)
[ https://issues.jboss.org/browse/WFLY-11221?page=com.atlassian.jira.plugin... ]
Martin Simka updated WFLY-11221:
--------------------------------
Steps to Reproduce:
# remove datasource subsystem
# add agroal subsystem and define ExampleDS datasource
{code}
<extension module="org.wildfly.extension.datasources-agroal"/>
...
<subsystem xmlns="urn:jboss:domain:datasources-agroal:1.0">
<datasource name="ExampleDS" jndi-name="java:jboss/datasources/ExampleDS">
<connection-factory driver="h2" url="jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE" username="sa" password="sa">
</connection-factory>
<connection-pool max-size="30"/>
</datasource>
<drivers>
<driver name="h2" module="com.h2database.h2" class="org.h2.Driver"/>
</drivers>
</subsystem>
{code}
#Deploy application that injects DefaultDataSource
{code}
@Resource(lookup="java:comp/DefaultDataSource")
DataSource myDS;
{code}
was:
Deploy application that injects DefaultDataSource
{code}
@Resource(lookup="java:comp/DefaultDataSource")
DataSource myDS;
{code}
> Agroal datasource cannot be used as DefaultDataSource without connector subsystem
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11221
> URL: https://issues.jboss.org/browse/WFLY-11221
> Project: WildFly
> Issue Type: Bug
> Components: Agroal, EE, JCA
> Affects Versions: 14.0.0.Final
> Reporter: Martin Simka
> Assignee: Stefano Maestri
> Priority: Major
>
> If {{datasources}} subsystem is removed and {{Example}} datasource is created in {{datasources-agroal}} subsystem it is expected that Example datasource ({{java:jboss/datasources/ExampleDS}}) is bound to {{java:comp/DefaultDataSource}}, but it is not.
> {noformat}
> 12:33:17,605 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "testwebapplication.war")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.module.testwebapplication.testwebapplication.DefaultDataSource"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.testwebapplication.testwebapplication.env.\"org.jboss.qa.msimka.testwebapp.TestBean\".myDS is missing [jboss.naming.context.java.module.testwebapplication.testwebapplication.DefaultDataSource]"]
> }
> {noformat}
> JNDI of datasource that should be bound to default datasource can be defined in [ee subsystem|http://wildscribe.github.io/WildFly/14.0/subsystem/ee/service/default-bindings/index.html]
> Datasources subsystem is currently responsible for DefaultDatasource [binding|https://github.com/wildfly/wildfly/blob/master/connector/src/main...].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11221) Agroal datasource cannot be used as DefaultDataSource without connector subsystem
by Martin Simka (Jira)
[ https://issues.jboss.org/browse/WFLY-11221?page=com.atlassian.jira.plugin... ]
Martin Simka updated WFLY-11221:
--------------------------------
Steps to Reproduce:
# remove datasources subsystem
# add agroal subsystem and define ExampleDS datasource
{code}
<extension module="org.wildfly.extension.datasources-agroal"/>
...
<subsystem xmlns="urn:jboss:domain:datasources-agroal:1.0">
<datasource name="ExampleDS" jndi-name="java:jboss/datasources/ExampleDS">
<connection-factory driver="h2" url="jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE" username="sa" password="sa">
</connection-factory>
<connection-pool max-size="30"/>
</datasource>
<drivers>
<driver name="h2" module="com.h2database.h2" class="org.h2.Driver"/>
</drivers>
</subsystem>
{code}
#Deploy application that injects DefaultDataSource
{code}
@Resource(lookup="java:comp/DefaultDataSource")
DataSource myDS;
{code}
was:
# remove datasource subsystem
# add agroal subsystem and define ExampleDS datasource
{code}
<extension module="org.wildfly.extension.datasources-agroal"/>
...
<subsystem xmlns="urn:jboss:domain:datasources-agroal:1.0">
<datasource name="ExampleDS" jndi-name="java:jboss/datasources/ExampleDS">
<connection-factory driver="h2" url="jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE" username="sa" password="sa">
</connection-factory>
<connection-pool max-size="30"/>
</datasource>
<drivers>
<driver name="h2" module="com.h2database.h2" class="org.h2.Driver"/>
</drivers>
</subsystem>
{code}
#Deploy application that injects DefaultDataSource
{code}
@Resource(lookup="java:comp/DefaultDataSource")
DataSource myDS;
{code}
> Agroal datasource cannot be used as DefaultDataSource without connector subsystem
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11221
> URL: https://issues.jboss.org/browse/WFLY-11221
> Project: WildFly
> Issue Type: Bug
> Components: Agroal, EE, JCA
> Affects Versions: 14.0.0.Final
> Reporter: Martin Simka
> Assignee: Stefano Maestri
> Priority: Major
>
> If {{datasources}} subsystem is removed and {{Example}} datasource is created in {{datasources-agroal}} subsystem it is expected that Example datasource ({{java:jboss/datasources/ExampleDS}}) is bound to {{java:comp/DefaultDataSource}}, but it is not.
> {noformat}
> 12:33:17,605 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "testwebapplication.war")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.module.testwebapplication.testwebapplication.DefaultDataSource"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.testwebapplication.testwebapplication.env.\"org.jboss.qa.msimka.testwebapp.TestBean\".myDS is missing [jboss.naming.context.java.module.testwebapplication.testwebapplication.DefaultDataSource]"]
> }
> {noformat}
> JNDI of datasource that should be bound to default datasource can be defined in [ee subsystem|http://wildscribe.github.io/WildFly/14.0/subsystem/ee/service/default-bindings/index.html]
> Datasources subsystem is currently responsible for DefaultDatasource [binding|https://github.com/wildfly/wildfly/blob/master/connector/src/main...].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (SWSQE-462) Update Istio Upstream Job
by Guilherme Baufaker Rêgo (Jira)
Guilherme Baufaker Rêgo created SWSQE-462:
---------------------------------------------
Summary: Update Istio Upstream Job
Key: SWSQE-462
URL: https://issues.jboss.org/browse/SWSQE-462
Project: Kiali QE
Issue Type: Task
Reporter: Guilherme Baufaker Rêgo
Assignee: Michael Foley
Istio Upstream job is fixed on Istio 1.0.2 version.
That needs to be updated in order to permit using another versions of istio
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3168) Kmodule ruleTemplate should support csv files
by Webster Homer (Jira)
Webster Homer created DROOLS-3168:
-------------------------------------
Summary: Kmodule ruleTemplate should support csv files
Key: DROOLS-3168
URL: https://issues.jboss.org/browse/DROOLS-3168
Project: Drools
Issue Type: Feature Request
Components: core engine
Reporter: Webster Homer
Assignee: Mario Fusco
<ruleTemplate dtable="rules/business/TermSearchQFRules.csv"
template="rules/business/templates/TermSearchQF.drt"
row="2" col="1"/>
The kmodule ruleTemplate option should support csv files. However if you specify a csv file, drools will throw an error when it tries to process it:
"An error occurred opening the workbook. It is possible that the encoding of the document did not match the encoding of the reader."
Caused by: org.drools.template.parser.DecisionTableParseException: An error occurred opening the workbook. It is possible that the encoding of the document did not match the encoding of the reader.
at org.drools.decisiontable.parser.xls.ExcelParser.parseFile(ExcelParser.java:87)
Change the file to an .xlsx file and it works. We want to mange these files in source control and would prefer the csv version as it is ascii.
I know that the KIE code can handle the csv file with a template, that the ruleTemplate cannot is probably a bug
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3151:
--------------------------------
Description:
[~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns.
{quote}
this is way too subtle, to be honest... can we get colours that are a bit more distinguishable?
{quote}
See the attached screenshot.
Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.)
was:
[~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns.
{quote}
this is way too subtle, to be honest... can we get colours that are a bit more distinguishable?
{quote}
See the attached screenshot.
Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type
> [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-3151
> URL: https://issues.jboss.org/browse/DROOLS-3151
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.13.0.Final
> Reporter: Edson Tirelli
> Assignee: Michael Anstis
> Priority: Major
> Labels: VisualDesign, drools-tools
> Attachments: GDT.png, dtable-column-colours.png
>
>
> [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns.
> {quote}
> this is way too subtle, to be honest... can we get colours that are a bit more distinguishable?
> {quote}
> See the attached screenshot.
> Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months