[JBoss JIRA] (DROOLS-3706) [DMN Designer] Boxed Expressions - Enhance component title
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3706?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3706:
-----------------------------------
Sprint: (was: 2019 Week 08-10)
> [DMN Designer] Boxed Expressions - Enhance component title
> ----------------------------------------------------------
>
> Key: DROOLS-3706
> URL: https://issues.jboss.org/browse/DROOLS-3706
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screen Shot 2019-02-25 at 2.33.44 PM.png
>
>
> Improve the boxed expression title.
> - Rename "<< Back to <NODE_NAME>" (*"<< Back to Decision-1"*) to just *"<< Back"*
> - Rename "<BOXED_EXPRESSION_TYPE>" (*"Decision Table"*) to "<NODE_NAME> (<BOXED_EXPRESSION_TYPE>)" (*"Decision-1 (Decision Table)"*)
> ⚠️ Notice: Check the latest Liz mockup for this task.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3657) [DMN Designer] Highlight invalid DRGElements
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3657?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3657:
-----------------------------------
Sprint: (was: 2019 Week 08-10)
> [DMN Designer] Highlight invalid DRGElements
> --------------------------------------------
>
> Key: DROOLS-3657
> URL: https://issues.jboss.org/browse/DROOLS-3657
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> Whenever a DMN file is validated (be it when the Project is compiled or via the Validate button on the toolbar) the DMN editor should highlight issues reported by the validation. This should include DRG nodes (on the graph view) or DRGElements (in the Boxed Expression, aka grid, view). The nature of the highlighting is to be defined; but probably consists of an orange background for warnings and red background for errors; possibly both with a warning triangle positioned somewhere. UX will need engaging for design proposals.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-11750) Allow cluster to use DNS addresses instead of IP addresses
by Tomasz Adamski (Jira)
[ https://issues.jboss.org/browse/WFLY-11750?page=com.atlassian.jira.plugin... ]
Tomasz Adamski commented on WFLY-11750:
---------------------------------------
{quote}
Agreed. The server supplies this information via client mappings, the destination address for which is stored and supplied as a string. Thus the server should already be capable of seding the client with a hostname instead of an IP address. However, I suspect that the address used by the transaction client is taken from the remote connection itself - which likely use the resolved destination address (as the established connection will have already resolved the host name), rather than preferring the host name over the address, if it exists.
{quote}
I was debugging into that and connections are based on the data obtained from cluster topology call. I have also checked standalone scenario and it works fine == narayana object store records consist of DNS address if WildFly is configured using those.
Maybe the right thing to deal with it is to do a translation is server's cluster topology call. I'm going to debug into that and see the possibilities. Generally, I was skeptical about the translating solution because I was afraid of bugs that may arise from it (f.e. race conditions during cluster reorganization). That's why I suggested for the cluster to be based on DNS (which have similar guarantees in OpenShift as IPs in bare-metal) addresses directly. But maybe, if this happens in the server topology call than those problems won't occur.
> Allow cluster to use DNS addresses instead of IP addresses
> ----------------------------------------------------------
>
> Key: WFLY-11750
> URL: https://issues.jboss.org/browse/WFLY-11750
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 16.0.0.Beta1
> Reporter: Tomasz Adamski
> Assignee: Paul Ferraro
> Priority: Major
>
> We would need a configuration that would allow for the cluster to use DNS addresses instead of IP addresses. The reason is that OpenShift guarantees the node identity under DNS address and not under IP address.
> Sample scenario that may currently fail when application are deployed in OpenShift:
> A (application)
> B (clustered application)
> 1. A calls transactional invocation on B
> 2. as a result of discovery process A obtains a cluster topology from B and uses one of obtained IP addresses for the connection
> 3. as the invocation is transactional the object-store records are written in A's persistent object store; those records are based on the data obtained from the cluster => subordinate node is identified by the IP address from point two
> 4. B node fails
> 5. OpenShift restarts node B on another IP address
> 6. A attempts recovery and persistently fails
> OTOH OpenShift guarantees node identity under DNS address. As a result, at point 5 node is guaranteed to restart on established DNS address so if the cluster used this address instead of physical addresses the scenario above will finish with A being able to recover the transaction.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-11739) Transaction JDBC object store does not start on PostgreSQL Plus 10.1
by Tom Jenkinson (Jira)
[ https://issues.jboss.org/browse/WFLY-11739?page=com.atlassian.jira.plugin... ]
Tom Jenkinson updated WFLY-11739:
---------------------------------
Issue Type: Enhancement (was: Bug)
> Transaction JDBC object store does not start on PostgreSQL Plus 10.1
> --------------------------------------------------------------------
>
> Key: WFLY-11739
> URL: https://issues.jboss.org/browse/WFLY-11739
> Project: WildFly
> Issue Type: Enhancement
> Components: Transactions
> Affects Versions: 14.0.0.Final, 15.0.1.Final, 16.0.0.Beta1
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Major
> Fix For: 16.0.0.CR1
>
>
> The JBossTM has not got driver class for PostgreSQL Plus 10.1. This results in a _ClassNotFoundException_ exception when transaction subsystem is configured to use a JDBC transaction object store on PostgreSQL Plus 10.1.
> The problem is that there is no driver class in [this package|https://github.com/jbosstm/narayana/tree/5.9.1.Final/ArjunaCore/a...] for [edb-jdbc18.jar|http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.3.0/po...] which is supposed to be used for PostgreSQL Plus 10.1. Narayana expects _edb_driver_ class. This has changed since edb-jdbc17.jar where _postgresql_driver_ is expected.
> PostgreSQL Plus 10.1 is supported in 7.2.0 and 7.3.0, Customers can not used the DB as JDBC object store due to this issue.
> {code:java}
> 16:33:17,027 FATAL [com.arjuna.ats.arjuna] (MSC service thread 1-2) ARJUNA012260: Received exception for com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess:JASDTJBossTSTxTable: java.lang.ClassNotFoundException: com.arjuna.ats.internal.arjuna.objectstore.jdbc.drivers.edb_driver from [Module "org.jboss.jts" from local module loader @2b80d80f (finder: local module finder @3ab39c39 (roots: /home/istraka/repositories/gitlab/tests-management/jboss-eap-7.1/modules,/home/istraka/repositories/gitlab/tests-management/jboss-eap-7.1/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.<init>(JDBCStore.java:251)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:129)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:152)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.<init>(CommitMarkableResourceRecordRecoveryModule.java:156)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192)
> at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.<init>(PeriodicRecovery.java:121)
> at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:107)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.<init>(RecoveryManager.java:477)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112)
> at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54)
> at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3706) [DMN Designer] Boxed Expressions - Enhance component title
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3706?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3706:
-----------------------------------
Tester: Jozef Marko
Writer: Stetson Robinson
> [DMN Designer] Boxed Expressions - Enhance component title
> ----------------------------------------------------------
>
> Key: DROOLS-3706
> URL: https://issues.jboss.org/browse/DROOLS-3706
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screen Shot 2019-02-25 at 2.33.44 PM.png
>
>
> Improve the boxed expression title.
> - Rename "<< Back to <NODE_NAME>" (*"<< Back to Decision-1"*) to just *"<< Back"*
> - Rename "<BOXED_EXPRESSION_TYPE>" (*"Decision Table"*) to "<NODE_NAME> (<BOXED_EXPRESSION_TYPE>)" (*"Decision-1 (Decision Table)"*)
> ⚠️ Notice: Check the latest Liz mockup for this task.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3706) [DMN Designer] Boxed Expressions - Enhance component title
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3706?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3706:
-----------------------------------
Story Points: 3
Sprint: 2019 Week 08-10
> [DMN Designer] Boxed Expressions - Enhance component title
> ----------------------------------------------------------
>
> Key: DROOLS-3706
> URL: https://issues.jboss.org/browse/DROOLS-3706
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screen Shot 2019-02-25 at 2.33.44 PM.png
>
>
> Improve the boxed expression title.
> - Rename "<< Back to <NODE_NAME>" (*"<< Back to Decision-1"*) to just *"<< Back"*
> - Rename "<BOXED_EXPRESSION_TYPE>" (*"Decision Table"*) to "<NODE_NAME> (<BOXED_EXPRESSION_TYPE>)" (*"Decision-1 (Decision Table)"*)
> ⚠️ Notice: Check the latest Liz mockup for this task.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3706) [DMN Designer] Boxed Expressions - Enhance component title
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3706?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-3706:
--------------------------------------
Assignee: Michael Anstis (was: Guilherme Carreiro)
> [DMN Designer] Boxed Expressions - Enhance component title
> ----------------------------------------------------------
>
> Key: DROOLS-3706
> URL: https://issues.jboss.org/browse/DROOLS-3706
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screen Shot 2019-02-25 at 2.33.44 PM.png
>
>
> Improve the boxed expression title.
> - Rename "<< Back to <NODE_NAME>" (*"<< Back to Decision-1"*) to just *"<< Back"*
> - Rename "<BOXED_EXPRESSION_TYPE>" (*"Decision Table"*) to "<NODE_NAME> (<BOXED_EXPRESSION_TYPE>)" (*"Decision-1 (Decision Table)"*)
> ⚠️ Notice: Check the latest Liz mockup for this task.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months