[JBoss JIRA] (WFLY-10837) IIOP subsystem requires port binding to be defined which was not necessary in prior WFLY versions
by Tomasz Adamski (Jira)
[ https://issues.jboss.org/browse/WFLY-10837?page=com.atlassian.jira.plugin... ]
Tomasz Adamski commented on WFLY-10837:
---------------------------------------
[~pkremens] In the new configuration of the IIOP subsystem socket bindings have to be defined explicitly. This is a model change and as a result model update was performed (please take a look at the commit abeb783bed0). If you are using the previous version of the subsystem then the socket binding should be automatically added by the transformer. If you use the newest model (2.1) you have to define socket binding explicitly.
[~ochaloup] This change was necessary because the migration was not working after the model refactor.
> IIOP subsystem requires port binding to be defined which was not necessary in prior WFLY versions
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-10837
> URL: https://issues.jboss.org/browse/WFLY-10837
> Project: WildFly
> Issue Type: Bug
> Components: IIOP
> Reporter: Ondra Chaloupka
> Assignee: Tomasz Adamski
> Priority: Blocker
> Fix For: 14.0.0.Final
>
>
> If the {{standalone-*.xml}} configuration defines to use IIOP subsystem but it does not defines the port binding element
> {code}
> <orb socket-binding="iiop"/>
> {code}
> The server starts with error
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.iiop-openjdk.orb-service: org.jboss.msc.service.StartException in service jboss.iiop-openjdk.orb-service: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have been configured
> at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:150)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> 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)
> Caused by: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have been configured
> at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:109)
> ... 8 more
> {code}
> The attribute of the {{socket-binding}} in the model is not defined as {{required}}.
> {code}
> "socket-binding" => {
> "type" => STRING,
> "description" => "The name of the socket binding configuration that specifies the ORB port.",
> "attribute-group" => "orb",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-constraints" => {"sensitive" => {"socket-binding-ref" => {"type" => "core"}}},
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }
> {code}
> Up to that declaring the iiop socket binding was not necessary in WildFly 13.0.0.Final. Could that be a backward compatibility problem too?
> Up to that
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3054) Highlight in expression builder previous selection in Scenario right panel
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3054?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3054:
-------------------------------------
[~gabriolo] [~srambach] [~danielezonca] In addition to the selection highlighting - the tree also has the following presentation errors:
- Nested nodes should not be outlined with a border line.
- Too much indented (to the right) for child nodes.
- Too much space below the parent node and the child node.
[~gabriolo] If you post a current screenshot, I will send back a high-fidelity mockup that betters aligns with the original wireframe.
> Highlight in expression builder previous selection in Scenario right panel
> --------------------------------------------------------------------------
>
> Key: DROOLS-3054
> URL: https://issues.jboss.org/browse/DROOLS-3054
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screen Shot 2018-09-28 at 3.45.25 PM.png
>
>
> When the user edits the type of a column, the expression builder into the right panel should highlight the existing mapped type.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3053) Warning dialog 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: Final-WarningA.png
> Warning dialog 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: Final-WarningA.png, Final-WarningB.png, Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.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 dialog 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:
-------------------------------------
[~stetson.robinson] [~gabriolo] [~srambach] Updated mockups per Stetson's copy edits above.
!Final-WarningA.png|thumbnail!
!Final-WarningB.png|thumbnail!
> Warning dialog 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: Final-WarningA.png, Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.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 dialog 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: Final-WarningB.png
> Warning dialog 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: Final-WarningA.png, Final-WarningB.png, Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.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 dialog 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: warning4.png)
> Warning dialog 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
>
>
> 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 dialog 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:
--------------------------------
Comment: was deleted
(was: Thank you again [~stetson.robinson] I've updated the mockup to match. [~gabriolo][~srambach]
!warning4.png|thumbnail! )
> Warning dialog 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
>
>
> 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 dialog 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 edited comment on DROOLS-3053 at 10/10/18 12:57 PM:
---------------------------------------------------------------------
[~uxdlc], [~danielezonca], [~gabriolo], I already proposed the text for the warnings, but am putting it all here to consolidate. The drafts below are also per the PatternFly warning message conventions.
Warning A: Preserve or delete scenario values
{quote}
Preserve or delete scenario values <window header>
Preserve or delete scenario values? <primary header>
This column contains scenario input values that might not correspond with the test statement after this change.
Select how you want to continue:
- Preserve existing scenario values in this column.
- Delete all scenario values in this column. (This action cannot be undone.)
[Cancel] [Preserve values] [Delete values]
{quote}
Warning B: Delete scenario values
{quote}
Delete scenario values <window header>
Delete scenario values? <primary header>
This column contains scenario input values that will not correspond with the test statement after this change and will therefore be deleted. Do you want to continue and delete all scenario values in this column?
Warning: This action cannot be undone.
[Cancel] [Delete values]
{quote}
was (Author: stetson.robinson):
[~uxdlc], [~danielezonca], [~gabriolo], I already proposed the text for the warnings, but am putting it all here to consolidate:
Warning A: Preserve or delete scenario values
{quote}
Preserve or delete scenario values <window header>
Preserve or delete scenario values? <primary header>
This column contains scenario input values that might not correspond with the test statement after this change.
Select how you want to continue:
- Preserve existing scenario values in this column.
- Delete all scenario values in this column. (This action cannot be undone.)
[Cancel] [Preserve values] [Delete values]
{quote}
Warning B: Delete scenario values
{quote}
Delete scenario values <window header>
Delete scenario values? <primary header>
This column contains scenario input values that will not correspond with the test statement after this change and will therefore be deleted. Do you want to continue and delete all scenario values in this column?
Warning: This action cannot be undone.
[Cancel] [Delete values]
{quote}
> Warning dialog 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, warning4.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 dialog 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 edited comment on DROOLS-3053 at 10/10/18 12:56 PM:
---------------------------------------------------------------------
[~uxdlc], [~danielezonca], [~gabriolo], I already proposed the text for the warnings, but am putting it all here to consolidate:
Warning A: Preserve or delete scenario values
{quote}
Preserve or delete scenario values <window header>
Preserve or delete scenario values? <primary header>
This column contains scenario input values that might not correspond with the test statement after this change.
Select how you want to continue:
- Preserve existing scenario values in this column.
- Delete all scenario values in this column. (This action cannot be undone.)
[Cancel] [Preserve values] [Delete values]
{quote}
Warning B: Delete scenario values
{quote}
Delete scenario values <window header>
Delete scenario values? <primary header>
This column contains scenario input values that will not correspond with the test statement after this change and will therefore be deleted. Do you want to continue and delete all scenario values in this column?
Warning: This action cannot be undone.
[Cancel] [Delete values]
{quote}
was (Author: stetson.robinson):
[~uxdlc], [~danielezonca], [~gabriolo], I already proposed the text for the warnings, but am putting it all here to consolidate:
Warning A: Preserve or Clear column values (update value of same type)
{quote}
Edit scenario test
This column contains scenario input values that might not correspond with the test statement after this change.
Select how you want to continue:
- Preserve existing scenario values in this column.
- Delete all scenario values in this column. (This action cannot be undone.)
[Cancel] [Preserve values] [Delete values]
{quote}
Warning B: Delete column data (update value of different type)
{quote}
Edit scenario test
This column contains scenario input values that will not correspond with the test statement after this change and will therefore be deleted. Do you want to continue and delete all scenario values in this column?
Warning: This action cannot be undone.
[Cancel] [Delete values]
{quote}
> Warning dialog 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, warning4.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 dialog 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:
-------------------------------------
Thank you again [~stetson.robinson] I've updated the mockup to match. [~gabriolo][~srambach]
!warning4.png|thumbnail!
> Warning dialog 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
>
>
> 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