[JBoss JIRA] (WFLY-11778) Missing ejb3 transformer tests
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-11778?page=com.atlassian.jira.plugin... ]
Cheng Fang edited comment on WFLY-11778 at 3/11/19 6:05 PM:
------------------------------------------------------------
In [WildFly 15|https://wildscribe.github.io/WildFly/15.0/subsystem/ejb3/passivation-store/index.html], {{passivation-store/bean-cache}} and {{passivation-store/cache-container}} both have access-type {{read-only}}.
In [WildFly 16|https://wildscribe.github.io/WildFly/16.0/subsystem/ejb3/passivation-store/index.html], their access-type changed to {{read-write}}.
It was changed on Dec 20, 2018 with this commit:
https://github.com/wildfly/wildfly/commit/f8ceb2daac6ee16b27991a402dcda63...
was (Author: cfang):
In [WildFly 15|https://wildscribe.github.io/WildFly/15.0/subsystem/ejb3/passivation-store/index.html], {{passivation-store/bean-cache}} and {{passivation-store/cache-container}} both have access-type {{read-only}}.
In [WildFly 16|https://wildscribe.github.io/WildFly/16.0/subsystem/ejb3/passivation-store/index.html], their access-type changed to {{read-write}}.
> Missing ejb3 transformer tests
> ------------------------------
>
> Key: WFLY-11778
> URL: https://issues.jboss.org/browse/WFLY-11778
> Project: WildFly
> Issue Type: Task
> Components: EJB
> Affects Versions: 16.0.0.Beta1
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
>
> Per Kabir's email to wildfly-dev list, need to add transformer tests for ejb3 subsystem. For details see http://lists.jboss.org/pipermail/wildfly-dev/2019-February/006772.html
> {quote}
> TL;DR: It looks like we may be missing transformer tests in the following
> subsystems: ejb3, infinispan, jca, logging, undertow. I've not dug in
> beyond that.
> Full:
> We have been using ModelTestControllerVersion.EAP_7_2_0_TEMP (containing
> WF14) for transformer testing until EAP 7.2.0 was released. [1] renames
> this to be EAP_7_2_0 and points to EAP 7.2.0.
> In addition I have some WIP to update the full mixed domain and subsystem
> tests to do the same. When doing this I noticed that the only subsystem
> that had transformer tests referencing EAP_7_2_0_TEMP was modcluster. I
> knew messaging-activemq had some changes, which Emmanuel is looking at.
> I've run the model comparison tool against master/7.2.0: and see changes
> which might be significant:
> ====== Resource root address: ["subsystem" => "ejb3"] - Current version:
> 0.0.0; legacy version: 5.0.0 =======
> --- Problems for relative address to root ["passivation-store" => "*"]:
> Different 'access-type' for attribute 'bean-cache'. Current: "read-write";
> legacy: "read-only"
> Different 'access-type' for attribute 'cache-container'. Current:
> "read-write"; legacy: "read-only"
> ...
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-11778) Missing ejb3 transformer tests
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-11778?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-11778:
-----------------------------------
In [WildFly 15|https://wildscribe.github.io/WildFly/15.0/subsystem/ejb3/passivation-store/index.html], {{passivation-store/bean-cache}} and {{passivation-store/cache-container}} both have access-type {{read-only}}.
In [WildFly 16|https://wildscribe.github.io/WildFly/16.0/subsystem/ejb3/passivation-store/index.html], their access-type changed to {{read-write}}.
> Missing ejb3 transformer tests
> ------------------------------
>
> Key: WFLY-11778
> URL: https://issues.jboss.org/browse/WFLY-11778
> Project: WildFly
> Issue Type: Task
> Components: EJB
> Affects Versions: 16.0.0.Beta1
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
>
> Per Kabir's email to wildfly-dev list, need to add transformer tests for ejb3 subsystem. For details see http://lists.jboss.org/pipermail/wildfly-dev/2019-February/006772.html
> {quote}
> TL;DR: It looks like we may be missing transformer tests in the following
> subsystems: ejb3, infinispan, jca, logging, undertow. I've not dug in
> beyond that.
> Full:
> We have been using ModelTestControllerVersion.EAP_7_2_0_TEMP (containing
> WF14) for transformer testing until EAP 7.2.0 was released. [1] renames
> this to be EAP_7_2_0 and points to EAP 7.2.0.
> In addition I have some WIP to update the full mixed domain and subsystem
> tests to do the same. When doing this I noticed that the only subsystem
> that had transformer tests referencing EAP_7_2_0_TEMP was modcluster. I
> knew messaging-activemq had some changes, which Emmanuel is looking at.
> I've run the model comparison tool against master/7.2.0: and see changes
> which might be significant:
> ====== Resource root address: ["subsystem" => "ejb3"] - Current version:
> 0.0.0; legacy version: 5.0.0 =======
> --- Problems for relative address to root ["passivation-store" => "*"]:
> Different 'access-type' for attribute 'bean-cache'. Current: "read-write";
> legacy: "read-only"
> Different 'access-type' for attribute 'cache-container'. Current:
> "read-write"; legacy: "read-only"
> ...
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3330) DMN Properties panel - UX enhancements
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3330:
--------------------------------
Tester: Jozef Marko
Affects: Documentation (Ref Guide, User Guide, etc.)
> DMN Properties panel - UX enhancements
> ---------------------------------------
>
> Key: DROOLS-3330
> URL: https://issues.jboss.org/browse/DROOLS-3330
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: ChlamydiaScreening_CQM.jpg, styles.png
>
>
> # Increase the size of the Description input to a text field.
> # Combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
> Notes re: Styles section:
> * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
> * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
> * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3330) DMN Properties panel - UX enhancements
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3330:
--------------------------------
Story Points: 3
> DMN Properties panel - UX enhancements
> ---------------------------------------
>
> Key: DROOLS-3330
> URL: https://issues.jboss.org/browse/DROOLS-3330
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: ChlamydiaScreening_CQM.jpg, styles.png
>
>
> # Increase the size of the Description input to a text field.
> # Combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
> Notes re: Styles section:
> * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
> * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
> * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3330) DMN Properties panel - UX enhancements
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3330:
--------------------------------
Description:
# Increase the size of the Description input to a text field.
# Combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
Notes re: Styles section:
* As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
* The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
* If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
was:
Request to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
Rationale:
* As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
* The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
* If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
> DMN Properties panel - UX enhancements
> ---------------------------------------
>
> Key: DROOLS-3330
> URL: https://issues.jboss.org/browse/DROOLS-3330
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Minor
> Labels: UX, UXTeam, drools-tools
> Attachments: ChlamydiaScreening_CQM.jpg, styles.png
>
>
> # Increase the size of the Description input to a text field.
> # Combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
> Notes re: Styles section:
> * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
> * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
> * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months