[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Roger Martinez (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Roger Martinez commented on DROOLS-3731:
----------------------------------------
mmmm that's also interesting [~uxdlc], so instead of a popup using some concrete panel for showing the errors, any error detail and providing related actions (like clear errors), tbh the mock looks great :)
[~manstis] Probably we could achieve that by improving the actual alerts widget?
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Test-error.png, Test-errorB.png, download (1).png, download.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[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
<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>
was:
Useful especially for clustrering 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: Jeff Mesnil
> 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
> <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>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-3731:
--------------------------------------
Attachment: Test-errorB.png
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Test-error.png, Test-errorB.png, download (1).png, download.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3731:
-------------------------------------------
[~jomarko] here's a mock that doesn't show the alerts in the Navigator, per your feedback. Thanks!
!Test-errorB.png|thumbnail!
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Test-error.png, Test-errorB.png, download (1).png, download.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[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 clustrering 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>
was:
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: Jeff Mesnil
> Priority: Major
>
> Useful especially for clustrering 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>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[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:
-----------------------------------
Affects Version/s: 9.0.0.Beta4
> 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: Jeff Mesnil
> Priority: Major
>
> 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>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[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 reassigned WFCORE-4459:
--------------------------------------
Component/s: Server
Summary: outbound-socket-binding element should allow grouping which subsystems can reference (was: outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol)
Assignee: Jeff Mesnil (was: Paul Ferraro)
> 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
> Reporter: Radoslav Husar
> Assignee: Jeff Mesnil
> Priority: Major
>
> 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>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFCORE-4459) outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFCORE-4459?page=com.atlassian.jira.plugi... ]
Radoslav Husar moved EAP7-1250 to WFCORE-4459:
----------------------------------------------
Project: WildFly Core (was: EAP 7 Planning Pilot)
Key: WFCORE-4459 (was: EAP7-1250)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0)
Component/s: (was: Clustering)
EAP PT Pre-Checked (PC): (was: TODO)
Target Release: (was: 7.backlog.GA)
EAP PT Community Docs (CD): (was: TODO)
EAP PT Product Docs (PD): (was: New)
EAP PT Test Dev (TD): (was: TODO)
EAP PT Docs Analysis (DA): (was: TODO)
EAP PT Test Plan (TP): (was: TODO)
EAP PT Analysis Document (AD): (was: TODO)
> outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4459
> URL: https://issues.jboss.org/browse/WFCORE-4459
> Project: WildFly Core
> Issue Type: Feature Request
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Major
>
> 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>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months