[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 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
# 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 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, 4 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 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
# 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
# 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
> 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 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
> # 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, 4 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 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
# 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
was:Refactoring for "Decision Table" editor
> 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 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
> # 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
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10036) Any tool to mirgrate my Jboss 5.1 project to Wildfly 10
by Hanuman Kumawat (JIRA)
Hanuman Kumawat created WFLY-10036:
--------------------------------------
Summary: Any tool to mirgrate my Jboss 5.1 project to Wildfly 10
Key: WFLY-10036
URL: https://issues.jboss.org/browse/WFLY-10036
Project: WildFly
Issue Type: Component Upgrade
Reporter: Hanuman Kumawat
Assignee: Jason Greene
Priority: Critical
Hi team,
I got a task to current project migrate to WildFly, so please need your help on this.
Below are my current project details-
JBoss 5.1
JDK 6
EJB 3
Hibernate 3
Oracle 11g
Thank you in advance!
Thanks & Regards,
Hanuman
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (LOGMGR-136) java.util.logging.LogManager removed deprecated property change listeners
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-136?page=com.atlassian.jira.plugin... ]
James Perkins updated LOGMGR-136:
---------------------------------
Fix Version/s: 2.1.1.Final
(was: 2.1.0.Final)
> java.util.logging.LogManager removed deprecated property change listeners
> -------------------------------------------------------------------------
>
> Key: LOGMGR-136
> URL: https://issues.jboss.org/browse/LOGMGR-136
> Project: JBoss Log Manager
> Issue Type: Sub-task
> Reporter: James Perkins
> Fix For: 2.1.1.Final
>
>
> Both the {{addPropertyChangeListener(PropertyChangeListener}} and {{removePropertyChangeListener(PropertyChangeListener}} were deprecated in Java 8 and removed in Java 9. There are two new replacement methods {{addConfigurationListener(Runnable)}} and {{removeConfigurationListener(Runnable)}} that have been added as replacements.
> For the JBoss Log Manager these could likely be no-ops like the originals were.
> In Java 9 to {{updateConfiguration()}} methods were added as well. These should also be overridden with no-ops.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (LOGMGR-52) Add option to WriterHandler to collapse repeated messages
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-52?page=com.atlassian.jira.plugin.... ]
James Perkins updated LOGMGR-52:
--------------------------------
Fix Version/s: 2.1.1.Final
(was: 2.1.0.Final)
> Add option to WriterHandler to collapse repeated messages
> ---------------------------------------------------------
>
> Key: LOGMGR-52
> URL: https://issues.jboss.org/browse/LOGMGR-52
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 2.1.1.Final
>
>
> The WriterHandler could have a time interval configured wherein a repeated message would be collapsed.
> The last message would be stored in a field for comparison along with a nanoTime tag (the timestamp on the message is not adequate because the clock can have skew or be reset completely at any time). If the current message string equals the last message string, and collapsing is enabled, then instead of logging the message, a count is incremented. If the current message is not equal, then the stored message is logged with a tag indicating the number of repeats (i18n?) and then the next submitted message is logged.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months