January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2219) CCE on node memories when using rule units but inserting a fact into the shared memory

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2219: ----------------------------------- Summary: CCE on node memories when using rule units but inserting a fact into the shared memory Key: DROOLS-2219 URL: https://issues.jboss.org/browse/DROOLS-2219 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Edson Tirelli -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2219) CCE on node memories when using rule units but inserting a fact into the shared memory

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2219?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-2219: ----------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > CCE on node memories when using rule units but inserting a fact into the shared memory > -------------------------------------------------------------------------------------- > > Key: DROOLS-2219 > URL: https://issues.jboss.org/browse/DROOLS-2219 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2219) CCE on node memories when using rule units but inserting a fact into the shared memory

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2219?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2219: -------------------------------- Component/s: core engine > CCE on node memories when using rule units but inserting a fact into the shared memory > -------------------------------------------------------------------------------------- > > Key: DROOLS-2219 > URL: https://issues.jboss.org/browse/DROOLS-2219 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2155) table editor should use full canvas area available

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2155?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2155: ----------------------------------- Sprint: 2018 Week 01-02 > table editor should use full canvas area available > -------------------------------------------------- > > Key: DROOLS-2155 > URL: https://issues.jboss.org/browse/DROOLS-2155 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Priority: Minor > Labels: UX > > DMN table editor should use the full canvas width that is available (minus panels, toolbars, etc.) It should not appear as a smaller fixed size area, with scrollbars, within the canvas. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1937) [DMN Editor] Dynamic Form Properties with nested hierarchy binds to wrong object/widget

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1937?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-1937: ---------------------------------------- [~pere.fernandez] [~roger600] Hi, I don't suppose anyone has any pointers for how [~pere.fernandez] worked around/fixed this!?!? It is beginning to "bite" the DMN Editor that more people are starting to fiddle with.. > [DMN Editor] Dynamic Form Properties with nested hierarchy binds to wrong object/widget > --------------------------------------------------------------------------------------- > > Key: DROOLS-1937 > URL: https://issues.jboss.org/browse/DROOLS-1937 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Roger Martínez > Priority: Critical > Labels: Stunner > > The Dynamic Form generated from a nested object hierarchy binds objects/widgets to the incorrect instances. For example; the below classes define an {{Id}} form field that is used in both {{InputData}} (through inheritance) and {{InformationItem}} (through sub-form reference and inheritance). When changing the {{Id}} field (for example) in the {{InputData}} form property the "Id" value of the nested "Information Item" is updated. > {code} > public abstract class DMNModelInstrumentedBase implements DMNDefinition { > > //No @FormFields etc > > } > > public abstract class DMNElement extends DMNModelInstrumentedBase { > > @Property > @FormField > protected Id id; > > @Property > @FormField(afterElement = "id") > protected Label label; > > @Property > @FormField(afterElement = "label") > protected Description description; > > .... > } > > public abstract class NamedElement extends DMNElement { > > @Property > @FormField(afterElement = "description") > protected Name name; > > .... > } > > @FormDefinition(policy = FieldPolicy.ONLY_MARKED) > public class InformationItem extends NamedElement implements DMNPropertySet { > > @Property > @FormField(afterElement = "name") > protected QName typeRef; > > .... > } > public abstract class DRGElement extends NamedElement {} > @FormDefinition(policy = FieldPolicy.ONLY_MARKED) > public class InputData extends DRGElement { > ... > @PropertySet > @FormField(afterElement = "name") > protected InformationItem variable; > ... > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Context Entry Definition is not saved

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2217: ---------------------------------------- [~tari_manga] I took [~jomarko] wording on face value; and made the Decision's Expression a Context with two ContextEntries.... The UI does not allow Users to create a ContextEntry as the child of a Decision; only as per the DMN hierachy: Decision->Context->ContextEntry. > [DMN Editor] Context Entry Definition is not saved > -------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-483) GssapiTestSuite and Gs2Test fail with com.ibm.security.krb5.KrbException, status code: 9 for IBM JDK

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-483?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-483: -------------------------------- Will be fixed as suggested by [~olukas] + GSS compatiblity tests needs to be reconsidered - it was not good idea and it has more troubles like ELY-1298. > GssapiTestSuite and Gs2Test fail with com.ibm.security.krb5.KrbException, status code: 9 for IBM JDK > ---------------------------------------------------------------------------------------------------- > > Key: ELY-483 > URL: https://issues.jboss.org/browse/ELY-483 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta5 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Labels: ibm-java > > Test cases initialization from GssapiTestSuite and Gs2Test fail with following exception for IBM JDK: > {code} > javax.security.auth.login.FailedLoginException: > Login error: com.ibm.security.krb5.KrbException, status code: 9 > message: The client or server has a null key > at com.ibm.security.jgss.i18n.I18NException.throwFailedLoginException(I18NException.java:15) > at com.ibm.security.auth.module.Krb5LoginModule.j(Krb5LoginModule.java:727) > at com.ibm.security.auth.module.Krb5LoginModule.b(Krb5LoginModule.java:307) > at com.ibm.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:59) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at javax.security.auth.login.LoginContext.invoke(LoginContext.java:788) > at javax.security.auth.login.LoginContext.access$000(LoginContext.java:196) > at javax.security.auth.login.LoginContext$5.run(LoginContext.java:721) > at javax.security.auth.login.LoginContext$5.run(LoginContext.java:719) > at java.security.AccessController.doPrivileged(AccessController.java:686) > at javax.security.auth.login.LoginContext.invokeCreatorPriv(LoginContext.java:719) > at javax.security.auth.login.LoginContext.login(LoginContext.java:593) > at org.wildfly.security.sasl.gssapi.JaasUtil.login(JaasUtil.java:71) > at org.wildfly.security.sasl.gssapi.JaasUtil.loginClient(JaasUtil.java:53) > at org.wildfly.security.sasl.gssapi.JdkClientJdkServer.initialise(JdkClientJdkServer.java:47) > ... > {code} > It is test case issue but it can hide any another functional issue because affected tests are not running with IBM JDK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Context Entry Definition is not saved

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2217: ---------------------------------------- Additionally, I don't believe a Decision can be a "context entry". A Context, yes, a Context-Entry alone, I don't think so. /cc [~manstis][~jomarko] > [DMN Editor] Context Entry Definition is not saved > -------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Context Entry Definition is not saved

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2217: ---------------------------------------- [~jomarko] I tried creating a Context with current code (at 5-Jan) and could not replicate this. Can you check/provide more steps? > [DMN Editor] Context Entry Definition is not saved > -------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Context Entry Definition is not saved

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-2217: -------------------------------------- Assignee: Matteo Mortari (was: Michael Anstis) > [DMN Editor] Context Entry Definition is not saved > -------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 January 2018