[JBoss JIRA] (WFCORE-4489) Missing quotes in wildfly\bin\standalone.bat
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4489?page=com.atlassian.jira.plugi... ]
James Perkins moved WFLY-12017 to WFCORE-4489:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-4489 (was: WFLY-12017)
Component/s: Scripts
(was: Scripts)
Affects Version/s: (was: 15.0.1.Final)
> Missing quotes in wildfly\bin\standalone.bat
> --------------------------------------------
>
> Key: WFCORE-4489
> URL: https://issues.jboss.org/browse/WFCORE-4489
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Environment: Windows 10
> Reporter: Joachim Petrich
> Assignee: James Perkins
> Priority: Major
>
> To be able to pass special characters (paratheses in our case) as Java options we added quotes in standalone.bat / line 251:
> set "JAVA_OPTS=%JAVA_OPTS% !TMP_PARAM!"
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFCORE-966) In domain mode non existing subhandler is saved to attributes.
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-966?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFCORE-966:
--------------------------------------
I though this would have been fixed by WFCORE-3337. However it does seem in {{admin-only}} mode on standalone or on a non-active domain profile you can still add invalid handler names. This is true for the loggers as well. Either capabilities can't guard against this, which I don't think is true, or there's something missing in the capability integration with the logging subsystem.
> In domain mode non existing subhandler is saved to attributes.
> --------------------------------------------------------------
>
> Key: WFCORE-966
> URL: https://issues.jboss.org/browse/WFCORE-966
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Environment: Running unsecured EAP 7.0.0 DR9 version in domain mode.
> Reporter: Patrik Cyprian
> Assignee: James Perkins
> Priority: Major
>
> When you in domain mode in created async handler add non existing sub handler to attributes it is successfully saved. In standalone mode it is not possible (subhandler is not saved - saving operation failed).
> 1.Run EAP in domain mode (default profile)
> 2.Create async handler
> 3.Try to add non existing subhandler to async handler attributes
> 4.Try the same in standalone mode with standalone-full-ha profile
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3976) [DMN Designer] edit cell by enter in Context, Function and Invocation
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3976?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3976:
-----------------------------------
Description:
Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
h3. Acceptance test
||#||Edit cell using mouse||Edit cell using keyboard||
|Literal Expression grid|(/)|(/)|
|Context grid|(/)|(/)|
|Invocation grid|(/)|(/)|
|Relation grid|(/)|(/)|
|Decision table grid|(/)|(/)|
was:
Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
h3. Acceptance test
||#||Edit cell using mouse||Edit cell using keyboard||
|Literal Expression grid|(/)|(/)|
|Context grid|(?)|(?)|
|Invocation grid|(?)|(?)|
|Relation grid|(?)|(?)|
|Decision table grid|(?)|(?)|
> [DMN Designer] edit cell by enter in Context, Function and Invocation
> ---------------------------------------------------------------------
>
> Key: DROOLS-3976
> URL: https://issues.jboss.org/browse/DROOLS-3976
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.21.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
> User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
> h3. Acceptance test
> ||#||Edit cell using mouse||Edit cell using keyboard||
> |Literal Expression grid|(/)|(/)|
> |Context grid|(/)|(/)|
> |Invocation grid|(/)|(/)|
> |Relation grid|(/)|(/)|
> |Decision table grid|(/)|(/)|
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3976) [DMN Designer] edit cell by enter in Context, Function and Invocation
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3976?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3976:
-----------------------------------
Description:
Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
h3. Acceptance test
||#||Edit cell using mouse||Edit cell using keyboard||
|Literal Expression grid|(/)|(/)|
|Context grid|(?)|(?)|
|Invocation grid|(?)|(?)|
|Relation grid|(?)|(?)|
|Decision table grid|(?)|(?)|
was:
Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
h3. Acceptance test
||#||Edit cell using mouse||Edit cell using keyboard||
|Literal Expression grid|(?)|(?)|
|Context grid|(?)|(?)|
|Invocation grid|(?)|(?)|
|Relation grid|(?)|(?)|
|Decision table grid|(?)|(?)|
> [DMN Designer] edit cell by enter in Context, Function and Invocation
> ---------------------------------------------------------------------
>
> Key: DROOLS-3976
> URL: https://issues.jboss.org/browse/DROOLS-3976
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.21.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
> User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
> h3. Acceptance test
> ||#||Edit cell using mouse||Edit cell using keyboard||
> |Literal Expression grid|(/)|(/)|
> |Context grid|(?)|(?)|
> |Invocation grid|(?)|(?)|
> |Relation grid|(?)|(?)|
> |Decision table grid|(?)|(?)|
--
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: (was: 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: 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 updated DROOLS-3731:
--------------------------------------
Attachment: (was: graph-test-hover.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-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 updated DROOLS-3731:
--------------------------------------
Attachment: (was: Test-error.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-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 updated DROOLS-3731:
--------------------------------------
Attachment: (was: with_some_callouts.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-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