[JBoss JIRA] (DROOLS-3126) Scenario UX/Visual enhancements
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3126:
--------------------------------
Summary: Scenario UX/Visual enhancements (was: Improve editor look and feel)
> Scenario UX/Visual enhancements
> -------------------------------
>
> Key: DROOLS-3126
> URL: https://issues.jboss.org/browse/DROOLS-3126
> Project: Drools
> Issue Type: Epic
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3126) Improve editor look and feel
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3126:
-------------------------------------
Drools jira for table style enhancements
> Improve editor look and feel
> ----------------------------
>
> Key: DROOLS-3126
> URL: https://issues.jboss.org/browse/DROOLS-3126
> Project: Drools
> Issue Type: Epic
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3126) Improve editor look and feel
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3126:
-------------------------------------
[~danielezonca][~manstis]
The Table related enhancements you mention
* Use grey borders for all the grid and not only for the header
* Add some padding to the cells of the grid
* Reduce the width of Index columnReduce the width of Index column
... might already be covered by: https://issues.jboss.org/browse/DROOLS-2709 or could be.
> Improve editor look and feel
> ----------------------------
>
> Key: DROOLS-3126
> URL: https://issues.jboss.org/browse/DROOLS-3126
> Project: Drools
> Issue Type: Epic
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3126) Improve editor look and feel
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3126:
-------------------------------------
[~danielezonca] I changed this to an Epic because many of these jiras relate to jiras in other spaces, or otherwise need to be coordinated and roadmapped - unless we plan to do 1-off fixes for Scenario. I'll start populating this will UX info and related jiras.
> Improve editor look and feel
> ----------------------------
>
> Key: DROOLS-3126
> URL: https://issues.jboss.org/browse/DROOLS-3126
> Project: Drools
> Issue Type: Epic
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3126) Improve editor look and feel
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3126:
--------------------------------
Issue Type: Epic (was: Enhancement)
> Improve editor look and feel
> ----------------------------
>
> Key: DROOLS-3126
> URL: https://issues.jboss.org/browse/DROOLS-3126
> Project: Drools
> Issue Type: Epic
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3095) Grid with multiple data/domain object instances
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3095?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3095:
-------------------------------------
Issue Type: Task (was: Story)
> Grid with multiple data/domain object instances
> -----------------------------------------------
>
> Key: DROOLS-3095
> URL: https://issues.jboss.org/browse/DROOLS-3095
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> As user I want to use multiple instances of my DO in a test scenario.
> *Implementation specs:*
> Implement "Instance" concept on the GIVEN/EXPECTED columns.
> Given/Expected columns should have three headers:
> # the top one is the group (GIVEN/EXPECTED),
> # the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
> # the third one is the specific property of the instance.
> Below every instance header there could be one ore more property header - each of them belonging to that instance.
> The workflow to define template creation is going to change because of the new header level: now user must define the type/name of the instance *before* mapping the final properties.
> When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
> When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
> When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
> Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
> These issue is related to https://issues.jboss.org/browse/DROOLS-2788
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM
by Jan Blizňák (Jira)
[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ]
Jan Blizňák edited comment on WFLY-11178 at 10/15/18 2:15 PM:
--------------------------------------------------------------
[~dmlloyd], I debugged the execution just before "SchemaFactory.newInstance()" should be called and tried to find something different before and after breaking commit.
There is actually a difference in system properties (dumped to stdout and sorted before diff, both runs using latest IBM JDK 8):
{code:java}
@@ -59,9 +58 @@
- javax.xml.datatype.DatatypeFactory=__redirected.__DatatypeFactory
- javax.xml.parsers.DocumentBuilderFactory=__redirected.__DocumentBuilderFactory
- javax.xml.parsers.SAXParserFactory=__redirected.__SAXParserFactory
- javax.xml.stream.XMLEventFactory=__redirected.__XMLEventFactory
- javax.xml.stream.XMLInputFactory=__redirected.__XMLInputFactory
- javax.xml.stream.XMLOutputFactory=__redirected.__XMLOutputFactory
- javax.xml.transform.TransformerFactory=__redirected.__TransformerFactory
- javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema=__red...
- javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom=__redirec...
+ javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema=org.a...
@@ -111 +101,0 @@
- org.xml.sax.driver=__redirected.__XMLReaderFactory
{code}
This looks related to changes in MODULES-339.
was (Author: jbliznak):
[~dmlloyd], I debugged the execution just before "SchemaFactory.newInstance()" should be called and tried to find something different before and after breaking commit.
There is actually a difference in system properties (dumped to stdout and sorted before diff):
{code:java}
@@ -59,9 +58 @@
- javax.xml.datatype.DatatypeFactory=__redirected.__DatatypeFactory
- javax.xml.parsers.DocumentBuilderFactory=__redirected.__DocumentBuilderFactory
- javax.xml.parsers.SAXParserFactory=__redirected.__SAXParserFactory
- javax.xml.stream.XMLEventFactory=__redirected.__XMLEventFactory
- javax.xml.stream.XMLInputFactory=__redirected.__XMLInputFactory
- javax.xml.stream.XMLOutputFactory=__redirected.__XMLOutputFactory
- javax.xml.transform.TransformerFactory=__redirected.__TransformerFactory
- javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema=__red...
- javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom=__redirec...
+ javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema=org.a...
@@ -111 +101,0 @@
- org.xml.sax.driver=__redirected.__XMLReaderFactory
{code}
This looks related to changes in MODULES-339.
> WSTrustTestCase failing on IBM
> ------------------------------
>
> Key: WFLY-11178
> URL: https://issues.jboss.org/browse/WFLY-11178
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 14.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
> Priority: Major
> Attachments: log.txt
>
>
> As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
> at javax.xml.validation.SchemaFactory.newInstance(Unknown Source)
> at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94)
> at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75)
> at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120)
> ... 102 more
> {code}
> It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration
by Daniel José dos Santos (Jira)
[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos updated DROOLS-3067:
-------------------------------------------
Story Points: 1 (was: 13)
> [DMN Designer] Automatic Layout Feature Workbench Integration
> -------------------------------------------------------------
>
> Key: DROOLS-3067
> URL: https://issues.jboss.org/browse/DROOLS-3067
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, Screenshot from 2018-10-10 08-22-25.png, a3.dmn, auto.png, manual.png
>
>
> Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
> h2. Acceptance tests
> # -User is prompted if he wants or not to apply autolayout feature- discussed in comments
> # Positioning is automatically stored after model opening (/)
> # Simple graph, no branches, starting node -> node -> ...... node -> ending node (/)
> # Tree, top node in the middle of the screen, some branches to all sides (/)
> # Graph with big crossing of edges, similar to complete graph (/)
> # Large (but sparse) graph, not all nodes visible without scrolling (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM
by Jan Blizňák (Jira)
[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ]
Jan Blizňák commented on WFLY-11178:
------------------------------------
[~dmlloyd], I debugged the execution just before "SchemaFactory.newInstance()" should be called and tried to find something different before and after breaking commit.
There is actually a difference in system properties (dumped to stdout and sorted before diff):
{code:java}
@@ -59,9 +58 @@
- javax.xml.datatype.DatatypeFactory=__redirected.__DatatypeFactory
- javax.xml.parsers.DocumentBuilderFactory=__redirected.__DocumentBuilderFactory
- javax.xml.parsers.SAXParserFactory=__redirected.__SAXParserFactory
- javax.xml.stream.XMLEventFactory=__redirected.__XMLEventFactory
- javax.xml.stream.XMLInputFactory=__redirected.__XMLInputFactory
- javax.xml.stream.XMLOutputFactory=__redirected.__XMLOutputFactory
- javax.xml.transform.TransformerFactory=__redirected.__TransformerFactory
- javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema=__red...
- javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom=__redirec...
+ javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema=org.a...
@@ -111 +101,0 @@
- org.xml.sax.driver=__redirected.__XMLReaderFactory
{code}
This looks related to changes in MODULES-339.
> WSTrustTestCase failing on IBM
> ------------------------------
>
> Key: WFLY-11178
> URL: https://issues.jboss.org/browse/WFLY-11178
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 14.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
> Priority: Major
> Attachments: log.txt
>
>
> As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
> at javax.xml.validation.SchemaFactory.newInstance(Unknown Source)
> at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94)
> at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75)
> at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120)
> ... 102 more
> {code}
> It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months