December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1031) Start using istio upstream for upstream pipeline instead of maistra

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1031?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1031. ---------------------------------- Resolution: Done Added https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/main-pipelines... > Start using istio upstream for upstream pipeline instead of maistra > ------------------------------------------------------------------- > > Key: SWSQE-1031 > URL: https://issues.redhat.com/browse/SWSQE-1031 > Project: Kiali QE > Issue Type: Story > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > TODO > Istio docs - https://istio.io/docs/setup/platform-setup/openshift/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4879) [UX] [DMN Designer] unification of import flash messages

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4879?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4879: ------------------------------------------- [~jomarko] [~dadossan] There was some confusion on this topic, but I think we should align with what ultimately decided on in a recent AF jira: https://issues.redhat.com/browse/AF-2322. {quote}"We agreed to the following change: Include the "X" on the right side of all notifications."{quote} cc [~ederign] ^^ > [UX] [DMN Designer] unification of import flash messages > -------------------------------------------------------- > > Key: DROOLS-4879 > URL: https://issues.redhat.com/browse/DROOLS-4879 > Project: Drools > Issue Type: Bug > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: drools-tools > > We should unify the flash messages related to import data types. See the github comment here https://github.com/kiegroup/kie-wb-common/pull/3071#issuecomment-566436373 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4878) Test Scenario: fix support for default stateless kieSession

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4878?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4878: ---------------------------------- Story Points: 3 > Test Scenario: fix support for default stateless kieSession > ----------------------------------------------------------- > > Key: DROOLS-4878 > URL: https://issues.redhat.com/browse/DROOLS-4878 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > How to reproduce: > - edit kmodule.xml and create only a default stateless session > {code:java} > <kmodule xmlns="http://www.drools.org/xsd/kmodule" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <kbase name="myKieBase"> > <ksession name="mySession" type="stateless" default="true"/> > </kbase> > </kmodule> > {code} > - create a Rule test scenario and specify in Setting panel {{stateless}} > - run -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4878) Test Scenario: fix support for default stateless kieSession

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4878?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4878: ---------------------------------- Sprint: 2019 Week 50-52 (from Dec 9) > Test Scenario: fix support for default stateless kieSession > ----------------------------------------------------------- > > Key: DROOLS-4878 > URL: https://issues.redhat.com/browse/DROOLS-4878 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > How to reproduce: > - edit kmodule.xml and create only a default stateless session > {code:java} > <kmodule xmlns="http://www.drools.org/xsd/kmodule" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <kbase name="myKieBase"> > <ksession name="mySession" type="stateless" default="true"/> > </kbase> > </kmodule> > {code} > - create a Rule test scenario and specify in Setting panel {{stateless}} > - run -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11566) ConstraintDeclarationException on JAX-RS/EJB Methods with List/Set query parameter

by Matěj Novotný (Jira)

