[JBoss JIRA] (DROOLS-2301) Decision Table editor
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2301?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2301:
--------------------------------
Description:
h1. Refactoring for "Decision Table" editor
h2. Acceptance criteria:
# Set table orientation (/)
## This should not be affected by the change of hit policy or table data
# Change hit policy (/)
## Change should be visible in most left upper cell
## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
# Clear decision table context entry clicking to any header cell (/)
# Add rule (/)
## Above
### Clicking to existing row number
### Clicking to existing cell
## Below
### Clicking to existing row number
### Clicking to existing cell
# Add input
## Before
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
## After
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
# Add output
## Before
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
## After
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
# Remove
## Input
## Output
## Rule
# Output clauses should be collapsed to one name
# Reorder
## Inputs separately
## Outputs separately
## inputs with outputs and vice versa shouldn't be allowed
## Description column should be prevented
## Rows of table
# Change column width
## Input
## Output
## Description
# Rename any input clause
# Rename any output clause
# Undo or Redo anything from this list (x)
##
# Save and reopen in any moment
# Use table as not most upper left context entry of decision
was:
h1. Refactoring for "Decision Table" editor
h2. Acceptance criteria:
# Set table orientation (/)
## This should not be affected by the change of hit policy or table data
# Change hit policy (/)
## Change should be visible in most left upper cell
## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
# Clear decision table context entry clicking to any header cell (/)
# Add rule (/)
## Above
### Clicking to existing row number
### Clicking to existing cell
## Below
### Clicking to existing row number
### Clicking to existing cell
# Add input
## Before
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
## After
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
# Add output
## Before
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
## After
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
# Remove
## Input
## Output
## Rule
# Output clauses should be collapsed to one name
# Reorder
## Inputs separately
## Outputs separately
## inputs with outputs and vice versa shouldn't be allowed
## Description column should be prevented
## Rows of table
# Change column width
## Input
## Output
## Description
# Rename any input clause
# Rename any output clause
# Undo or Redo anything from this list
# Save and reopen in any moment
# Use table as not most upper left context entry of decision
> Decision Table editor
> ---------------------
>
> Key: DROOLS-2301
> URL: https://issues.jboss.org/browse/DROOLS-2301
> Project: Drools
> Issue Type: Sub-task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> h1. Refactoring for "Decision Table" editor
> h2. Acceptance criteria:
> # Set table orientation (/)
> ## This should not be affected by the change of hit policy or table data
> # Change hit policy (/)
> ## Change should be visible in most left upper cell
> ## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
> # Clear decision table context entry clicking to any header cell (/)
> # Add rule (/)
> ## Above
> ### Clicking to existing row number
> ### Clicking to existing cell
> ## Below
> ### Clicking to existing row number
> ### Clicking to existing cell
> # Add input
> ## Before
> ### Clicking to existing input
> ### Clicking to existing output shouldn't allow to add input
> ## After
> ### Clicking to existing input
> ### Clicking to existing output shouldn't allow to add input
> # Add output
> ## Before
> ### Clicking to existing output
> ### Clicking to existing input shouldn't allow to add output
> ## After
> ### Clicking to existing output
> ### Clicking to existing input shouldn't allow to add output
> # Remove
> ## Input
> ## Output
> ## Rule
> # Output clauses should be collapsed to one name
> # Reorder
> ## Inputs separately
> ## Outputs separately
> ## inputs with outputs and vice versa shouldn't be allowed
> ## Description column should be prevented
> ## Rows of table
> # Change column width
> ## Input
> ## Output
> ## Description
> # Rename any input clause
> # Rename any output clause
> # Undo or Redo anything from this list (x)
> ##
> # Save and reopen in any moment
> # Use table as not most upper left context entry of decision
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2301) Decision Table editor
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2301?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2301:
--------------------------------
Description:
h1. Refactoring for "Decision Table" editor
h2. Acceptance criteria:
# Set table orientation (/)
## This should not be affected by the change of hit policy or table data
# Change hit policy (/)
## Change should be visible in most left upper cell
## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
# Clear decision table context entry clicking to any header cell (/)
# Add rule (/)
## Above
### Clicking to existing row number
### Clicking to existing cell
## Below
### Clicking to existing row number
### Clicking to existing cell
# Add input
## Before
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
## After
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
# Add output
## Before
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
## After
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
# Remove
## Input
## Output
## Rule
# Output clauses should be collapsed to one name
# Reorder
## Inputs separately
## Outputs separately
## inputs with outputs and vice versa shouldn't be allowed
## Description column should be prevented
## Rows of table
# Change column width
## Input
## Output
## Description
# Rename any input clause
# Rename any output clause
# Undo or Redo anything from this list
# Save and reopen in any moment
# Use table as not most upper left context entry of decision
was:
h1. Refactoring for "Decision Table" editor
h2. Acceptance criteria:
# Set table orientation (/)
## This should not be affected by the change of hit policy or table data
# Change hit policy (/)
## Change should be visible in most left upper cell
## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
# Clear decision table context entry clicking to any header cell (/)
# Add rule
## Above
### Clicking to existing row number
### Clicking to existing cell
## Below
### Clicking to existing row number
### Clicking to existing cell
# Add input
## Before
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
## After
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
# Add output
## Before
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
## After
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
# Remove
## Input
## Output
## Rule
# Output clauses should be collapsed to one name
# Reorder
## Inputs separately
## Outputs separately
## inputs with outputs and vice versa shouldn't be allowed
## Description column should be prevented
## Rows of table
# Change column width
## Input
## Output
## Description
# Rename any input clause
# Rename any output clause
# Undo or Redo anything from this list
# Save and reopen in any moment
# Use table as not most upper left context entry of decision
> Decision Table editor
> ---------------------
>
> Key: DROOLS-2301
> URL: https://issues.jboss.org/browse/DROOLS-2301
> Project: Drools
> Issue Type: Sub-task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> h1. Refactoring for "Decision Table" editor
> h2. Acceptance criteria:
> # Set table orientation (/)
> ## This should not be affected by the change of hit policy or table data
> # Change hit policy (/)
> ## Change should be visible in most left upper cell
> ## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
> # Clear decision table context entry clicking to any header cell (/)
> # Add rule (/)
> ## Above
> ### Clicking to existing row number
> ### Clicking to existing cell
> ## Below
> ### Clicking to existing row number
> ### Clicking to existing cell
> # Add input
> ## Before
> ### Clicking to existing input
> ### Clicking to existing output shouldn't allow to add input
> ## After
> ### Clicking to existing input
> ### Clicking to existing output shouldn't allow to add input
> # Add output
> ## Before
> ### Clicking to existing output
> ### Clicking to existing input shouldn't allow to add output
> ## After
> ### Clicking to existing output
> ### Clicking to existing input shouldn't allow to add output
> # Remove
> ## Input
> ## Output
> ## Rule
> # Output clauses should be collapsed to one name
> # Reorder
> ## Inputs separately
> ## Outputs separately
> ## inputs with outputs and vice versa shouldn't be allowed
> ## Description column should be prevented
> ## Rows of table
> # Change column width
> ## Input
> ## Output
> ## Description
> # Rename any input clause
> # Rename any output clause
> # Undo or Redo anything from this list
> # Save and reopen in any moment
> # Use table as not most upper left context entry of decision
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JGRP-2249) CENTRAL_LOCK2: reconciliation protocol on coord change
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2249?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2249:
---------------------------
Fix Version/s: 4.0.12
(was: 4.0.11)
> CENTRAL_LOCK2: reconciliation protocol on coord change
> ------------------------------------------------------
>
> Key: JGRP-2249
> URL: https://issues.jboss.org/browse/JGRP-2249
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0.12
>
>
> Implement a reconciliation protocol when the coord changes: instead of backing up all lock information to another member, the new coord asks all members for their current lock information (acquired locks, pending acquire and release requests) and constructs the lock table accordingly.
> This is described in https://issues.jboss.org/browse/JGRP-2234 (later comments).
> Comment from 2234:
> Clients need to have the following information:
> * Locks they acquired
> * Pending lock requests; locks which they want to acquire but for which they haven't yet received a LOCK_GRANTED response
> * Pending lock release requests; lock that have been released, but for which no RELEASE_LOCK_OK response has been received
> * Ditto for conditions, but we'll tackle them in a second stage
> The reconciliation protocol queues all new requests on the coord and asks all members for their lock information. Once the coord has received this information from all members, it applies this and then drains the queue of pending requests.
> It is important that the requests are ordered per member, ie. a release(L) cannot come before a lock(L).
> Since {{CENTRAL_LOCK}} allows for multiple members to hold the same lock in a split brain scenario, we need to think about how to handle merging where the coord detects that multiple members hold the same lock...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JGRP-2241) Bundler using direct memory as buffer
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2241?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2241:
---------------------------
Fix Version/s: 4.0.12
(was: 4.0.11)
> Bundler using direct memory as buffer
> -------------------------------------
>
> Key: JGRP-2241
> URL: https://issues.jboss.org/browse/JGRP-2241
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0.12
>
>
> The current bundler impls use a byte[] array in an output stream as buffer into which messages are written.
> If we instead used a direct byte buffer (off-heap), the JDK would not create an additional copy but simply pass the contents to the corresponding socket. This would reduce the memory allocation rate.
> Direct buffers can also be used on the receiver side, investigate.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JGRP-2227) Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2227?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2227:
---------------------------
Fix Version/s: 4.0.12
(was: 4.0.11)
> Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JGRP-2227
> URL: https://issues.jboss.org/browse/JGRP-2227
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.6
> Reporter: Robert Cernak
> Assignee: Bela Ban
> Fix For: 4.0.12
>
> Attachments: jgroupsLogs.zip
>
>
> I implemented method org.jgroups.auth.AuthToken#authenticate(AuthToken token, Message msg) in my class and its body contained only one line: return false;
> In this way authentication should be false and I should get SecurityException.
> When I started joining of nodes together to form a cluster, instead of getting SecurityException, nodes formed 2 different clusters with the same name.
> I am sure method was evaluated, since I tried to run it also with breakpoint, which was triggered during joining process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JGRP-2255) Message Bundling in TUNNEL mode
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2255?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2255:
---------------------------
Fix Version/s: 4.0.12
(was: 4.0.11)
> Message Bundling in TUNNEL mode
> -------------------------------
>
> Key: JGRP-2255
> URL: https://issues.jboss.org/browse/JGRP-2255
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 3.6.4
> Reporter: Bharad S
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0.12
>
>
> Hi, I'm using JGroups v3.6.4 and it is working great. I have a quick question --
> TUNNEL.java's 'send' method clearly says -- "// we don't currently support message bundling in TUNNEL"
> If I wish to use 'SenderSendsWithTimerBundler' (i.e., bundle and send when queued messages are 64K or 20ms have passed), could you please let me know what options I have? E.g., whether I need to use a later version that supports bundling with TUNNEL or is there some other option. Thanks!
> Regards,
> -Bharad
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2301) Decision Table editor
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2301?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2301:
--------------------------------
Description:
h1. Refactoring for "Decision Table" editor
h2. Acceptance criteria:
# Set table orientation (/)
## This should not be affected by the change of hit policy or table data
# Change hit policy (/)
## Change should be visible in most left upper cell
## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
# Clear decision table context entry clicking to any header cell (/)
# Add rule
## Above
### Clicking to existing row number
### Clicking to existing cell
## Below
### Clicking to existing row number
### Clicking to existing cell
# Add input
## Before
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
## After
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
# Add output
## Before
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
## After
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
# Remove
## Input
## Output
## Rule
# Output clauses should be collapsed to one name
# Reorder
## Inputs separately
## Outputs separately
## inputs with outputs and vice versa shouldn't be allowed
## Description column should be prevented
## Rows of table
# Change column width
## Input
## Output
## Description
# Rename any input clause
# Rename any output clause
# Undo or Redo anything from this list
# Save and reopen in any moment
# Use table as not most upper left context entry of decision
was:
h1. Refactoring for "Decision Table" editor
h2. Acceptance criteria:
# Set table orientation (/)
## This should not be affected by the change of hit policy or table data
# Change hit policy (/)
## Change should be visible in most left upper cell
## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
# Clear decision table context entry clicking to any header cell
# Add rule
## Above
### Clicking to existing row number
### Clicking to existing cell
## Below
### Clicking to existing row number
### Clicking to existing cell
# Add input
## Before
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
## After
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
# Add output
## Before
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
## After
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
# Remove
## Input
## Output
## Rule
# Output clauses should be collapsed to one name
# Reorder
## Inputs separately
## Outputs separately
## inputs with outputs and vice versa shouldn't be allowed
## Description column should be prevented
## Rows of table
# Change column width
## Input
## Output
## Description
# Rename any input clause
# Rename any output clause
# Undo or Redo anything from this list
# Save and reopen in any moment
# Use table as not most upper left context entry of decision
> Decision Table editor
> ---------------------
>
> Key: DROOLS-2301
> URL: https://issues.jboss.org/browse/DROOLS-2301
> Project: Drools
> Issue Type: Sub-task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> h1. Refactoring for "Decision Table" editor
> h2. Acceptance criteria:
> # Set table orientation (/)
> ## This should not be affected by the change of hit policy or table data
> # Change hit policy (/)
> ## Change should be visible in most left upper cell
> ## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
> # Clear decision table context entry clicking to any header cell (/)
> # Add rule
> ## Above
> ### Clicking to existing row number
> ### Clicking to existing cell
> ## Below
> ### Clicking to existing row number
> ### Clicking to existing cell
> # Add input
> ## Before
> ### Clicking to existing input
> ### Clicking to existing output shouldn't allow to add input
> ## After
> ### Clicking to existing input
> ### Clicking to existing output shouldn't allow to add input
> # Add output
> ## Before
> ### Clicking to existing output
> ### Clicking to existing input shouldn't allow to add output
> ## After
> ### Clicking to existing output
> ### Clicking to existing input shouldn't allow to add output
> # Remove
> ## Input
> ## Output
> ## Rule
> # Output clauses should be collapsed to one name
> # Reorder
> ## Inputs separately
> ## Outputs separately
> ## inputs with outputs and vice versa shouldn't be allowed
> ## Description column should be prevented
> ## Rows of table
> # Change column width
> ## Input
> ## Output
> ## Description
> # Rename any input clause
> # Rename any output clause
> # Undo or Redo anything from this list
> # Save and reopen in any moment
> # Use table as not most upper left context entry of decision
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2301) Decision Table editor
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2301?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2301:
--------------------------------
Description:
h1. Refactoring for "Decision Table" editor
h2. Acceptance criteria:
# Set table orientation (/)
## This should not be affected by the change of hit policy or table data
# Change hit policy (/)
## Change should be visible in most left upper cell
## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
# Clear decision table context entry clicking to any header cell
# Add rule
## Above
### Clicking to existing row number
### Clicking to existing cell
## Below
### Clicking to existing row number
### Clicking to existing cell
# Add input
## Before
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
## After
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
# Add output
## Before
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
## After
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
# Remove
## Input
## Output
## Rule
# Output clauses should be collapsed to one name
# Reorder
## Inputs separately
## Outputs separately
## inputs with outputs and vice versa shouldn't be allowed
## Description column should be prevented
## Rows of table
# Change column width
## Input
## Output
## Description
# Rename any input clause
# Rename any output clause
# Undo or Redo anything from this list
# Save and reopen in any moment
# Use table as not most upper left context entry of decision
was:
h1. Refactoring for "Decision Table" editor
h2. Acceptance criteria:
# Set table orientation (/)
## This should not be affected by the change of hit policy or table data
# Change hit policy (/)
## Change should be visible in most left upper cell
## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
# Clear decision table context entry clicking to any cell
# Add rule
## Above
### Clicking to existing row number
### Clicking to existing cell
## Below
### Clicking to existing row number
### Clicking to existing cell
# Add input
## Before
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
## After
### Clicking to existing input
### Clicking to existing output shouldn't allow to add input
# Add output
## Before
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
## After
### Clicking to existing output
### Clicking to existing input shouldn't allow to add output
# Remove
## Input
## Output
## Rule
# Output clauses should be collapsed to one name
# Reorder
## Inputs separately
## Outputs separately
## inputs with outputs and vice versa shouldn't be allowed
## Description column should be prevented
## Rows of table
# Change column width
## Input
## Output
## Description
# Rename any input clause
# Rename any output clause
# Undo or Redo anything from this list
# Save and reopen in any moment
# Use table as not most upper left context entry of decision
> Decision Table editor
> ---------------------
>
> Key: DROOLS-2301
> URL: https://issues.jboss.org/browse/DROOLS-2301
> Project: Drools
> Issue Type: Sub-task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> h1. Refactoring for "Decision Table" editor
> h2. Acceptance criteria:
> # Set table orientation (/)
> ## This should not be affected by the change of hit policy or table data
> # Change hit policy (/)
> ## Change should be visible in most left upper cell
> ## If {{COLLECT <function>}} was selected, then hit policy changed and then again {{COLLECT}} selected, then {{<function>}} should be same as previously
> # Clear decision table context entry clicking to any header cell
> # Add rule
> ## Above
> ### Clicking to existing row number
> ### Clicking to existing cell
> ## Below
> ### Clicking to existing row number
> ### Clicking to existing cell
> # Add input
> ## Before
> ### Clicking to existing input
> ### Clicking to existing output shouldn't allow to add input
> ## After
> ### Clicking to existing input
> ### Clicking to existing output shouldn't allow to add input
> # Add output
> ## Before
> ### Clicking to existing output
> ### Clicking to existing input shouldn't allow to add output
> ## After
> ### Clicking to existing output
> ### Clicking to existing input shouldn't allow to add output
> # Remove
> ## Input
> ## Output
> ## Rule
> # Output clauses should be collapsed to one name
> # Reorder
> ## Inputs separately
> ## Outputs separately
> ## inputs with outputs and vice versa shouldn't be allowed
> ## Description column should be prevented
> ## Rows of table
> # Change column width
> ## Input
> ## Output
> ## Description
> # Rename any input clause
> # Rename any output clause
> # Undo or Redo anything from this list
> # Save and reopen in any moment
> # Use table as not most upper left context entry of decision
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months