November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4767) Fix error-popover position on simulation/background grids

by yamer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4767?page=com.atlassian.jira.plugi... ] yamer updated DROOLS-4767: -------------------------- Story Points: 5 (was: 3) > Fix error-popover position on simulation/background grids > --------------------------------------------------------- > > Key: DROOLS-4767 > URL: https://issues.jboss.org/browse/DROOLS-4767 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > When there is only one column on the grid, the popover is show to the left. But if there is not enough space to the left, the popover is not visible. > Proposed solution, for this situation, is to show the popover _below_ the cell. > If there is not space below, the the popover will be shown _above_. > The final position preference order will be (respect the cell): > RIGTH -> LEFT -> BELOW -> ABOVE > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4754) Background cell doesn't highlites if passed vallue to DRL returns scenario failure

by yamer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4754?page=com.atlassian.jira.plugi... ] yamer updated DROOLS-4754: -------------------------- Story Points: 3 > Background cell doesn't highlites if passed vallue to DRL returns scenario failure > ---------------------------------------------------------------------------------- > > Key: DROOLS-4754 > URL: https://issues.jboss.org/browse/DROOLS-4754 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus > Attachments: Traffic7442357700425429882.tar.xz > > > If the value in Background section made a scenario DRL to fall with exception then the scenario fails and alerts is viewing in alerts table, but the caused cell are not getting red. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4753) NPE shows in scesim editor when user runs imported scesim

by yamer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4753?page=com.atlassian.jira.plugi... ] yamer updated DROOLS-4753: -------------------------- Story Points: 1 > NPE shows in scesim editor when user runs imported scesim > --------------------------------------------------------- > > Key: DROOLS-4753 > URL: https://issues.jboss.org/browse/DROOLS-4753 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus > Attachments: Traffic7442357700425429882.tar.xz, image-2019-11-13-16-59-18-340.png > > > Unexpected exception throws if user runs test scenario that was previously imported s a scesim file. > !image-2019-11-13-16-59-18-340.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4753) NPE shows in scesim editor when user runs imported scesim

by yamer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4753?page=com.atlassian.jira.plugi... ] yamer reassigned DROOLS-4753: ----------------------------- Assignee: Anna Dupliak (was: Daniele Zonca) > NPE shows in scesim editor when user runs imported scesim > --------------------------------------------------------- > > Key: DROOLS-4753 > URL: https://issues.jboss.org/browse/DROOLS-4753 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Anna Dupliak > Assignee: Anna Dupliak > Priority: Major > Labels: CustomerFocus > Attachments: Traffic7442357700425429882.tar.xz, image-2019-11-13-16-59-18-340.png > > > Unexpected exception throws if user runs test scenario that was previously imported s a scesim file. > !image-2019-11-13-16-59-18-340.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4507) Ability to externally execute project defined tests.

by yamer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4507?page=com.atlassian.jira.plugi... ] yamer updated DROOLS-4507: -------------------------- Story Points: 1 (was: 5) > Ability to externally execute project defined tests. > ---------------------------------------------------- > > Key: DROOLS-4507 > URL: https://issues.jboss.org/browse/DROOLS-4507 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Paul Brown > Assignee: Daniele Zonca > Priority: Major > > Provide the ability to externally invoke project define tests scenario i.e via a rest api. > This is required in order for project defined tests to be reused and executed as part of a delivery pipeline and not from within business central. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12794) Elytron/JACC: Inconsistent EjbMethodPermissions

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-12794?page=com.atlassian.jira.plugin... ] Farah Juma updated WFLY-12794: ------------------------------ Priority: Critical (was: Major) > Elytron/JACC: Inconsistent EjbMethodPermissions > ----------------------------------------------- > > Key: WFLY-12794 > URL: https://issues.jboss.org/browse/WFLY-12794 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Affects Versions: 18.0.0.Final > Reporter: Ulf Brosziewski > Priority: Critical > Attachments: quickstart-ejb-sec.diff > > > When JACC is enabled in an elytron application domain, calling a secured ejb method that has an array parameter causes an EjbAccessException. > The reason for the failure is that the EjbMethodPermissions created by the EjbJaccConfigurator and the JaccInterceptor do not agree in the format of the type names for method parameters. According to the JACC specification and API documentation, names for array types should have the "canonical" form: component-type + "[]". The permission objects built by the JaccInterceptor conform to that, but the EjbJaccConfigurator builds them with type names obtained from a "MethodIdentifier", and these names have the internal format as returned by Class.getName(). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4698) Adding "expression" type handling for Collection type propereties

by uxdlc (Jira)

