[JBoss JIRA] (DROOLS-1748) Drools workbench datasource on Wildfly domain.
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1748?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-1748:
-------------------------------------
Assignee: Petr Široký (was: Edson Tirelli)
> Drools workbench datasource on Wildfly domain.
> ----------------------------------------------
>
> Key: DROOLS-1748
> URL: https://issues.jboss.org/browse/DROOLS-1748
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.0.0.Final, 7.3.0.Final
> Environment: Drools workbench on Wildfly domain cluster
> Reporter: M C
> Assignee: Petr Široký
> Priority: Critical
>
> After starting workbench war (version 7.3 and 7.0, both Final) on Wildfly 10.1 domain cluster, got the issues with data source.
> [Server:server-one] 13:09:07,908 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: operation execution failed. :WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datasources")]
> Problem does not affect Wildfly standalone configuration, only domain configuration using profiles.
> WFLYCTL0030 warning says the syntax problem using jboss-cli.sh. In domain cluster it's used /profile=full-ha/subsystem=datasource/...
> In standalone syntax is: /subsystem=datasource/.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (DROOLS-1748) Drools workbench datasource on Wildfly domain.
by M C (JIRA)
M C created DROOLS-1748:
---------------------------
Summary: Drools workbench datasource on Wildfly domain.
Key: DROOLS-1748
URL: https://issues.jboss.org/browse/DROOLS-1748
Project: Drools
Issue Type: Bug
Affects Versions: 7.3.0.Final, 7.0.0.Final
Environment: Drools workbench on Wildfly domain cluster
Reporter: M C
Assignee: Edson Tirelli
Priority: Critical
After starting workbench war (version 7.3 and 7.0, both Final) on Wildfly 10.1 domain cluster, got the issues with data source.
[Server:server-one] 13:09:07,908 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: operation execution failed. :WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datasources")]
Problem does not affect Wildfly standalone configuration, only domain configuration using profiles.
WFLYCTL0030 warning says the syntax problem using jboss-cli.sh. In domain cluster it's used /profile=full-ha/subsystem=datasource/...
In standalone syntax is: /subsystem=datasource/.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-3180) ElytronSubsystemMessages uses double quotes to surround string literals
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3180?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3180:
------------------------------------------
Hi [~yersan] -- sure that would be fine.
> ElytronSubsystemMessages uses double quotes to surround string literals
> -----------------------------------------------------------------------
>
> Key: WFCORE-3180
> URL: https://issues.jboss.org/browse/WFCORE-3180
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Brian Stansberry
> Priority: Minor
>
> Lots of things like this:
> @Message(id = 910, value = "Password cannot be resolved for key-store \"%s\"")
> Use ' instead of \". If the string ends up in a DMR ModelNode, which it often does, the output looks bad when double quotes are present.
> For this ModelNode
> ModelNode node = new ModelNode("Password cannot be resolved for key-store \"%s\"");
>
> A call to node.toString() produces
> "Password cannot be resolved for key-store \"%s\""
> node.asString() is better, but that requires a special call vs the standard Object.toString
> Password cannot be resolved for key-store "%s"
> This is minor since we can try to ensure asString is used or perhaps even consider changing how toString works. But I think single quotes are a better practice.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-3180) ElytronSubsystemMessages uses double quotes to surround string literals
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3180?page=com.atlassian.jira.plugi... ]
Yeray Borges commented on WFCORE-3180:
--------------------------------------
[~brian.stansberry] just a random thought, would you be interested in a solution that works with LocalDescription.properties as well?
There are text descriptions using double quotes there. Those descriptions are "badly" scaped when they are displayed by read-resource-description for example, maybe it could be useful a general solution that takes those cases into account.
> ElytronSubsystemMessages uses double quotes to surround string literals
> -----------------------------------------------------------------------
>
> Key: WFCORE-3180
> URL: https://issues.jboss.org/browse/WFCORE-3180
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Brian Stansberry
> Priority: Minor
>
> Lots of things like this:
> @Message(id = 910, value = "Password cannot be resolved for key-store \"%s\"")
> Use ' instead of \". If the string ends up in a DMR ModelNode, which it often does, the output looks bad when double quotes are present.
> For this ModelNode
> ModelNode node = new ModelNode("Password cannot be resolved for key-store \"%s\"");
>
> A call to node.toString() produces
> "Password cannot be resolved for key-store \"%s\""
> node.asString() is better, but that requires a special call vs the standard Object.toString
> Password cannot be resolved for key-store "%s"
> This is minor since we can try to ensure asString is used or perhaps even consider changing how toString works. But I think single quotes are a better practice.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months