November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11430) tasks-rs: Add to README a instruction to comment an import line

by Sande Gilda (Jira)

[ https://issues.jboss.org/browse/WFLY-11430?page=com.atlassian.jira.plugin... ] Sande Gilda closed WFLY-11430. ------------------------------ Resolution: Cannot Reproduce Closing this issue as it is a not a quickstart bug. It is a bug that needs to be fixed in the internal QE tests > tasks-rs: Add to README a instruction to comment an import line > ---------------------------------------------------------------- > > Key: WFLY-11430 > URL: https://issues.jboss.org/browse/WFLY-11430 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Sande Gilda > Priority: Major > > The issue is in _EnableJsonSupport_ Manu framework unit. The description below is no more relevant. > -Currently maven checkstyle plugin [fails|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-...] on unused import after adding JSON support to the tasks-rs quickstart- > {noformat} > tasks-rs/src/main/java/org/jboss/as/quickstarts/tasksrs/service/TaskResource.java:30:8: Unused import - javax.ws.rs.Produces. [UnusedImports] > {noformat} > -Our QE tests are fixed now, but for the customers it would be useful to have an instruction to comment the line- > {noformat} > import javax.ws.rs.Produces > {noformat} > -It would be nice to have this instruction in Modify this Quickstart to Support JSON Representations of Tasks section, step 3, Add comments to this line sentence-. > -Thanks!- -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3382) [DMN Designer] Decision Navigator - The focus feature does not work in the "Overview" tab

by Guilherme Carreiro (Jira)

Guilherme Carreiro created DROOLS-3382: ------------------------------------------ Summary: [DMN Designer] Decision Navigator - The focus feature does not work in the "Overview" tab Key: DROOLS-3382 URL: https://issues.jboss.org/browse/DROOLS-3382 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Guilherme Carreiro Assignee: Guilherme Carreiro Attachments: bug.gif The focus feature does not work in the "Overview" tab. See the steps to reproduce: !bug.gif|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3364) Remove from scenario editor Data Objects tab if user is testing DMN

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3364?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3364: --------------------------------------- I think it is better to remove it at all for now when the scesim is for a DMN model. If I remember correctly [~manstis] (or maybe [~karreiro]) is going to create for DMN Editor a "Data Objects" tab equivalent to show/edit data objects so in the future maybe we can reuse the same (in "read only" mode) but for now remove is enough > Remove from scenario editor Data Objects tab if user is testing DMN > ------------------------------------------------------------------- > > Key: DROOLS-3364 > URL: https://issues.jboss.org/browse/DROOLS-3364 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Toni Rikkola > Priority: Major > Labels: ScenarioSimulation > > Data object tab should not be available if the scesim has been created for DMN testing -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2911) Update Scenario Simulation command to use the new module

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-2911?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-2911. ------------------------------------ > Update Scenario Simulation command to use the new module > -------------------------------------------------------- > > Key: DROOLS-2911 > URL: https://issues.jboss.org/browse/DROOLS-2911 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > > Use new kie-wb-common-command-api for Scenario Simulation commands > *Specs:* > Preliminary steps: > * Add dependency to the new module containing AbstractCommand > * Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events > * Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model) > * Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command > Move to common API: > * Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl > * Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand > * Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*) > * Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl > * Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11430) tasks-rs: Add to README a instruction to comment an import line

by Sultan Zhantemirov (Jira)

[ https://issues.jboss.org/browse/WFLY-11430?page=com.atlassian.jira.plugin... ] Sultan Zhantemirov updated WFLY-11430: -------------------------------------- Description: The issue is in _EnableJsonSupport_ Manu framework unit. The description below is no more relevant. -Currently maven checkstyle plugin [fails|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-...] on unused import after adding JSON support to the tasks-rs quickstart- {noformat} tasks-rs/src/main/java/org/jboss/as/quickstarts/tasksrs/service/TaskResource.java:30:8: Unused import - javax.ws.rs.Produces. [UnusedImports] {noformat} -Our QE tests are fixed now, but for the customers it would be useful to have an instruction to comment the line- {noformat} import javax.ws.rs.Produces {noformat} -It would be nice to have this instruction in Modify this Quickstart to Support JSON Representations of Tasks section, step 3, Add comments to this line sentence-. -Thanks!- was: Currently maven checkstyle plugin [fails|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-...] on unused import after adding JSON support to the tasks-rs quickstart: {noformat} tasks-rs/src/main/java/org/jboss/as/quickstarts/tasksrs/service/TaskResource.java:30:8: Unused import - javax.ws.rs.Produces. [UnusedImports] {noformat} Our QE tests are fixed now, but for the customers it would be useful to have an instruction to comment the line {noformat} import javax.ws.rs.Produces {noformat} in _tasks-rs/src/main/java/org/jboss/as/quickstarts/tasksrs/service/TaskResource.java_ file, line 30. Ii would be nice to have this instruction in _Modify this Quickstart to Support JSON Representations of Tasks_ section, step 3, _Add comments to this line_ sentence. Thanks! > tasks-rs: Add to README a instruction to comment an import line > ---------------------------------------------------------------- > > Key: WFLY-11430 > URL: https://issues.jboss.org/browse/WFLY-11430 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Sande Gilda > Priority: Major > > The issue is in _EnableJsonSupport_ Manu framework unit. The description below is no more relevant. > -Currently maven checkstyle plugin [fails|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-...] on unused import after adding JSON support to the tasks-rs quickstart- > {noformat} > tasks-rs/src/main/java/org/jboss/as/quickstarts/tasksrs/service/TaskResource.java:30:8: Unused import - javax.ws.rs.Produces. [UnusedImports] > {noformat} > -Our QE tests are fixed now, but for the customers it would be useful to have an instruction to comment the line- > {noformat} > import javax.ws.rs.Produces > {noformat} > -It would be nice to have this instruction in Modify this Quickstart to Support JSON Representations of Tasks section, step 3, Add comments to this line sentence-. > -Thanks!- -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3372) [DMN Designer] Add support for marshalling of Decision Services

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3372?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3372: ----------------------------------- Sprint: 2018 Week 48-50 > [DMN Designer] Add support for marshalling of Decision Services > --------------------------------------------------------------- > > Key: DROOLS-3372 > URL: https://issues.jboss.org/browse/DROOLS-3372 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Michael Anstis > Assignee: Matteo Mortari > Priority: Major > Labels: drools-tools > > Following https://issues.jboss.org/browse/DROOLS-3371 we need to support marshalling of the Decision Service UI model to and from the DMN model. Thus loading and saving of models containing Decision Services will be possible! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3381) [DMN Designer] Do not add Header to nested ContextGrid

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3381: -------------------------------------- Summary: [DMN Designer] Do not add Header to nested ContextGrid Key: DROOLS-3381 URL: https://issues.jboss.org/browse/DROOLS-3381 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.15.0.Final Reporter: Michael Anstis Assignee: Michael Anstis During the work [~jomarko] is doing for [DROOLS-2932|https://issues.jboss.org/browse/DROOLS-2932] it became apparent that _hiding_ the {{Header}} for a _nested_ {{ContextGrid}} is wrong; as it allows keyboard navigation into the (invisible) {{Header}}. We should not add a {{Header}} at all for _nested_ {{ContextGrid}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11340) Tests in org.jboss.as.test.integration.microprofile.opentracing failing with security manager

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFLY-11340?page=com.atlassian.jira.plugin... ] Jan Stourac commented on WFLY-11340: ------------------------------------ Thank you, [~jamezp]. I have reviewed the MR and it looks good! Regarding to the privileged parts of code. I am not sure I have enough context here. Will you create those component jiras by yourself, or do you want me to create them myself? > Tests in org.jboss.as.test.integration.microprofile.opentracing failing with security manager > --------------------------------------------------------------------------------------------- > > Key: WFLY-11340 > URL: https://issues.jboss.org/browse/WFLY-11340 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing, Test Suite > Affects Versions: 14.0.0.Final > Reporter: Martin Choma > Assignee: Jan Stourac > Priority: Major > Labels: security-manager > > These tests fail with security manager from package org.jboss.as.test.integration.microprofile.opentracing > * ResourceNotTracedTestCase.notTracedEndpointYieldsNoSpans > * ResourceTracedTestCase.tracedEndpointYieldsSpan > * ResourceWithCDITestCase.tracedEndpointYieldsSpan > * ResourceWithCustomOperationNameBeanTestCase.customOperationName > * SimpleRestClientTestCase.clientRequestSpanJoinsServer > {noformat} > java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "modifyThread")" in code source "(vfs:/content/3f3aff01-8e62-42e9-81c0-022f693ec7e0.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.3f3aff01-8e62-42e9-81c0-022f693ec7e0.war" from Service Module Loader") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:294) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:191) > at java.util.concurrent.ThreadPoolExecutor.checkShutdownAccess(ThreadPoolExecutor.java:742) > at java.util.concurrent.ThreadPoolExecutor.shutdownNow(ThreadPoolExecutor.java:1429) > at java.util.concurrent.Executors$DelegatedExecutorService.shutdownNow(Executors.java:670) > at org.jboss.as.test.integration.common.HttpRequest.execute(HttpRequest.java:63) > at org.jboss.as.test.integration.common.HttpRequest.get(HttpRequest.java:82) > at org.jboss.as.test.integration.microprofile.opentracing.ResourceNotTracedTestCase.performCall(ResourceNotTracedTestCase.java:63) > at org.jboss.as.test.integration.microprofile.opentracing.ResourceNotTracedTestCase.notTracedEndpointYieldsNoSpans(ResourceNotTracedTestCase.java:57) > {noformat} > As stacktrace is from test side and tests are missing @RunAsClient, I believe tests are running in container. [~juraci.costa] is this really intent tests are missing @RunAsClient annotation? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10638) Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-10638?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-10638: ------------------------------------- new jira is [WFLY-11436] > Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments > ------------------------------------------------------------------------------------------ > > Key: WFLY-10638 > URL: https://issues.jboss.org/browse/WFLY-10638 > Project: WildFly > Issue Type: Task > Components: Clustering, JPA / Hibernate > Affects Versions: 13.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 15.0.0.Beta1 > > > Currently, during deployment of ORM 5.3.* applications, the following warning is logged in the server console, four times per persistence unit. It should not appear at all. > {quote} > HHH025030: Transactional caches are not supported. The configuration option will be ignored; please unset. > {quote} > The warning comes from ORM 5.3 integration code org.infinispan.hibernate.cache.v53.InfinispanRegionFactory#unsetTransactions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11436) Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11436?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11436: -------------------------------- Fix Version/s: 16.0.0.Beta1 (was: 15.0.0.Beta1) > Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments > ------------------------------------------------------------------------------------------ > > Key: WFLY-11436 > URL: https://issues.jboss.org/browse/WFLY-11436 > Project: WildFly > Issue Type: Task > Components: Clustering, JPA / Hibernate > Affects Versions: 13.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 16.0.0.Beta1 > > > Currently, during deployment of ORM 5.3.* applications, the following warning is logged in the server console, four times per persistence unit. It should not appear at all. > {quote} > HHH025030: Transactional caches are not supported. The configuration option will be ignored; please unset. > {quote} > The warning comes from ORM 5.3 integration code org.infinispan.hibernate.cache.v53.InfinispanRegionFactory#unsetTransactions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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