[JBoss JIRA] (WFCORE-4908) The write-attribute operation does not work on a hosts JVM resource
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-4908?page=com.atlassian.jira.plug... ]
Brian Stansberry edited comment on WFCORE-4908 at 4/14/20 10:17 PM:
--------------------------------------------------------------------
Thanks, guys. The problem is EnhancedSyntaxSupport.updateWithEnhancedSyntax isn't very careful about seeing whether the 'attributeExpression' it is given has anything to do with the actual model structure. I threw up https://github.com/wildfly/wildfly-core/pull/4158 which fixes it.
was (Author: brian.stansberry):
Thanks, guys. The problem is EnhancedSyntaxSupport.updateWithEnhancedSyntax isn't very careful about seeing whether the 'attributeExpression' it is given has anything to do with the actual model structure. I threw up https://github.com/bstansberry/wildfly-core/commit/2f3eac59ce2423475718c3... which causes this bad op to correctly fail but it breaks some unit tests, which I've no time to look at.
> The write-attribute operation does not work on a hosts JVM resource
> -------------------------------------------------------------------
>
> Key: WFCORE-4908
> URL: https://issues.redhat.com/browse/WFCORE-4908
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: Jeff Mesnil
> Priority: Major
> Labels: domain-mode
>
> Under a hosts server config, {{/host=master/server-config=server-one/}}, there is a {{jvm}} resource. On this resource the {{write-attribute}} operation does not work expected.
> {code}
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:add
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options["-Xlog:gc*:file=${jboss.domain.servers.dir}/server-two/log/gc.log"])
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:read-resource
> {
> "outcome" => "success",
> "result" => {
> "agent-lib" => undefined,
> "agent-path" => undefined,
> "debug-enabled" => undefined,
> "debug-options" => undefined,
> "env-classpath-ignored" => undefined,
> "environment-variables" => undefined,
> "heap-size" => undefined,
> "java-agent" => undefined,
> "java-home" => undefined,
> "jvm-options" => undefined,
> "launch-command" => undefined,
> "max-heap-size" => undefined,
> "max-permgen-size" => undefined,
> "permgen-size" => undefined,
> "stack-size" => undefined,
> "type" => undefined
> }
> }
> {code}
> As you can see from the above command does not update the {{jvm-options}}. However if you use the {{add-jvm-option}} operation that does work. It seems the {{write-attribute}} operation should also work.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFCORE-4908) The write-attribute operation does not work on a hosts JVM resource
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-4908?page=com.atlassian.jira.plug... ]
Brian Stansberry reassigned WFCORE-4908:
----------------------------------------
Assignee: Brian Stansberry (was: Jeff Mesnil)
> The write-attribute operation does not work on a hosts JVM resource
> -------------------------------------------------------------------
>
> Key: WFCORE-4908
> URL: https://issues.redhat.com/browse/WFCORE-4908
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: Brian Stansberry
> Priority: Major
> Labels: domain-mode
>
> Under a hosts server config, {{/host=master/server-config=server-one/}}, there is a {{jvm}} resource. On this resource the {{write-attribute}} operation does not work expected.
> {code}
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:add
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options["-Xlog:gc*:file=${jboss.domain.servers.dir}/server-two/log/gc.log"])
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:read-resource
> {
> "outcome" => "success",
> "result" => {
> "agent-lib" => undefined,
> "agent-path" => undefined,
> "debug-enabled" => undefined,
> "debug-options" => undefined,
> "env-classpath-ignored" => undefined,
> "environment-variables" => undefined,
> "heap-size" => undefined,
> "java-agent" => undefined,
> "java-home" => undefined,
> "jvm-options" => undefined,
> "launch-command" => undefined,
> "max-heap-size" => undefined,
> "max-permgen-size" => undefined,
> "permgen-size" => undefined,
> "stack-size" => undefined,
> "type" => undefined
> }
> }
> {code}
> As you can see from the above command does not update the {{jvm-options}}. However if you use the {{add-jvm-option}} operation that does work. It seems the {{write-attribute}} operation should also work.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFCORE-4908) The write-attribute operation does not work on a hosts JVM resource
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-4908?page=com.atlassian.jira.plug... ]
Brian Stansberry commented on WFCORE-4908:
------------------------------------------
Thanks, guys. The problem is EnhancedSyntaxSupport.updateWithEnhancedSyntax isn't very careful about seeing whether the 'attributeExpression' it is given has anything to do with the actual model structure. I threw up https://github.com/bstansberry/wildfly-core/commit/2f3eac59ce2423475718c3... which causes this bad op to correctly fail but it breaks some unit tests, which I've no time to look at.
> The write-attribute operation does not work on a hosts JVM resource
> -------------------------------------------------------------------
>
> Key: WFCORE-4908
> URL: https://issues.redhat.com/browse/WFCORE-4908
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: Jeff Mesnil
> Priority: Major
> Labels: domain-mode
>
> Under a hosts server config, {{/host=master/server-config=server-one/}}, there is a {{jvm}} resource. On this resource the {{write-attribute}} operation does not work expected.
> {code}
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:add
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options["-Xlog:gc*:file=${jboss.domain.servers.dir}/server-two/log/gc.log"])
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:read-resource
> {
> "outcome" => "success",
> "result" => {
> "agent-lib" => undefined,
> "agent-path" => undefined,
> "debug-enabled" => undefined,
> "debug-options" => undefined,
> "env-classpath-ignored" => undefined,
> "environment-variables" => undefined,
> "heap-size" => undefined,
> "java-agent" => undefined,
> "java-home" => undefined,
> "jvm-options" => undefined,
> "launch-command" => undefined,
> "max-heap-size" => undefined,
> "max-permgen-size" => undefined,
> "permgen-size" => undefined,
> "stack-size" => undefined,
> "type" => undefined
> }
> }
> {code}
> As you can see from the above command does not update the {{jvm-options}}. However if you use the {{add-jvm-option}} operation that does work. It seems the {{write-attribute}} operation should also work.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFCORE-4908) The write-attribute operation does not work on a hosts JVM resource
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-4908?page=com.atlassian.jira.plug... ]
Brian Stansberry updated WFCORE-4908:
-------------------------------------
Component/s: (was: CLI)
> The write-attribute operation does not work on a hosts JVM resource
> -------------------------------------------------------------------
>
> Key: WFCORE-4908
> URL: https://issues.redhat.com/browse/WFCORE-4908
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: Jeff Mesnil
> Priority: Major
> Labels: domain-mode
>
> Under a hosts server config, {{/host=master/server-config=server-one/}}, there is a {{jvm}} resource. On this resource the {{write-attribute}} operation does not work expected.
> {code}
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:add
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options["-Xlog:gc*:file=${jboss.domain.servers.dir}/server-two/log/gc.log"])
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@embedded /] /host=master/server-config=server-one/jvm=default:read-resource
> {
> "outcome" => "success",
> "result" => {
> "agent-lib" => undefined,
> "agent-path" => undefined,
> "debug-enabled" => undefined,
> "debug-options" => undefined,
> "env-classpath-ignored" => undefined,
> "environment-variables" => undefined,
> "heap-size" => undefined,
> "java-agent" => undefined,
> "java-home" => undefined,
> "jvm-options" => undefined,
> "launch-command" => undefined,
> "max-heap-size" => undefined,
> "max-permgen-size" => undefined,
> "permgen-size" => undefined,
> "stack-size" => undefined,
> "type" => undefined
> }
> }
> {code}
> As you can see from the above command does not update the {{jvm-options}}. However if you use the {{add-jvm-option}} operation that does work. It seems the {{write-attribute}} operation should also work.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ]
Elizabeth Clayton edited comment on DROOLS-4746 at 4/14/20 4:37 PM:
--------------------------------------------------------------------
[~tirelli] [~karreiro]
I updated the [click-thru|https://marvelapp.com/7208d3a] with the changes discussed:
- Added "Inspect" and "View properties" to "Clear" option in the menu the user gets when selecting the table/grid. I placed these in a left-click popover menu. The same option could be added to the right click contextual menu as well.
- I removed the Inspect menu option for the right click contextual menu at the header cell level, because the action is already covered by the table select action.
- I changed the "Test" button label to "Inspect" because I believe that I heard that was a more accurate description of the action.
- I looked for alternative fontawesome icons to replace the bug. I found these but I'm not sure if any of them are better?:
https://fontawesome.com/icons/microscope?style=solid
https://fontawesome.com/icons/binoculars?style=solid
https://fontawesome.com/icons/wpexplorer?style=brands
If not, I can see if someone from visual design could help.
Please let me know if I missed anything, if not I'll go ahead and mark this Resolved. Thanks!
was (Author: uxdlc):
[~tirelli] [~karreiro]
I updated the click-thru with the changes discussed:
- Added "Inspect" and "View properties" to "Clear" option in the menu the user gets when selecting the table/grid. I placed these in a left-click popover menu. The same option could be added to the right click contextual menu as well.
- I removed the Inspect menu option for the right click contextual menu at the header cell level, because the action is already covered by the table select action.
- I changed the "Test" button label to "Inspect" because I believe that I heard that was a more accurate description of the action.
- I looked for alternative fontawesome icons to replace the bug. I found these but I'm not sure if any of them are better?:
https://fontawesome.com/icons/microscope?style=solid
https://fontawesome.com/icons/binoculars?style=solid
https://fontawesome.com/icons/wpexplorer?style=brands
If not, I can see if someone from visual design could help.
Please let me know if this looks complete otherwise, and I'll close the jira, thanks!
> UX for DMN "quick test" tool
> ----------------------------
>
> Key: DROOLS-4746
> URL: https://issues.redhat.com/browse/DROOLS-4746
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Fine.png, Screen Shot 2020-04-08 at 4.34.49 PM.png, Screen Shot 2020-04-08 at 5.01.51 PM.png, Screen Shot 2020-04-09 at 9.29.34 AM.png, decision-logic-2-2.png, decision-logic-3-2.png
>
>
> As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test.
> When the user run the test he can get back the results of the DMN execution.
> Moreover, it would be handy to add those input/output to an existing (or new) test scenario.
> *Acceptance criteria*
> Users are able to:
> * Execute a single node boxed expression by providing node inputs (within the DMN editor.)
> * Explore the DMN model and provide inputs necessary to run a scenario test.
> * Obtain results (Expected) within the DMN editor once the test is run.
> Notes:
> * Try to dissociate this feature from the "test scenario" concept and think of this more as a partial execution. When we're thinking about the concept of a "test scenario", we think about input values and expected outputs... however, in this new component, users will be able to provide inputs and just check the current output.
> * Out of scope: Saving or exporting the "quick test."
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ]
Elizabeth Clayton commented on DROOLS-4746:
-------------------------------------------
[~tirelli] [~karreiro]
I updated the click-thru with the changes discussed:
- Added "Inspect" and "View properties" to "Clear" option in the menu the user gets when selecting the table/grid. I placed these in a left-click popover menu. The same option could be added to the right click contextual menu as well.
- I removed the Inspect menu option for the right click contextual menu at the header cell level, because the action is already covered by the table select action.
- I changed the "Test" button label to "Inspect" because I believe that I heard that was a more accurate description of the action.
- I looked for alternative fontawesome icons to replace the bug. I found these but I'm not sure if any of them are better?:
https://fontawesome.com/icons/microscope?style=solid
https://fontawesome.com/icons/binoculars?style=solid
https://fontawesome.com/icons/wpexplorer?style=brands
If not, I can see if someone from visual design could help.
Please let me know if this looks complete otherwise, and I'll close the jira, thanks!
> UX for DMN "quick test" tool
> ----------------------------
>
> Key: DROOLS-4746
> URL: https://issues.redhat.com/browse/DROOLS-4746
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Fine.png, Screen Shot 2020-04-08 at 4.34.49 PM.png, Screen Shot 2020-04-08 at 5.01.51 PM.png, Screen Shot 2020-04-09 at 9.29.34 AM.png, decision-logic-2-2.png, decision-logic-3-2.png
>
>
> As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test.
> When the user run the test he can get back the results of the DMN execution.
> Moreover, it would be handy to add those input/output to an existing (or new) test scenario.
> *Acceptance criteria*
> Users are able to:
> * Execute a single node boxed expression by providing node inputs (within the DMN editor.)
> * Explore the DMN model and provide inputs necessary to run a scenario test.
> * Obtain results (Expected) within the DMN editor once the test is run.
> Notes:
> * Try to dissociate this feature from the "test scenario" concept and think of this more as a partial execution. When we're thinking about the concept of a "test scenario", we think about input values and expected outputs... however, in this new component, users will be able to provide inputs and just check the current output.
> * Out of scope: Saving or exporting the "quick test."
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13256) Upgrade bouncycastle to 1.65.0
by Ashley Abdel-Sayed (Jira)
[ https://issues.redhat.com/browse/WFLY-13256?page=com.atlassian.jira.plugi... ]
Ashley Abdel-Sayed commented on WFLY-13256:
-------------------------------------------
Thanks [~jim.ma]! I double checked with {{mvn dependency:tree}} and it looks like PicketLink brings in xmlsec version 2.1.4 into WildFly so I guess its not the issue.
> Upgrade bouncycastle to 1.65.0
> ------------------------------
>
> Key: WFLY-13256
> URL: https://issues.redhat.com/browse/WFLY-13256
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Build System, Server
> Reporter: Bartosz Spyrko-Smietanko
> Assignee: Brian Stansberry
> Priority: Blocker
> Labels: downstream_dependency
> Fix For: 20.0.0.Beta1
>
> Attachments: handshake-error.log, handshake-success.log
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years