March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3759) Extends editing support inside CollectionEditor

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3759?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3759: ---------------------------------- Labels: ScenarioSimulation (was: ) > Extends editing support inside CollectionEditor > ----------------------------------------------- > > Key: DROOLS-3759 > URL: https://issues.jboss.org/browse/DROOLS-3759 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: 1.png > > > Currently the CollectionEditor does not allow to insert/edit "complex" properties (i.e. properties mapped to other bean/datatype) but only for "simple" ones (e.g. String, number, boolean). > It should be possible to *at least* insert/edit first-level complex properties > h3. Issues that need to be addressed as a part of this task: > # The top-level collections message inside the *Unsupported DMN asset* should no longer be displayed: > !1.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3783) Fix runner for top-level collection

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3783?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3783: ---------------------------------- Labels: ScenarioSimulation (was: ) > Fix runner for top-level collection > ----------------------------------- > > Key: DROOLS-3783 > URL: https://issues.jboss.org/browse/DROOLS-3783 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Fix the runner for scenarios containing top-level collection -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3783) Fix runner for top-level collection

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3783?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3783: ---------------------------------- Component/s: Scenario Simulation and Testing > Fix runner for top-level collection > ----------------------------------- > > Key: DROOLS-3783 > URL: https://issues.jboss.org/browse/DROOLS-3783 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Fix the runner for scenarios containing top-level collection -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3782) Enable top-level collection support

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3782?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3782: ---------------------------------- Labels: ScenarioSimulation (was: ) > Enable top-level collection support > ----------------------------------- > > Key: DROOLS-3782 > URL: https://issues.jboss.org/browse/DROOLS-3782 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Enable top-level collection support for dmn scenarios. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3782) Enable top-level collection support

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3782?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3782: ---------------------------------- Component/s: Scenario Simulation and Testing > Enable top-level collection support > ----------------------------------- > > Key: DROOLS-3782 > URL: https://issues.jboss.org/browse/DROOLS-3782 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Enable top-level collection support for dmn scenarios. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11910) Upgrade Infinispan to 9.4.11.Final

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-11910: ----------------------------------- Summary: Upgrade Infinispan to 9.4.11.Final Key: WFLY-11910 URL: https://issues.jboss.org/browse/WFLY-11910 Project: WildFly Issue Type: Component Upgrade Components: Clustering Affects Versions: 16.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro https://issues.jboss.org/projects/ISPN/versions/12340950 https://issues.jboss.org/projects/ISPN/versions/12341250 https://issues.jboss.org/projects/ISPN/versions/12341373 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11904) No ActiveMQ connection factory with RAR deployment

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11904?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet commented on WFLY-11904: ------------------------------------------ @reporter Could you be be more precise in your reproducer as 1st I can't build current master or wildfly-camel (issue with org.eclipse.sensinact.gateway.nthbnd:parent:pom:1.5-SNAPSHOT) and it seems to be on WildFly 16. I tried to deploy manually and all seemed to be working except for missing quotes in serverUrl (but I was using the cli). > No ActiveMQ connection factory with RAR deployment > -------------------------------------------------- > > Key: WFLY-11904 > URL: https://issues.jboss.org/browse/WFLY-11904 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Thomas Diesler > Assignee: ehsavoie Hugonnet > Priority: Major > Fix For: 17.0.0.Beta1 > > > The ActiveMQ RAR deployment no longer registers its connection factory nor destination. > Is org.apache.activemq:activemq-rar:rar:5.15.7 no longer supported? > CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2783 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3741) Create HTML/CSS for Test scenario coverage report

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3741?page=com.atlassian.jira.plugi... ] Klara Kufova resolved DROOLS-3741. ---------------------------------- Resolution: Done > Create HTML/CSS for Test scenario coverage report > ------------------------------------------------- > > Key: DROOLS-3741 > URL: https://issues.jboss.org/browse/DROOLS-3741 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Sarah Rambacher > Priority: Major > Labels: ScenarioSimulation > > Create HTML/CSS for this new dock component > https://issues.jboss.org/browse/DROOLS-3516 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3341) Duplicate DO columns

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3341?page=com.atlassian.jira.plugi... ] Klara Kufova reassigned DROOLS-3341: ------------------------------------ Assignee: Yeser Amer (was: Gabriele Cardosi) > Duplicate DO columns > -------------------- > > Key: DROOLS-3341 > URL: https://issues.jboss.org/browse/DROOLS-3341 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: duplicate.png, multiDO.png > > > As a user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario. > * As a user I want a means to create a data object instance in the test template using an existing statement column, so that I can quickly create instances from the test table. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11907) NPE trying to use Resteasy Client inside CDI Async Event

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-11907?page=com.atlassian.jira.plugin... ] Marek Kopecký updated WFLY-11907: --------------------------------- Affects Version/s: 14.0.0.Final > NPE trying to use Resteasy Client inside CDI Async Event > -------------------------------------------------------- > > Key: WFLY-11907 > URL: https://issues.jboss.org/browse/WFLY-11907 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 14.0.0.Final, 16.0.0.Final > Reporter: Cody Lerum > Assignee: Matej Novotny > Priority: Major > > When attempting to use the Resteasy Client inside a CDI Async Event a NPE is thrown. > {code} > 12:49:33,513 ERROR [stderr] (Weld Thread Pool -- 4) java.lang.RuntimeException: java.lang.NullPointerException > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:49) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.getProviderFactory(ResteasyClientBuilder.java:362) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.build(ResteasyClientBuilder.java:395) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.build(ResteasyClientBuilder.java:38) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at com.outjected.demo.ResteasyClientEventObserver.load(ResteasyClientEventObserver.java:28) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at com.outjected.demo.ResteasyClientEventObserver.observeAsync(ResteasyClientEventObserver.java:23) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at java.lang.reflect.Method.invoke(Method.java:498) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.MethodInvocationStrategy$DefaultMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:109) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.util.Observers.notify(Observers.java:166) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.notifyAsyncObserver(ObserverNotifier.java:413) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$notifyAsyncObservers$5(ObserverNotifier.java:356) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$null$8(ObserverNotifier.java:438) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.security.spi.SecurityServices.lambda$getSecurityContextAssociator$0(SecurityServices.java:80) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$createSupplier$9(ObserverNotifier.java:435) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.CompletableFuture$AsyncSupply.run$$$capture(CompletableFuture.java:1590) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at java.lang.Thread.run(Thread.java:748) > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.threads.JBossThread.run(JBossThread.java:485) > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) Caused by: java.lang.NullPointerException > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.registerProviders(RegisterBuiltin.java:60) > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:45) > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) ... 28 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019