[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Liz Clayton edited comment on DROOLS-3053 at 10/4/18 3:24 PM:
--------------------------------------------------------------
Thanks [~stetson.robinson], much better thanks so much! I made one additional tweak, let me know. :)
was (Author: uxdlc):
Thanks [~stetson.robinson], much better thanks so much! I made one additional tweak, let me know. :)
!warning2.png|thumbnail!
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning2.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3053:
--------------------------------
Attachment: (was: warning.png)
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning2.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-4153) Capability 'org.wildfly.nosql.mongo.driver-service' is unknown error thrown on WildFly 14 + current master branch
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFCORE-4153?page=com.atlassian.jira.plugi... ]
Scott Marlow commented on WFCORE-4153:
--------------------------------------
Thanks Brian, I definitely will try your suggestion, really appreciate the help! :)
> Capability 'org.wildfly.nosql.mongo.driver-service' is unknown error thrown on WildFly 14 + current master branch
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4153
> URL: https://issues.jboss.org/browse/WFCORE-4153
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 6.0.1.Final
> Reporter: Scott Marlow
> Assignee: Jeff Mesnil
> Priority: Major
>
> As reported on [https://issues.jboss.org/browse/WFNOSQL-28], the wildfly-nosql subsystems are failing on WF14. I will try to work around the failure, following Brian's advice but would still like to see this resolved for other (externally created) subsystems that might hit it.
> Example of failure:
> {quote}
> 2018-10-04 11:09:17,904 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool – 10) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "mongodb"),("mongo" => "default"),("host" => "default")
> ]): java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.nosql.mongo.driver-service' is unknown.
> at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.getDependentName(CapabilityReferenceRecorder.java:139)
> at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.processCapabilityRequirement(CapabilityReferenceRecorder.java:196)
> at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.addCapabilityRequirements(CapabilityReferenceRecorder.java:182)
> at org.jboss.as.controller.AttributeDefinition.addCapabilityRequirements(AttributeDefinition.java:1066)
> at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:291)
> at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:154)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3053:
-------------------------------------
Thanks [~stetson.robinson], much better thanks so much! I made one additional tweak, let me know. :)
!warning2.png|thumbnail!
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3053:
--------------------------------
Attachment: warning2.png
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning.png, warning2.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-4153) Capability 'org.wildfly.nosql.mongo.driver-service' is unknown error thrown on WildFly 14 + current master branch
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4153?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-4153:
------------------------------------------
The key details:
The failure:
{code}
15:57:11,908 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool – 37) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "mongodb"),
("mongo" => "default"),
("host" => "default")
]): java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.nosql.mongo.driver-service' is unknown.
at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.getDependentName(CapabilityReferenceRecorder.java:139)
at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.processCapabilityRequirement(CapabilityReferenceRecorder.java:196)
at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.addCapabilityRequirements(CapabilityReferenceRecorder.java:182)
at org.jboss.as.controller.AttributeDefinition.addCapabilityRequirements(AttributeDefinition.java:1066)
at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:291)
at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:154)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
{code}
The attribute registering the requirement:
https://github.com/scottmarlow/wildfly-nosql/blob/WF14/mongodb/subsystem/...
The 'add' handler for the subsystem root resource declaring the depended-upon capability:
https://github.com/scottmarlow/wildfly-nosql/blob/WF14/mongodb/subsystem/...
That last bit is no longer best practice for how to register a cap, but unless I've forgotten something I think it should still work. AIUI, it worked in WF 13.
[~smarlow] Once you try it please comment here as to whether my suggested code improvement fixes the problem.
> Capability 'org.wildfly.nosql.mongo.driver-service' is unknown error thrown on WildFly 14 + current master branch
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4153
> URL: https://issues.jboss.org/browse/WFCORE-4153
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 6.0.1.Final
> Reporter: Scott Marlow
> Assignee: Jeff Mesnil
> Priority: Major
>
> As reported on [https://issues.jboss.org/browse/WFNOSQL-28], the wildfly-nosql subsystems are failing on WF14. I will try to work around the failure, following Brian's advice but would still like to see this resolved for other (externally created) subsystems that might hit it.
> Example of failure:
> {quote}
> 2018-10-04 11:09:17,904 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool – 10) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "mongodb"),("mongo" => "default"),("host" => "default")
> ]): java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.nosql.mongo.driver-service' is unknown.
> at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.getDependentName(CapabilityReferenceRecorder.java:139)
> at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.processCapabilityRequirement(CapabilityReferenceRecorder.java:196)
> at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.addCapabilityRequirements(CapabilityReferenceRecorder.java:182)
> at org.jboss.as.controller.AttributeDefinition.addCapabilityRequirements(AttributeDefinition.java:1066)
> at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:291)
> at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:154)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-4153) Capability 'org.wildfly.nosql.mongo.driver-service' is unknown error thrown on WildFly 14 + current master branch
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFCORE-4153?page=com.atlassian.jira.plugi... ]
Scott Marlow updated WFCORE-4153:
---------------------------------
Description:
As reported on [https://issues.jboss.org/browse/WFNOSQL-28], the wildfly-nosql subsystems are failing on WF14. I will try to work around the failure, following Brian's advice but would still like to see this resolved for other (externally created) subsystems that might hit it.
Example of failure:
{quote}
2018-10-04 11:09:17,904 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool – 10) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "mongodb"),("mongo" => "default"),("host" => "default")
]): java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.nosql.mongo.driver-service' is unknown.
at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.getDependentName(CapabilityReferenceRecorder.java:139)
at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.processCapabilityRequirement(CapabilityReferenceRecorder.java:196)
at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.addCapabilityRequirements(CapabilityReferenceRecorder.java:182)
at org.jboss.as.controller.AttributeDefinition.addCapabilityRequirements(AttributeDefinition.java:1066)
at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:291)
at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:154)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
{quote}
was:As reported on [https://issues.jboss.org/browse/WFNOSQL-28], the wildfly-nosql subsystems are failing on WF14. I will try to work around the failure, following Brian's advice but would still like to see this resolved for other (externally created) subsystems that might hit it.
> Capability 'org.wildfly.nosql.mongo.driver-service' is unknown error thrown on WildFly 14 + current master branch
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4153
> URL: https://issues.jboss.org/browse/WFCORE-4153
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 6.0.1.Final
> Reporter: Scott Marlow
> Assignee: Jeff Mesnil
> Priority: Major
>
> As reported on [https://issues.jboss.org/browse/WFNOSQL-28], the wildfly-nosql subsystems are failing on WF14. I will try to work around the failure, following Brian's advice but would still like to see this resolved for other (externally created) subsystems that might hit it.
> Example of failure:
> {quote}
> 2018-10-04 11:09:17,904 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool – 10) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "mongodb"),("mongo" => "default"),("host" => "default")
> ]): java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.nosql.mongo.driver-service' is unknown.
> at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.getDependentName(CapabilityReferenceRecorder.java:139)
> at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.processCapabilityRequirement(CapabilityReferenceRecorder.java:196)
> at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.addCapabilityRequirements(CapabilityReferenceRecorder.java:182)
> at org.jboss.as.controller.AttributeDefinition.addCapabilityRequirements(AttributeDefinition.java:1066)
> at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:291)
> at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:154)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-3053:
------------------------------------------
[~uxdlc], I like it! Verbose can be good if it clarifies. What do you think about this instead:
This column contains Scenario input values that might not correspond with the new values after this change. Select how you want to continue.
- Preserve existing Scenario values in this column.
- Clear all Scenario values in this column.
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months