[JBoss JIRA] (DROOLS-2747) [DMN Designer] Support table header cell selection
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2747?page=com.atlassian.jira.plugi... ]
Michael Anstis moved BAPL-992 to DROOLS-2747:
---------------------------------------------
Project: Drools (was: Business Automation Planning)
Key: DROOLS-2747 (was: BAPL-992)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Target Release: (was: RHDM 7.2.0.GA)
QE Status: NEW
> [DMN Designer] Support table header cell selection
> --------------------------------------------------
>
> Key: DROOLS-2747
> URL: https://issues.jboss.org/browse/DROOLS-2747
> Project: Drools
> Issue Type: Epic
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Attachments: Screenshot from 2018-03-20 08-59-39.png, Screenshot from 2018-03-20 09-20-04.png
>
>
> The decision table header cell does not support highlight / selection feature, see:
> !Screenshot from 2018-03-20 08-59-39.png|thumbnail!
> In contrast context entry name cell support this:
> !Screenshot from 2018-03-20 09-20-04.png|thumbnail!
> The outline should be consistent, i.e. blue rectangle should be rendered regardless of the selected cell type (data vs. header).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFWIP-55) Default value defined on injection point of List and Set fields is not taken into account
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFWIP-55?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil commented on WFWIP-55:
----------------------------------
I have opened https://github.com/eclipse/microprofile-config/issues/376 to clarify the behaviour of injected collection and array without configured and default values.
Note that regardless of the behaviour, it must be consistent between array and collections (which is not the case currently).
> Default value defined on injection point of List and Set fields is not taken into account
> -----------------------------------------------------------------------------------------
>
> Key: WFWIP-55
> URL: https://issues.jboss.org/browse/WFWIP-55
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Config
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
>
> Assume we define a following injection points:
> {code:java}
> @Inject
> @ConfigProperty(name = "myPets", defaultValue = "horse,monkey")
> private String[] myArrayPets;
> @Inject
> @ConfigProperty(name = "myPets", defaultValue = "cat,lama")
> private List<String> myListPets;
> @Inject
> @ConfigProperty(name = "myPets", defaultValue = "dog,mouse")
> private Set<String> mySetPets;
> {code}
> Passing a -DmyPets=snake,ox property work as expected:
> {noformat}
> myArrayPets : [snake,ox]
> myListPets : [snake,ox]
> mySetPets : [snake,ox]
> {noformat}
> but trying to use the defults I get:
> {noformat}
> myArrayPets : [horse,monkey]
> myListPets : <empty list>
> mySetPets : <empty set>
> {noformat}
> defaults are not applied to List and Set fields, no exception is thrown.
> Another inconsistency between Array and Set+List I run into is behaviour on missing property (myPets is not set):
> *Array*
> {code:java}
> @Inject
> @ConfigProperty(name = "myPets")
> private String[] myArrayPets;
> >>>
> 08:34:05,178 ERROR [stderr] (MSC service thread 1-2) org.jboss.weld.exceptions.DeploymentException: Error while validating Configuration
> 08:34:05,178 ERROR [stderr] (MSC service thread 1-2) No Config Value exists for myPets
> myArrayPets : [org.eclipse.microprofile.config.configproperty.unconfigureddvalue]
> {code}
> *Set, List*
> {code:java}
> @Inject
> @ConfigProperty(name = "myPets")
> private List<String> myListPets;
> @Inject
> @ConfigProperty(name = "myPets")
> private Set<String> mySetPets;
> >>>
> no errors
> myListPets : <empty list>
> mySetPets : <empty set>
> {code}
> https://microprofile.io/project/eclipse/microprofile-config/spec/src/main...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2738) Create a simple, structured or compound data type
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2738?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2738:
----------------------------------------
I added a rather rubbish wire-frame illustrating how a {{treegrid}} could theoretically work.
> Create a simple, structured or compound data type
> -------------------------------------------------
>
> Key: DROOLS-2738
> URL: https://issues.jboss.org/browse/DROOLS-2738
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Attachments: DROOLS-2738.bmpr, DT-nest-People.pdf
>
>
> We're trying to solve two big issues with this dialog:
> I) the definition of a simple (basic) data type; and
> II) the definition of a structured data type.
> * The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type.
> * The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types) Additionally, a structured data type can have other complex nested data types.
> * Requirement to address situations where we're going to have many levels of nesting and many fields. The user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFWIP-55) Default value defined on injection point of List and Set fields is not taken into account
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFWIP-55?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil commented on WFWIP-55:
----------------------------------
Default value for injected collection is fixed in https://github.com/smallrye/smallrye-config/pull/10
I'll check with MicroProfile Config to clarify the behaviour of array and collections in the absence of configured and default value.
> Default value defined on injection point of List and Set fields is not taken into account
> -----------------------------------------------------------------------------------------
>
> Key: WFWIP-55
> URL: https://issues.jboss.org/browse/WFWIP-55
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Config
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
>
> Assume we define a following injection points:
> {code:java}
> @Inject
> @ConfigProperty(name = "myPets", defaultValue = "horse,monkey")
> private String[] myArrayPets;
> @Inject
> @ConfigProperty(name = "myPets", defaultValue = "cat,lama")
> private List<String> myListPets;
> @Inject
> @ConfigProperty(name = "myPets", defaultValue = "dog,mouse")
> private Set<String> mySetPets;
> {code}
> Passing a -DmyPets=snake,ox property work as expected:
> {noformat}
> myArrayPets : [snake,ox]
> myListPets : [snake,ox]
> mySetPets : [snake,ox]
> {noformat}
> but trying to use the defults I get:
> {noformat}
> myArrayPets : [horse,monkey]
> myListPets : <empty list>
> mySetPets : <empty set>
> {noformat}
> defaults are not applied to List and Set fields, no exception is thrown.
> Another inconsistency between Array and Set+List I run into is behaviour on missing property (myPets is not set):
> *Array*
> {code:java}
> @Inject
> @ConfigProperty(name = "myPets")
> private String[] myArrayPets;
> >>>
> 08:34:05,178 ERROR [stderr] (MSC service thread 1-2) org.jboss.weld.exceptions.DeploymentException: Error while validating Configuration
> 08:34:05,178 ERROR [stderr] (MSC service thread 1-2) No Config Value exists for myPets
> myArrayPets : [org.eclipse.microprofile.config.configproperty.unconfigureddvalue]
> {code}
> *Set, List*
> {code:java}
> @Inject
> @ConfigProperty(name = "myPets")
> private List<String> myListPets;
> @Inject
> @ConfigProperty(name = "myPets")
> private Set<String> mySetPets;
> >>>
> no errors
> myListPets : <empty list>
> mySetPets : <empty set>
> {code}
> https://microprofile.io/project/eclipse/microprofile-config/spec/src/main...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2738) Create a simple, structured or compound data type
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2738?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2738:
-----------------------------------
Attachment: (was: DROOLS-2738.bmpr)
> Create a simple, structured or compound data type
> -------------------------------------------------
>
> Key: DROOLS-2738
> URL: https://issues.jboss.org/browse/DROOLS-2738
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Attachments: DT-nest-People.pdf
>
>
> We're trying to solve two big issues with this dialog:
> I) the definition of a simple (basic) data type; and
> II) the definition of a structured data type.
> * The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type.
> * The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types) Additionally, a structured data type can have other complex nested data types.
> * Requirement to address situations where we're going to have many levels of nesting and many fields. The user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2734) [Guided Decision Table] - Zooming
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2734?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2734:
----------------------------------------
[~roger600] Yes, the implementation for Stunner based editors (BPMN, DM and DMN) and GDT will be different; but from a User's perspective operation (of zoom) across the visually similar editors needs to be consistent. So, I need to make some changes to GDT (and DMN-grid editor) and you (or colleague) need to make changes to Stunner to align the operation.
> [Guided Decision Table] - Zooming
> ---------------------------------
>
> Key: DROOLS-2734
> URL: https://issues.jboss.org/browse/DROOLS-2734
> Project: Drools
> Issue Type: Story
> Components: Guided Decision Table Editor
> Reporter: Matthew Stevens
> Assignee: Michael Anstis
> Labels: UX, UXTeam
>
> In order to improve zoom capabilities, a first priority is to better align current capabilities across the workbench, specifically GDT and Stunner.
> *For GDT*
> # Add support for Control click with mouse wheel or trackpad to zoom like Stunner.
> # Add keyboard support for Control click with +/- to allow users to cycle through the different zoom levels.
> A long term solution might move these controls to the canvas, add more zoom levels, and add a slider. But aligning things is a good start.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFWIP-56) IndexOutOfBoundsException in JDBC HA scenario
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-56?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak updated WFWIP-56:
--------------------------------
Component/s: Artemis
(was: JMS)
> IndexOutOfBoundsException in JDBC HA scenario
> ---------------------------------------------
>
> Key: WFWIP-56
> URL: https://issues.jboss.org/browse/WFWIP-56
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> PR: https://github.com/wildfly/wildfly/pull/11355
> *Scenario:*
> * There are two Wildfly servers each containing two Artemis brokers
> * Artemis brokers creates two live-backup pairs. Each Wildfly instance contains one live and one backup
> * Second server has MDB which resends messages from InQueue to OutQueue
> * The second server is stopped and restarted
> After the second server is restarted, everything works correctly for a while. Failback performs successfully, MDB resends messages. However after some time the server starts to print many errors \[1\]. It looks like some messages where corrupted during failover/failback and cannot be delivered.
> The reproducer always hits the issue. The issue is not relevant to particular database, I hit it with Oracle12c and DB2 11.1. I also tried to reduce amount of messages and their size, but I still hit the issue. So it is not related to paging or large messages.
> \[1\]
> {code}
> 15:20:50,010 ERROR [org.apache.activemq.artemis.ra] (Thread-7 (ActiveMQ-client-global-threads)) AMQ154004: Failed to deliver message: java.lang.IndexOutOfBoundsException
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readSimpleStringInternal(ChannelBufferWrapper.java:93) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:73) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.reader.TextMessageUtil.readBodyText(TextMessageUtil.java:37) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.jms.client.ActiveMQTextMessage.doBeforeReceive(ActiveMQTextMessage.java:112) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:295) [artemis-ra-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFWIP-56) IndexOutOfBoundsException in JDBC HA scenario
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-56?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak reassigned WFWIP-56:
-----------------------------------
Assignee: Martyn Taylor (was: Jeff Mesnil)
> IndexOutOfBoundsException in JDBC HA scenario
> ---------------------------------------------
>
> Key: WFWIP-56
> URL: https://issues.jboss.org/browse/WFWIP-56
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Erich Duda
> Assignee: Martyn Taylor
> Priority: Blocker
>
> PR: https://github.com/wildfly/wildfly/pull/11355
> *Scenario:*
> * There are two Wildfly servers each containing two Artemis brokers
> * Artemis brokers creates two live-backup pairs. Each Wildfly instance contains one live and one backup
> * Second server has MDB which resends messages from InQueue to OutQueue
> * The second server is stopped and restarted
> After the second server is restarted, everything works correctly for a while. Failback performs successfully, MDB resends messages. However after some time the server starts to print many errors \[1\]. It looks like some messages where corrupted during failover/failback and cannot be delivered.
> The reproducer always hits the issue. The issue is not relevant to particular database, I hit it with Oracle12c and DB2 11.1. I also tried to reduce amount of messages and their size, but I still hit the issue. So it is not related to paging or large messages.
> \[1\]
> {code}
> 15:20:50,010 ERROR [org.apache.activemq.artemis.ra] (Thread-7 (ActiveMQ-client-global-threads)) AMQ154004: Failed to deliver message: java.lang.IndexOutOfBoundsException
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readSimpleStringInternal(ChannelBufferWrapper.java:93) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:73) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.reader.TextMessageUtil.readBodyText(TextMessageUtil.java:37) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.jms.client.ActiveMQTextMessage.doBeforeReceive(ActiveMQTextMessage.java:112) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:295) [artemis-ra-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years