November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3249) [DMN Designer] Add support for optional typeRefs

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3249?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3249: ----------------------------------- Story Points: 5 > [DMN Designer] Add support for optional typeRefs > ------------------------------------------------ > > Key: DROOLS-3249 > URL: https://issues.jboss.org/browse/DROOLS-3249 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > > At the moment {{TypeRef}} is a mandatory field within the editor. > This is a hard limitation of use of the Properties Panel bean-binding (it cannot bind to {{null}} values). However the DMN Specification states that {{TypeRef}} are optional (and we are working around by changing the _default_ to {{Any}} - see [DROOLS-3248|https://issues.jboss.org/browse/DROOLS-3248]). > We need to change the UI and marshaller to be able to support _optional_ {{TypeRef}}. This would (probably) require adding a _magic_ value to {{BuiltInType}} representing a "null" selection. It would need to: > - Appear at the top of the "Data Type selector" widget (with label "<None>" or similar) > - Be the _selected_ option when the {{TypeRef}} is the new _magic_ value (this should happen automatically, but worth checking!) > - The marshaller should set the {{TypeRef}} to the _magic_ {{BuiltInType}} if the DMN model (coming from XML->{{kie-dmn-model}}->workbench model) has a {{null}} {{TypeRef}} - the _magic_ value is only to be used _client-side_. > - The marshaller should set the {{TypeRef}} to {{null}} when converting from the workbench model to {{kie-dmn-model}} and the workbench model {{TypeRef}} is the _magic_ value - again, the _magic_ value is only to be used _client-side_. > - Check that creating new data-types does not show the _magic_ value (it uses a different widget, but population of the widget probably iterates all {{BuiltInType}}. > [~tari_manga] [~karreiro] seem reasonable to you? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3248) [DMN Designer] QName: Default to be 'Any' not 'string'

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3248?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3248: ----------------------------------- Story Points: 2 > [DMN Designer] QName: Default to be 'Any' not 'string' > ------------------------------------------------------ > > Key: DROOLS-3248 > URL: https://issues.jboss.org/browse/DROOLS-3248 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > > At the moment the _default_ {{QName}} is {{string}} however [~tirelli] has requested it be changed to {{Any}}. Please also note that the the _name_ for {{Any}} should be "*A*ny" and not "*a*ny" as we currently have. See: > https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-dmn/k... > https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-dmn/k... > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-209) NoSuchAlgorithmException in SocketHandlerTests on IBM JDK

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-209?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-209: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/204 > NoSuchAlgorithmException in SocketHandlerTests on IBM JDK > --------------------------------------------------------- > > Key: LOGMGR-209 > URL: https://issues.jboss.org/browse/LOGMGR-209 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.5.Final > Reporter: Nikoleta Žiaková > Assignee: James Perkins > Priority: Major > > Following tests fail on IBM JDK: > {code} > org.jboss.logmanager.handlers.SocketHandlerTests#testProtocolChange > org.jboss.logmanager.handlers.SocketHandlerTests#testTlsConnection > org.jboss.logmanager.handlers.SocketHandlerTests#testTlsConfig > {code} > Error: > {code} > java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.aj) > {code} > Stack Trace: > {code} > Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.aj) > at java.security.Provider$Service.newInstance(Provider.java:1628) > at sun.security.jca.GetInstance.getInstance(GetInstance.java:248) > at sun.security.jca.GetInstance.getInstance(GetInstance.java:176) > at javax.net.ssl.SSLContext.getInstance(SSLContext.java:6) > at javax.net.ssl.SSLContext.getDefault(SSLContext.java:8) > at javax.net.ssl.SSLServerSocketFactory.getDefault(SSLServerSocketFactory.java:32) > ... 29 more > Caused by: java.security.KeyStoreException: IBMKeyManager: Problem accessing key store java.io.IOException: Invalid keystore format > at com.ibm.jsse2.ah.a(ah.java:72) > at com.ibm.jsse2.aj.g(aj.java:5) > at com.ibm.jsse2.aj.<init>(aj.java:13) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57) > at java.lang.reflect.Constructor.newInstance(Constructor.java:437) > at java.security.Provider$Service.newInstance(Provider.java:1606) > ... 34 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-209) NoSuchAlgorithmException in SocketHandlerTests on IBM JDK

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-209?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-209: --------------------------------- Fix Version/s: 2.2.0.Final > NoSuchAlgorithmException in SocketHandlerTests on IBM JDK > --------------------------------------------------------- > > Key: LOGMGR-209 > URL: https://issues.jboss.org/browse/LOGMGR-209 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.5.Final > Reporter: Nikoleta Žiaková > Assignee: James Perkins > Priority: Major > Fix For: 2.2.0.Final > > > Following tests fail on IBM JDK: > {code} > org.jboss.logmanager.handlers.SocketHandlerTests#testProtocolChange > org.jboss.logmanager.handlers.SocketHandlerTests#testTlsConnection > org.jboss.logmanager.handlers.SocketHandlerTests#testTlsConfig > {code} > Error: > {code} > java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.aj) > {code} > Stack Trace: > {code} > Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.aj) > at java.security.Provider$Service.newInstance(Provider.java:1628) > at sun.security.jca.GetInstance.getInstance(GetInstance.java:248) > at sun.security.jca.GetInstance.getInstance(GetInstance.java:176) > at javax.net.ssl.SSLContext.getInstance(SSLContext.java:6) > at javax.net.ssl.SSLContext.getDefault(SSLContext.java:8) > at javax.net.ssl.SSLServerSocketFactory.getDefault(SSLServerSocketFactory.java:32) > ... 29 more > Caused by: java.security.KeyStoreException: IBMKeyManager: Problem accessing key store java.io.IOException: Invalid keystore format > at com.ibm.jsse2.ah.a(ah.java:72) > at com.ibm.jsse2.aj.g(aj.java:5) > at com.ibm.jsse2.aj.<init>(aj.java:13) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57) > at java.lang.reflect.Constructor.newInstance(Constructor.java:437) > at java.security.Provider$Service.newInstance(Provider.java:1606) > ... 34 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3158) [DMN Designer] Automatic Layout Feature - toolbar integration

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3158?page=com.atlassian.jira.plugi... ] Jozef Marko deleted DROOLS-3158: -------------------------------- > [DMN Designer] Automatic Layout Feature - toolbar integration > ------------------------------------------------------------- > > Key: DROOLS-3158 > URL: https://issues.jboss.org/browse/DROOLS-3158 > Project: Drools > Issue Type: Epic > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > This requirement follows DROOLS-3061. > The automatic layout feature should be available from designer toolbar, furthermore we should allow user to undo/redo the automatic layout positioning. > h2. Acceptance criteria > - Add a toolbar button to perform the automatic layout operation > -- Button visible in toolbar > -- Disabled in read only mode, enabled otherwise > - Allow to undo/redo the button's action > -- implies using the commands API instead of applying the changes directly on the graph instance > - Show the notification to the user as in DROOLS-3061 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11288) Missing proton SaslListener

