October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3151: ---------------------------------------- [~uxdlc] [~bdellasc] [~tirelli] New "colouring" (for GDT and DMN) attached FYI. > [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns > ---------------------------------------------------------------------------------- > > Key: DROOLS-3151 > URL: https://issues.jboss.org/browse/DROOLS-3151 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: VisualDesign, drools-tools > Attachments: DROOLS-3151-DMN.png, DROOLS-3151-GDT.png, GDT.png, dtable-column-colours.png > > > [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns. > {quote} > this is way too subtle, to be honest... can we get colours that are a bit more distinguishable? > {quote} > See the attached screenshot. > Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3151: ----------------------------------- Attachment: DROOLS-3151-DMN.png DROOLS-3151-GDT.png > [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns > ---------------------------------------------------------------------------------- > > Key: DROOLS-3151 > URL: https://issues.jboss.org/browse/DROOLS-3151 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: VisualDesign, drools-tools > Attachments: DROOLS-3151-DMN.png, DROOLS-3151-GDT.png, GDT.png, dtable-column-colours.png > > > [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns. > {quote} > this is way too subtle, to be honest... can we get colours that are a bit more distinguishable? > {quote} > See the attached screenshot. > Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11244) RemoteStatefulEJBConcurrentFailoverTestCase fails intermittently again (more frequent after Infinispan 9.4.0 upgrade)

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFLY-11244?page=com.atlassian.jira.plugin... ] Rostislav Svoboda commented on WFLY-11244: ------------------------------------------ [~rhusar] fyi > RemoteStatefulEJBConcurrentFailoverTestCase fails intermittently again (more frequent after Infinispan 9.4.0 upgrade) > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11244 > URL: https://issues.jboss.org/browse/WFLY-11244 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Rostislav Svoboda > Assignee: Paul Ferraro > Priority: Major > > RemoteStatefulEJBConcurrentFailoverTestCase fails intermittently again (more frequent after Infinispan 9.4.0 upgrade) > {code} > javax.ejb.EJBException: org.infinispan.util.concurrent.TimeoutException: > Could not acquire lock on InfinispanBeanGroupKey(UUIDSessionID [5a0d25a0-ab32-49e3-b849-016756dfa2e4]) > in behalf of transaction GlobalTx:node-2:7. Current owner GlobalTx:node-2:5. > at org.jboss.as.ejb3@15.0.0.Alpha1-SNAPSHOT//org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:220) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) > at java.base/java.lang.Thread.run(Thread.java:844) > Suppressed: java.net.ConnectException: Connection refused > at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) > at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:327) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) > at ...asynchronous invocation...(Unknown Source) > {code} > Stacktrace example: https://ci.wildfly.org/viewLog.html?buildId=126049&buildTypeId=WF_PullReq... > Test history: https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3184) [DMN Designer] Edge source and target WayPoints are same

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3184?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3184: -------------------------------------- Assignee: Matteo Mortari (was: Michael Anstis) > [DMN Designer] Edge source and target WayPoints are same > -------------------------------------------------------- > > Key: DROOLS-3184 > URL: https://issues.jboss.org/browse/DROOLS-3184 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2018-10-25 12-12-20.png, a1.dmn, image (2).png > > > The source of DMN model has same waypoint for edge source and target. If you open the attached [^a1.dmn] model, there will be: > {code:xml} > <dmndi:DMNEdge id="dmnedge-_594C4BE1-52D0-4009-9D4F-9960957539FB" dmnElementRef="_594C4BE1-52D0-4009-9D4F-9960957539FB"> > <di:waypoint xmlns:di="http://www.omg.org/spec/DMN/20180521/DI/" x="50" y="25"/> > <di:waypoint xmlns:di="http://www.omg.org/spec/DMN/20180521/DI/" x="50" y="25"/> > </dmndi:DMNEdge> > {code} > However in our designer the edge has different waypoints: > !Screenshot from 2018-10-25 12-12-20.png|thumbnail! > In the external modeling tools, the edge is rendered according to real waypoints and this the edge is not visible: > !image (2).png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11244) RemoteStatefulEJBConcurrentFailoverTestCase fails intermittently again (more frequent after Infinispan 9.4.0 upgrade)

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFLY-11244: ---------------------------------------- Summary: RemoteStatefulEJBConcurrentFailoverTestCase fails intermittently again (more frequent after Infinispan 9.4.0 upgrade) Key: WFLY-11244 URL: https://issues.jboss.org/browse/WFLY-11244 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Rostislav Svoboda Assignee: Paul Ferraro RemoteStatefulEJBConcurrentFailoverTestCase fails intermittently again (more frequent after Infinispan 9.4.0 upgrade) {code} javax.ejb.EJBException: org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on InfinispanBeanGroupKey(UUIDSessionID [5a0d25a0-ab32-49e3-b849-016756dfa2e4]) in behalf of transaction GlobalTx:node-2:7. Current owner GlobalTx:node-2:5. at org.jboss.as.ejb3@15.0.0.Alpha1-SNAPSHOT//org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:220) at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) at java.base/java.lang.Thread.run(Thread.java:844) Suppressed: java.net.ConnectException: Connection refused at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:327) at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) at ...asynchronous invocation...(Unknown Source) {code} Stacktrace example: https://ci.wildfly.org/viewLog.html?buildId=126049&buildTypeId=WF_PullReq... Test history: https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3143) [DMN Designer] DMN unmarshal from 1.1, 1.2; marshal as 1.2

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3143?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3143: -------------------------------- Description: Unmarshalling side will need to open either 1.1 or 1.2 models. Marshalling side will need to persist always as 1.2 model. /cc [~manstis] h2. Manual acceptance test Check marshalling by opening in other tool - Connections (x) DROOLS-3184 - Output Type Ref -- Decision --- Decision Table --- Literal Expression --- Context --- Function -- BKM -- Input Data - Custom Data Type was: Unmarshalling side will need to open either 1.1 or 1.2 models. Marshalling side will need to persist always as 1.2 model. /cc [~manstis] > [DMN Designer] DMN unmarshal from 1.1, 1.2; marshal as 1.2 > ---------------------------------------------------------- > > Key: DROOLS-3143 > URL: https://issues.jboss.org/browse/DROOLS-3143 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Labels: drools-tools > > Unmarshalling side will need to open either 1.1 or 1.2 models. > Marshalling side will need to persist always as 1.2 model. > /cc [~manstis] > h2. Manual acceptance test > Check marshalling by opening in other tool > - Connections (x) DROOLS-3184 > - Output Type Ref > -- Decision > --- Decision Table > --- Literal Expression > --- Context > --- Function > -- BKM > -- Input Data > - Custom Data Type -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3184) [DMN Designer] Edge source and target WayPoints are same

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3184: ----------------------------------- Summary: [DMN Designer] Edge source and target WayPoints are same Key: DROOLS-3184 URL: https://issues.jboss.org/browse/DROOLS-3184 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.14.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2018-10-25 12-12-20.png, a1.dmn, image (2).png The source of DMN model has same waypoint for edge source and target. If you open the attached [^a1.dmn] model, there will be: {code:xml} <dmndi:DMNEdge id="dmnedge-_594C4BE1-52D0-4009-9D4F-9960957539FB" dmnElementRef="_594C4BE1-52D0-4009-9D4F-9960957539FB"> <di:waypoint xmlns:di="http://www.omg.org/spec/DMN/20180521/DI/" x="50" y="25"/> <di:waypoint xmlns:di="http://www.omg.org/spec/DMN/20180521/DI/" x="50" y="25"/> </dmndi:DMNEdge> {code} However in our designer the edge has different waypoints: !Screenshot from 2018-10-25 12-12-20.png|thumbnail! In the external modeling tools, the edge is rendered according to real waypoints and this the edge is not visible: !image (2).png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10997) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-10997?page=com.atlassian.jira.plugin... ] Bartosz Baranowski updated WFLY-10997: -------------------------------------- Workaround Description: (was: @RunAs("ejbuser") seems to alleviate problem. ) > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-10997 > URL: https://issues.jboss.org/browse/WFLY-10997 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > Assignee: Bartosz Baranowski > Priority: Major > Labels: downstream_dependency > Original Estimate: 3 days > Remaining Estimate: 3 days > > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > Using WildFlyInitialContextFactory and calling a remote EJB server. > Observations: > 1) If the ejb lookup is "reproducer/TestSLSB!test.Test" (basically like a RemoteNaming lookup), the ejb is invoked successfully, but the caller is seen as anonymous instead of the ejbuser which is specified in the Context properties. > Using the ejb-client type lookup: ejb:/reproducer/TestSLSB!test.Test , then it shows up as ejbuser as expected > 2) if a client creates 2 InitialContexts and uses the lookup reproducer/TestSLSB!test.Test" on ctx1 , then uses the lookup "ejb:/reproducer/TestSLSB!test.Test " on ctx2 in that order, then they both show anonymous (as if it uses only the context that was created first). > If you switch the order, and use ejb:/reproducer/TestSLSB!test.Test first, then they both show ejbuser -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10997) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-10997?page=com.atlassian.jira.plugin... ] Bartosz Baranowski updated WFLY-10997: -------------------------------------- Workaround Description: @RunAs("ejbuser") seems to alleviate problem. (was: @RunAs("ejbuser") seems to alleviate problem. (At least if declared on Servlet from: http://lacrosse.corp.redhat.com/lgao/WFLY-10997_reproducer.zip)) > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-10997 > URL: https://issues.jboss.org/browse/WFLY-10997 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > Assignee: Bartosz Baranowski > Priority: Major > Labels: downstream_dependency > Original Estimate: 3 days > Remaining Estimate: 3 days > > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > Using WildFlyInitialContextFactory and calling a remote EJB server. > Observations: > 1) If the ejb lookup is "reproducer/TestSLSB!test.Test" (basically like a RemoteNaming lookup), the ejb is invoked successfully, but the caller is seen as anonymous instead of the ejbuser which is specified in the Context properties. > Using the ejb-client type lookup: ejb:/reproducer/TestSLSB!test.Test , then it shows up as ejbuser as expected > 2) if a client creates 2 InitialContexts and uses the lookup reproducer/TestSLSB!test.Test" on ctx1 , then uses the lookup "ejb:/reproducer/TestSLSB!test.Test " on ctx2 in that order, then they both show anonymous (as if it uses only the context that was created first). > If you switch the order, and use ejb:/reproducer/TestSLSB!test.Test first, then they both show ejbuser -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11136) It is not possible to build Mojarra with JDK10+

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/WFLY-11136?page=com.atlassian.jira.plugin... ] Ingo Weiss reassigned WFLY-11136: --------------------------------- Assignee: Ingo Weiss (was: Farah Juma) > It is not possible to build Mojarra with JDK10+ > ----------------------------------------------- > > Key: WFLY-11136 > URL: https://issues.jboss.org/browse/WFLY-11136 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Jan Kašík > Assignee: Ingo Weiss > Priority: Major > Labels: Java11 > > It is not possible to build Mojarra with JDK10+. See [issue on project page (upstream)|https://github.com/eclipse-ee4j/mojarra/issues/4461]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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