[JBoss JIRA] (WFCORE-4316) Spaces are not supported in a header value
by ehsavoie Hugonnet (Jira)
ehsavoie Hugonnet created WFCORE-4316:
-----------------------------------------
Summary: Spaces are not supported in a header value
Key: WFCORE-4316
URL: https://issues.jboss.org/browse/WFCORE-4316
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 8.0.0.Beta4
Reporter: ehsavoie Hugonnet
Assignee: Jean-Francois Denise
standalone@localhost:9990 /] echo-dmr /system-property=test30:add(value='my test'){GIT_MESSAGE=mon message}
{
"address" => [("system-property" => "test30")],
"operation" => "add",
"value" => "'my test'",
"operation-headers" => {"GIT_MESSAGE" => "monmessage"}
}
We have monmessage instead of mon message
Setting ignoreWhitespace to false in HeaderValueState fixes this but doesn't trim the result even if we are quoting (single or double) the value.
[standalone@localhost:9990 /] echo-dmr /system-property=test30:add(value='my test'){GIT_MESSAGE="mon message" ; header2=test}
The closing '"' is missing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 8 months
[JBoss JIRA] (WFCORE-4315) Upgrade the wildfly-maven-plugin to 1.2.1.Final
by Yeray Borges (Jira)
Yeray Borges created WFCORE-4315:
------------------------------------
Summary: Upgrade the wildfly-maven-plugin to 1.2.1.Final
Key: WFCORE-4315
URL: https://issues.jboss.org/browse/WFCORE-4315
Project: WildFly Core
Issue Type: Component Upgrade
Reporter: Yeray Borges
Assignee: Yeray Borges
Upgrade the wildfly-maven-plugin to version 1.2.1.Final
The sole intention of this upgrade is to include WFMP-88 fix in wildfly core.
notice the following; wildfly-full is already using 1.2.1.Final
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 8 months
[JBoss JIRA] (WFLY-10540) jboss-ejb-client.xml is unable to specify global cluster config
by Stefano Maestri (Jira)
[ https://issues.jboss.org/browse/WFLY-10540?page=com.atlassian.jira.plugin... ]
Stefano Maestri reassigned WFLY-10540:
--------------------------------------
Assignee: Paul Ferraro
> jboss-ejb-client.xml is unable to specify global cluster config
> ---------------------------------------------------------------
>
> Key: WFLY-10540
> URL: https://issues.jboss.org/browse/WFLY-10540
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Affects Versions: 13.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Paul Ferraro
> Priority: Critical
>
> When configuring an Wildfly instance with EJB Client applications to make remote EJB calls to another Wildfly instance with clustering enabled using a server to server connection configuration, the client Wildfly will specify remote-outbound-connection in the remoting subsystem. The client Wildfly instance will create and maintain these 2 connections in this example below.
> Client applications deployed on the client Wildfly instance will then package a jboss-ejb-client.xml in the application which specifies the remote server aliases that it wants to have access to.
> For the application to use clustered ejb, it then specifies the cluster information in the jboss-ejb-client.xml, where it has to specify connection information like username, connection options as opposed to just an alias as in the case of remoting-ejb-receiver.
> The cluster info should be configured in the JBoss profile xml so that client apps jboss-ejb-client.xml can just reference aliases like the non clustered connections to avoid applications creating their own connections to the same cluster nodes.
> {code}
> <subsystem xmlns="urn:jboss:domain:remoting:3.0">
> <endpoint/>
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
> <outbound-connections>
> <remote-outbound-connection name="remote-ejb-connection-1" outbound-socket-binding-ref="remote-ejb-1" username="ejbuser" security-realm="ApplicationRealm" protocol="http-remoting">
> <properties>
> <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
> <property name="SASL_DISALLOWED_MECHANISMS" value="JBOSS-LOCAL-USER"/>
> <property name="SSL_ENABLED" value="false"/>
> </properties>
> </remote-outbound-connection>
> <remote-outbound-connection name="remote-ejb-connection-2" outbound-socket-binding-ref="remote-ejb-2" username="ejbuser" security-realm="ApplicationRealm" protocol="http-remoting">
> <properties>
> <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
> <property name="SASL_DISALLOWED_MECHANISMS" value="JBOSS-LOCAL-USER"/>
> <property name="SSL_ENABLED" value="false"/>
> </properties>
> </remote-outbound-connection>
> </outbound-connections>
> </subsystem>
> {code}
> {code}
> <jboss-ejb-client xmlns:xsi="urn:jboss:ejb-client:1.2"
> xsi:noNamespaceSchemaLocation="jboss-ejb-client_1_2.xsd">
> <client-context>
> <ejb-receivers exclude-local-receiver="true">
> <remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection-1" />
> <remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection-2" />
> </ejb-receivers>
> <clusters>
> <cluster name="ejb" security-realm="ApplicationRealm"
> username="ejb-cluster-username">
> <connection-creation-options>
> <property name="org.xnio.Options.SSL_ENABLED" value="false" />
> <property name="org.xnio.Options.SASL_POLICY_NOANONYMOUS"
> value="false" />
> </connection-creation-options>
> </cluster>
> </clusters>
> </client-context>
> </jboss-ejb-client>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 8 months
[JBoss JIRA] (DROOLS-3218) [DMN Designer] UX enhancements for Parameters popover
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3218?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3218:
--------------------------------
Summary: [DMN Designer] UX enhancements for Parameters popover (was: [DMN Designer] UX for Parameters popover)
> [DMN Designer] UX enhancements for Parameters popover
> -----------------------------------------------------
>
> Key: DROOLS-3218
> URL: https://issues.jboss.org/browse/DROOLS-3218
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-3218.png
>
>
> The "Function Grid" allows for the definition of "parameters".
> For 7.14.0 (7.2) we went quick and dirty and have the attached (see screenshot) popover.
> The popover is launched by double-clicking the "parameters" cell in the grid.
> Could UX please work their magic?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 8 months
[JBoss JIRA] (DROOLS-3218) [DMN Designer] UX for Parameters popover
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3218?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3218:
--------------------------------
Affects Version/s: (was: 7.14.0.Final)
> [DMN Designer] UX for Parameters popover
> ----------------------------------------
>
> Key: DROOLS-3218
> URL: https://issues.jboss.org/browse/DROOLS-3218
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-3218.png
>
>
> The "Function Grid" allows for the definition of "parameters".
> For 7.14.0 (7.2) we went quick and dirty and have the attached (see screenshot) popover.
> The popover is launched by double-clicking the "parameters" cell in the grid.
> Could UX please work their magic?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 8 months