[ https://issues.redhat.com/browse/WFLY-11566?page=com.atlassian.jira.plugi... ] Matěj Novotný commented on WFLY-11566: -------------------------------------- After some digging, [~mkouba], [~tomekadamski] and I came up with the following... The instance of [{{ValidatorFactory}} that WFLY uses|https://github.com/wildfly/wildfly/blob/master/bean-validation/src/m...] seems to be a CDI-enabled instance (a bean) that is provided somewhere else and retrieved via CDI [here|https://github.com/wildfly/wildfly/blob/master/weld/bean-validation/...]. We think that the bean is most likely provided via [Hibernate Validator CDI extension in their repository|https://github.com/hibernate/hibernate-validator/blob/master/c...] - this way you get fully configured Factory instance. Now, what we need is to be able to configure this instance somehow, namely to pass in [BeanMetadataClassNormalizer|https://github.com/hibernate/hibernate-valida...] that will be able to unwrap EJB proxies. So the theoretical options are: * Configure the Factory once WFLY gets it ** Not sure this is possible, I suspect it will be immutable * Provide a custom new bean that will replace this Factory (e.g. an enabled CDI alternative that will "override" the original bean), this new bean will be configured by WFLY ** This is hacky, but something that could work for starters, CDI bean annotated with {{@Alternative @Priority()}} will be used instead of the original bean assuming it has same type(s) and qualifier(s) * Find a way to pass config options to Hibernate Validator so they are aware of it while booting and providing their own bean ** NOTE - you cannot do that via another CDI bean. Assuming HV is providing bean via extension, they won't be able to use other beans at that point, it is too early in the process. I'd be nice to have some input/confirmation from HV team [~guillaume.smet] [~y.rodiere] on how the bean is provided and whether it can be configured afterwards? > ConstraintDeclarationException on JAX-RS/EJB Methods with List/Set query parameter > ---------------------------------------------------------------------------------- > > Key: WFLY-11566 > URL: https://issues.redhat.com/browse/WFLY-11566 > Project: WildFly > Issue Type: Bug > Components: Bean Validation, EJB, REST > Affects Versions: 14.0.0.Final, 15.0.1.Final > Reporter: Alexander Wagner > Assignee: Tomasz Adamski > Priority: Critical > Labels: downstream_dependency > Attachments: WFLY-11566-3.tar > > > You got an exception if you call methods on JAX-RS endpoints which are also e.g. a stateless EJB and have Set or List as query parameters. > As a workaround we use the "@Context UriInfo info" as parameter an read the parameter manually. As a downside this parameters are missing than in automated api generation with e.g. swagger. Without the @NotEmpty annotation it works fine. Without the generic type parameter ie just List it works fine. Making it a simple CDI bean makes it work fine. > This issue is caused by [commit - WFLY-9628 Allow to switch to Hibernate Validator 6.0 / Bean Validation 2.0|https://github.com/wildfly/wildfly/commit/02f230d91f55f86ee6cadf53832...] > Steps to reproduce: > {code:java} > @Stateless > @Path("/") > public class Resource { > @POST > @Path("put/list") > @Consumes(MediaType.APPLICATION_JSON) > public String putList(@NotEmpty List<String> a) { > return "Hello bars " + a.stream().collect(Collectors.joining(", ")); > } > } > {code} > {noformat} > [mkopecky@dhcp-10-40-5-71 bin]$ curl -d '["a","b","c"]' -H "Content-Type: application/json" -X POST http://localhost:8080/jaxrs-wf/put/list > javax.validation.ConstraintDeclarationException: HV000151: A method overriding another method must not redefine the parameter constraint configuration, but method Resource$$$view1#putList(List) redefines the configuration of Resource#putList(List). > [mkopecky@dhcp-10-40-5-71 bin]$ > {noformat} > {noformat} > javax.validation.ConstraintDeclarationException: HV000151: A method overriding another method must not redefine the parameter constraint configuration, but method Resource$$$view1#putList(List) redefines the configuration of Resource#putList(List). > at org.hibernate.validator.internal.metadata.aggregated.rule.OverridingMethodMustNotAlterParameterConstraints.apply(OverridingMethodMustNotAlterParameterConstraints.java:24) > at org.hibernate.validator.internal.metadata.aggregated.ExecutableMetaData$Builder.assertCorrectnessOfConfiguration(ExecutableMetaData.java:461) > at org.hibernate.validator.internal.metadata.aggregated.ExecutableMetaData$Builder.build(ExecutableMetaData.java:377) > at org.hibernate.validator.internal.metadata.aggregated.BeanMetaDataImpl$BuilderDelegate.build(BeanMetaDataImpl.java:788) > at org.hibernate.validator.internal.metadata.aggregated.BeanMetaDataImpl$BeanMetaDataBuilder.build(BeanMetaDataImpl.java:648) > at org.hibernate.validator.internal.metadata.BeanMetaDataManager.createBeanMetaData(BeanMetaDataManager.java:192) > at org.hibernate.validator.internal.metadata.BeanMetaDataManager.lambda$getBeanMetaData$0(BeanMetaDataManager.java:160) > at java.util.concurrent.ConcurrentMap.computeIfAbsent(ConcurrentMap.java:324) > at org.hibernate.validator.internal.metadata.BeanMetaDataManager.getBeanMetaData(BeanMetaDataManager.java:159) > at org.hibernate.validator.internal.engine.ValidationContext$ValidationContextBuilder.forValidateParameters(ValidationContext.java:619) > at org.hibernate.validator.internal.engine.ValidatorImpl.validateParameters(ValidatorImpl.java:254) > at org.hibernate.validator.internal.engine.ValidatorImpl.validateParameters(ValidatorImpl.java:224) > at org.jboss.resteasy.plugins.validation.GeneralValidatorImpl.validateAllParameters(GeneralValidatorImpl.java:177) > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:118) > at org.jboss.resteasy.core.ResourceMethodInvoker.internalInvokeOnTarget(ResourceMethodInvoker.java:509) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTargetAfterFilter(ResourceMethodInvoker.java:399) > at org.jboss.resteasy.core.ResourceMethodInvoker.lambda$invokeOnTarget$0(ResourceMethodInvoker.java:363) > at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:355) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:365) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:337) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:310) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:439) > at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:229) > at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:135) > at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:355) > at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:138) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:215) > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:791) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129) > at io.opentracing.contrib.jaxrs2.server.SpanFinishingFilter.doFilter(SpanFinishingFilter.java:55) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > {noformat} > Links: > * [forum|https://developer.jboss.org/thread/278822] > * WFLY-11566 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2651) [DMN Designer] i18n Expression Types in Navigator and grid screen title

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-2651?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-2651: ---------------------------------------- *_Decision Navigator_* https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-dmn/k... *_Grid screen title_* https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-dmn/k... Both places use {{ExpressionEditorDefinition.getName()}} that is i18n'ed. 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... 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... 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... > [DMN Designer] i18n Expression Types in Navigator and grid screen title > ----------------------------------------------------------------------- > > Key: DROOLS-2651 > URL: https://issues.redhat.com/browse/DROOLS-2651 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Fix For: 7.31.0.Final > > > -Both the Navigator (west dock) and the grid screen title (after https://issues.jboss.org/browse/DROOLS-2156) show the Expression's simple class name as the text. i18n both of these!- > The default names given to new nodes/node elements following https://issues.jboss.org/browse/DROOLS-2653 will also need to be i18n'ed to match. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1915) stronger credential store

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1915?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on ELY-1915: --------------------------------------- A while back I think [~dmlloyd] suggested we could back the credential store in a similar way to how we back our filesystem realm, that could be something to consider - if we were to do that we could have complete control of how the entries are encrypted. If we did that I would consider that we look at both symetric and asymetric encryption, one use case I think could be useful is: - # A DBA creates a new account with password for a server. # The DBA encrypts an entry in an agreed format using the public key of the server. # The entry is imported into the server's credential store. # The server loads the entry from the credential store using it's private key to decrypt. I have seen cases where users use multiple credential stores so one team providing credentials can not see the credentials provided by another team. Anyway that is a bit of a tangent but if we do look to increase the strength of the encryption I think reviewing the type of the encryption at the same time is worth considering. > stronger credential store > ------------------------- > > Key: ELY-1915 > URL: https://issues.redhat.com/browse/ELY-1915 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Credential Store > Affects Versions: 1.6.1.Final > Reporter: Hisanobu Okuda > Priority: Major > > JCEKS which is used for credential store uses 3DES. Need more stronger credential store based on a stronger cryptography like AES256 or more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2651) [DMN Designer] i18n Expression Types in Navigator and grid screen title

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-2651?page=com.atlassian.jira.plug... ] Michael Anstis resolved DROOLS-2651. ------------------------------------ Fix Version/s: 7.31.0.Final Resolution: Out of Date Both the Expression Type text in the Decision Navigator and grid screen title are i18n'ed. > [DMN Designer] i18n Expression Types in Navigator and grid screen title > ----------------------------------------------------------------------- > > Key: DROOLS-2651 > URL: https://issues.redhat.com/browse/DROOLS-2651 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Fix For: 7.31.0.Final > > > -Both the Navigator (west dock) and the grid screen title (after https://issues.jboss.org/browse/DROOLS-2156) show the Expression's simple class name as the text. i18n both of these!- > The default names given to new nodes/node elements following https://issues.jboss.org/browse/DROOLS-2653 will also need to be i18n'ed to match. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4777) Upgrade JBoss Remoting from 5.0.16 to 5.0.17

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFCORE-4777?page=com.atlassian.jira.plug... ] Flavia Rainone reassigned WFCORE-4777: -------------------------------------- Assignee: Flavia Rainone (was: Ilia Vassilev) > Upgrade JBoss Remoting from 5.0.16 to 5.0.17 > -------------------------------------------- > > Key: WFCORE-4777 > URL: https://issues.redhat.com/browse/WFCORE-4777 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Flavia Rainone > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4641) Running the Traffic Violation tutorial closing DMN editor Zoom toolbar persisted

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4641?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-4641: ----------------------------------- Story Points: 3 Sprint: 2019 Week 50-52 (from Dec 9) > Running the Traffic Violation tutorial closing DMN editor Zoom toolbar persisted > -------------------------------------------------------------------------------- > > Key: DROOLS-4641 > URL: https://issues.redhat.com/browse/DROOLS-4641 > Project: Drools > Issue Type: Bug > Components: Stunner > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: image-2019-10-11-11-16-50-339.png > > > As per title. Following the Traffic Violation tutorial. Closing the DMN editor. the Zoom bar persist on screen as per screenshot. > !image-2019-10-11-11-16-50-339.png|thumbnail! > Not sure this is the correct JIRA component, please move this JIRA as necessary -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019