[JBoss JIRA] (WFCORE-4459) outbound-socket-binding element should allow grouping which subsystems can reference
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFCORE-4459?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFCORE-4459:
-----------------------------------
Description:
Useful especially for clustering subsystems like jgroups discovery protocols, infinispan hotrod servers, and mod_cluster balancers.
----
JGroups configuration can use two different ways to configure cluster detection
------ older configuration is via protocol properties --
<protocol type="TCPPING">
<property name="initial_hosts">host[7600]</property>
------ new configuration via socket reference
<socket-discovery-protocol type="TCPPING" socket-bindings="ref-a ref-b"/>
...
<outbound-socket-binding name="ref-a">
<remote-destination host="127.0.0.1" port="7600"/>
</outbound-socket-binding>
-----------
with the old option it is possible to use an expression to set all hosts in a cluster.
The new one need to have all outbound connections listed which is harder to maintain.
As an administrator I want to have the possibility to group the connections and only have one reference and the number of connections can be vary without changing multiple point in the configuration.
So a configuration like this would enhance that
{code:xml}
<outbound-socket-binding-group>
<outbound-socket-binding name="ref-a">
<remote-destination host="host1" port="7600"/>
</outbound-socket-binding>
<outbound-socket-binding name="ref-b">
<remote-destination host="host2" port="7600"/>
</outbound-socket-binding>
</outbound-socket-binding-group>
{code}
was:
Useful especially for clustering subsystems like jgroups discovery protocols, infinispan hotrod servers, and mod_cluster balancers.
----
JGroups configuration can use two different ways to configure cluster detection
------ older configuration is via protocol properties --
<protocol type="TCPPING">
<property name="initial_hosts">host[7600]</property>
------ new configuration via socket reference
<socket-discovery-protocol type="TCPPING" socket-bindings="ref-a ref-b"/>
...
<outbound-socket-binding name="ref-a">
<remote-destination host="127.0.0.1" port="7600"/>
</outbound-socket-binding>
-----------
with the old option it is possible to use an expression to set all hosts in a cluster.
The new one need to have all outbound connections listed which is harder to maintain.
As an administrator I want to have the possibility to group the connections and only have one reference and the number of connections can be vary without changing multiple point in the configuration.
So a configuration like this would enhance that
<outbound-socket-binding-group>
<outbound-socket-binding name="ref-a">
<remote-destination host="host1" port="7600"/>
</outbound-socket-binding>
<outbound-socket-binding name="ref-b">
<remote-destination host="host2" port="7600"/>
</outbound-socket-binding>
</outbound-socket-binding-group>
> outbound-socket-binding element should allow grouping which subsystems can reference
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-4459
> URL: https://issues.jboss.org/browse/WFCORE-4459
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.0.0.Beta4
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> Useful especially for clustering subsystems like jgroups discovery protocols, infinispan hotrod servers, and mod_cluster balancers.
> ----
> JGroups configuration can use two different ways to configure cluster detection
> ------ older configuration is via protocol properties --
> <protocol type="TCPPING">
> <property name="initial_hosts">host[7600]</property>
> ------ new configuration via socket reference
> <socket-discovery-protocol type="TCPPING" socket-bindings="ref-a ref-b"/>
> ...
> <outbound-socket-binding name="ref-a">
> <remote-destination host="127.0.0.1" port="7600"/>
> </outbound-socket-binding>
> -----------
> with the old option it is possible to use an expression to set all hosts in a cluster.
> The new one need to have all outbound connections listed which is harder to maintain.
> As an administrator I want to have the possibility to group the connections and only have one reference and the number of connections can be vary without changing multiple point in the configuration.
> So a configuration like this would enhance that
> {code:xml}
> <outbound-socket-binding-group>
> <outbound-socket-binding name="ref-a">
> <remote-destination host="host1" port="7600"/>
> </outbound-socket-binding>
> <outbound-socket-binding name="ref-b">
> <remote-destination host="host2" port="7600"/>
> </outbound-socket-binding>
> </outbound-socket-binding-group>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4178) [DMN Designer] Selected Node Is selected also in Documentation
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4178?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-4178:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] Selected Node Is selected also in Documentation
> --------------------------------------------------------------
>
> Key: DROOLS-4178
> URL: https://issues.jboss.org/browse/DROOLS-4178
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2019-06-13 11-31-38.png
>
>
> User has possibility to export documentation of a dmn diagram. Such documentation contains a picture of the diagram. The issue is the picture has highlighted some nodes, if those were selected in the designer model tab.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months