[JBoss JIRA] (WFCORE-255) Boot time only system properties should not modify the runtime only the model
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-255:
--------------------------------------
I'll try to think of a better title. I could go either way with it being a feature. I know when I had a look it wasn't a simple task to allow these properties to be defined as system properties. The issue there is no way to override these properties for a server within domain, but it can be done for standalone servers. It's been like this from the start. Maybe it's intentional and we can just accept in which case I'm completely fine with closing this issue.
> Boot time only system properties should not modify the runtime only the model
> -----------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-255) jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-255:
---------------------------------
Summary: jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command. (was: Boot time only system properties should not modify the runtime only the model)
> jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-255) Boot time only system properties should not modify the runtime only the model
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-255:
-----------------------------------------
The title of this JIRA doesn't match very well with the description.
The description sounds like a Feature Request.
> Boot time only system properties should not modify the runtime only the model
> -----------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Elizabeth Clayton updated DROOLS-4994:
--------------------------------------
Attachment: collection-infotip.png
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Elizabeth Clayton commented on DROOLS-4994:
-------------------------------------------
[~adupliak] Here are mockups for two possible approaches to the first suggestion made, which could be a *short term* enhancements. Would need correct help text from [~stetson.robinson] or yourself.
!collection-inline.png|thumbnail!
!collection-infotip.png|thumbnail!
[~yamer] is working on some related issues in https://issues.redhat.com/browse/DROOLS-4972. I defer to [~yamer] and [~danielezonca] as to whether this will address the concern for the short term, or where you want me to look into a more comprehensive redesign of the widget. Thanks!
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Elizabeth Clayton updated DROOLS-4994:
--------------------------------------
Attachment: collection-inline.png
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ]
Anna Dupliak reassigned DROOLS-4972:
------------------------------------
Assignee: Yeser Amer (was: Anna Dupliak)
> Buttons stay disabled when switching to textual collection editor
> -----------------------------------------------------------------
>
> Key: DROOLS-4972
> URL: https://issues.redhat.com/browse/DROOLS-4972
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm
>
>
> If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-4972:
---------------------------------
Tester: Anna Dupliak (was: Jozef Marko)
> Buttons stay disabled when switching to textual collection editor
> -----------------------------------------------------------------
>
> Key: DROOLS-4972
> URL: https://issues.redhat.com/browse/DROOLS-4972
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Anna Dupliak
> Priority: Minor
> Labels: drools-tools
> Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm
>
>
> If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-12093) bug in tutorial "batch-processing" with column "End Time"
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFLY-12093?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFLY-12093:
--------------------------------------
[~emmartins] I'm not really sure. I don't really know anything about this quickstart. I would assume not, but I honestly don't know.
> bug in tutorial "batch-processing" with column "End Time"
> ---------------------------------------------------------
>
> Key: WFLY-12093
> URL: https://issues.redhat.com/browse/WFLY-12093
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Environment: batch-processing
> Reporter: Святослав Кремлёв
> Assignee: Eduardo Martins
> Priority: Major
> Attachments: 2019-05-18 23_16_51-Batch Processing.png
>
>
> in file
> org/jboss/as/quickstarts/batch/controller/JobData.java
> {code}
> public Date getEndTime() {
> endTime = new Date();
> return endTime.getTime() == 0 ? null : endTime;
> }
> {code}
> its returns current time every time, not the job endTime
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months