by Karl Sorensen (Jira)

Karl Sorensen created WFLY-11288: ------------------------------------ Summary: Missing proton SaslListener Key: WFLY-11288 URL: https://issues.jboss.org/browse/WFLY-11288 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 14.0.0.Final Reporter: Karl Sorensen Assignee: Jeff Mesnil When trying to use an external client to connect to ActiveMQ/Artemis instance using the AMQP protocol an SASL exception is thrown. 2018-11-05 12:08:01,636 TRACE [org.jboss.modules] (Thread-1 (activemq-netty-threads)) Class org.apache.qpid.proton.engine.SaslListener not found from Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base)) Issue can be resolved by manually including proton-j-0.27.3.jar into the org.apache.activemq.artemis.protocol.amqp module as discussed in the attached forum post. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1942) [DMN Editor] InformationItem's "Name" is always the same as the containing node

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1942?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-1942: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 45-47 (was: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26) > [DMN Editor] InformationItem's "Name" is always the same as the containing node > ------------------------------------------------------------------------------- > > Key: DROOLS-1942 > URL: https://issues.jboss.org/browse/DROOLS-1942 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Whilst an {{InformationItem}} Node has a "Name" its value is always the same as the containing Node's "Name" (for {{InputData}}, {{Decision}} and {{BusinessKnowledgeModel}}). {{ContextEntry}}'s "Name" are not the same as outer most node's "Name" (as a {{ContextEntry}} is contained within a {{Context}} and not directly in a node itself). > It is proposed that this synchronization should be handled in the "Stunner to (org.kie) DMN model" marshalling. Therefore we need to remove the "Name" {{@FormField}} from {{InformationItem}}. > [~tari_manga] [~tirelli] Please confirm. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3250) [DMN Designer] Information Item name is empty by default

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3250?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3250: ----------------------------------- Sprint: 2018 Week 45-47 > [DMN Designer] Information Item name is empty by default > -------------------------------------------------------- > > Key: DROOLS-3250 > URL: https://issues.jboss.org/browse/DROOLS-3250 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > The properties of decision has two sections with *Name* property. One general *Decision Name* and one *Information Item Name*. > The second *Information Item Name* reflects in <variable/> tag of the backing xml file. Its value important for the runtime. > I think we should solve this issue doing two actions: > - Make *Information Item Name* readonly > - Set *Information Item Name* automatically according to *Decision Name* -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3258) [DMN Designer] Import external DMN file (initial R&D)

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3258?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3258: --------------------------------------- Summary: [DMN Designer] Import external DMN file (initial R&D) (was: [DMN Designer] Import external DMN file) > [DMN Designer] Import external DMN file (initial R&D) > ----------------------------------------------------- > > Key: DROOLS-3258 > URL: https://issues.jboss.org/browse/DROOLS-3258 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > This is a R&D task. > Check DMN spec, the current code, break the initial tasks, convert this JIRA to a EPIC and update its description for the import feature. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3258) [DMN Designer] Import external DMN file

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3258?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3258: --------------------------------------- Description: This is a R&D task. Check DMN spec, the current code, break the initial tasks, convert this JIRA to a EPIC and update its description for the import feature. was: This is a R&D task. Check DMN spec, the current code, break the initial tasks and update this description for the import feature. > [DMN Designer] Import external DMN file > --------------------------------------- > > Key: DROOLS-3258 > URL: https://issues.jboss.org/browse/DROOLS-3258 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > This is a R&D task. > Check DMN spec, the current code, break the initial tasks, convert this JIRA to a EPIC and update its description for the import feature. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2018