[ https://issues.jboss.org/browse/DROOLS-4698?page=com.atlassian.jira.plugi... ] uxdlc commented on DROOLS-4698: ------------------------------- [~yamer] [~danielezonca] If you need something from UX, please clone this jira to create a separate jira for UX with a description and some images if relevant. Thanks! > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4698 > URL: https://issues.jboss.org/browse/DROOLS-4698 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: yamer > Assignee: yamer > Priority: Major > Labels: UX, UXTeam > Fix For: 7.31.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4698) Adding "expression" type handling for Collection type propereties

by uxdlc (Jira)

[ https://issues.jboss.org/browse/DROOLS-4698?page=com.atlassian.jira.plugi... ] uxdlc updated DROOLS-4698: -------------------------- Labels: UX UXTeam (was: ) > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4698 > URL: https://issues.jboss.org/browse/DROOLS-4698 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: yamer > Assignee: yamer > Priority: Major > Labels: UX, UXTeam > Fix For: 7.31.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1944) [DMN Editor] Toolbox: Only one arrow for generic "connector". Type of connector depends on type of target node

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1944?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-1944: ----------------------------------- Priority: Minor (was: Major) > [DMN Editor] Toolbox: Only one arrow for generic "connector". Type of connector depends on type of target node > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1944 > URL: https://issues.jboss.org/browse/DROOLS-1944 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Daniel José dos Santos > Priority: Minor > Labels: drools-tools > > The "Toolbox" currently has a number of different "connector" icons; one for each type of connector that can emanate from the selected "source" node. [~tirelli] requested we have only one generic "connector" icon and the type of the created connector depends on the target node. This probably has an impact on the command being executed during drag move and drag complete. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12806) Upgrade to Wildfly 17, can't find persistence unit

by Emilio Cuberos (Jira)

[ https://issues.jboss.org/browse/WFLY-12806?page=com.atlassian.jira.plugin... ] Emilio Cuberos updated WFLY-12806: ---------------------------------- Description: Hi, Could you give us some advice? We upgraded from Java 8 / Wildfly 10, to Java 11 and Wildfly 17. Now the persistence units (attached persistence.xml) are no longer found: {code:java} Caused by: java.lang.IllegalArgumentException: WFLYWELD0037: Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named 'healthtrender-core' in deployment healthtrender-cloud-1.0.0.war for injection point private javax.persistence.EntityManager com.hemocue.cloud.repository.UserProfileRepository.em"}} {code} Here is an example of class where we inject a persistence-unit called "healthtrender-core" which is present in the persistence.xml: {code:java} package com.hemocue.cloud.repository; import com.hemocue.cloud.entity.user.Program; import javax.enterprise.context.Dependent; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; @Dependent public class ProgramRepository extends AbstractRepository<Program> { @PersistenceContext(unitName = "healthtrender-core") private EntityManager em; @Override EntityManager entityManager() { return em; } } {code} was: Hi, Could you give us some advice? We upgraded from Java 8 / Wildfly 10, to Java 11 and Wildfly 17. Now the persistence units (attached persistence.xml) are no longer found: {code:java} Caused by: java.lang.IllegalArgumentException: WFLYWELD0037: Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named 'healthtrender-core' in deployment healthtrender-cloud-1.0.0.war for injection point private javax.persistence.EntityManager com.hemocue.cloud.repository.UserProfileRepository.em"}} {code} Here is an example of class where we inject a persistence-unit called "healthtrender-core" which is present in the persistence.xml: {code:java} package com.hemocue.cloud.repository; import com.hemocue.cloud.entity.user.Program; import javax.enterprise.context.Dependent; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; /** * * @author Ivar Grimstad (ivar.grimstad(a)gmail.com) */ @Dependent public class ProgramRepository extends AbstractRepository<Program> { @PersistenceContext(unitName = "healthtrender-core") private EntityManager em; @Override EntityManager entityManager() { return em; } } {code} > Upgrade to Wildfly 17, can't find persistence unit > -------------------------------------------------- > > Key: WFLY-12806 > URL: https://issues.jboss.org/browse/WFLY-12806 > Project: WildFly > Issue Type: Bug > Reporter: Emilio Cuberos > Assignee: Brian Stansberry > Priority: Major > Attachments: persistence.xml > > > Hi, > Could you give us some advice? We upgraded from Java 8 / Wildfly 10, to Java 11 and Wildfly 17. > Now the persistence units (attached persistence.xml) are no longer found: > {code:java} > Caused by: java.lang.IllegalArgumentException: WFLYWELD0037: Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named 'healthtrender-core' in deployment healthtrender-cloud-1.0.0.war for injection point private javax.persistence.EntityManager com.hemocue.cloud.repository.UserProfileRepository.em"}} > {code} > Here is an example of class where we inject a persistence-unit called "healthtrender-core" which is present in the persistence.xml: > {code:java} > package com.hemocue.cloud.repository; > import com.hemocue.cloud.entity.user.Program; > import javax.enterprise.context.Dependent; > import javax.persistence.EntityManager; > import javax.persistence.PersistenceContext; > @Dependent > public class ProgramRepository extends AbstractRepository<Program> { > @PersistenceContext(unitName = "healthtrender-core") > private EntityManager em; > @Override > EntityManager entityManager() { > return em; > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

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