March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3094) Create a Verifier backend adapter for DMN tables

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-3094?page=com.atlassian.jira.plug... ] Toni Rikkola resolved DROOLS-3094. ---------------------------------- Resolution: Done > Create a Verifier backend adapter for DMN tables > ------------------------------------------------ > > Key: DROOLS-3094 > URL: https://issues.redhat.com/browse/DROOLS-3094 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Optional > Labels: drools-tools, verifier > > The goal is to make it possible to run the DMN Validation using the DMN backend validate-method. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5203) Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-5203: ------------------------------------ Summary: Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows Key: DROOLS-5203 URL: https://issues.redhat.com/browse/DROOLS-5203 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2845) Extend the existing verifier to support DMN tables

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-2845?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-2845: --------------------------------- Description: h1. Goal Merge the Validation methods DMN has with the generic Validator that is used by the GDST. was: h1. Goal Reuse the V&V created for Guided Decision Tables on the DMN tables. h1. Workload divided to steps I propose the work goes in the following steps. After each step I should be able to merge into master. Steps: # Move Verifier core to kie-wb-common # Move V&V reporting UI to kie-wb-common # Make the web worker connector reusable for different V&V types # -Make a servlet module for DMN that allows the download of the Web Worker.- # Create an adapter for DMN tables # Add support for ranges ( these are given in DMN so no need to use JSR303 ) # Duplicate i18n of the V&V for DMN or unify the reports so that the terms make sense The workload has changed. Now the goal is to reuse the DRL V&V codes in the existing DMN Codes. This means most of the work done for this ticket has no effect and the goal is to adjust to existing DMN V&V reporting, not the other way around. > Extend the existing verifier to support DMN tables > -------------------------------------------------- > > Key: DROOLS-2845 > URL: https://issues.redhat.com/browse/DROOLS-2845 > Project: Drools > Issue Type: Epic > Components: DMN Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Optional > Labels: UX, drools-tools, verifier > > h1. Goal > Merge the Validation methods DMN has with the generic Validator that is used by the GDST. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13304) JwtActivationProcessor throws NPE when LoginConfig#realmName not declared

by Michael Edgar (Jira)

Michael Edgar created WFLY-13304: ------------------------------------ Summary: JwtActivationProcessor throws NPE when LoginConfig#realmName not declared Key: WFLY-13304 URL: https://issues.redhat.com/browse/WFLY-13304 Project: WildFly Issue Type: Bug Components: MP JWT Affects Versions: 19.0.0.Final Reporter: Michael Edgar Assignee: Darran Lofthouse When starting a Microprofile application utilizing the {{org.eclipse.microprofile.auth.LoginConfig}} annotation, a {{NullPointerException}} is thrown if the annotation does not declare the {{realmName}} property. {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) {} MSC000001: Failed to start service jboss.deployment.unit."example.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."example.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "example.war" at org.jboss.as.server@11.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183) at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException at org.wildfly.extension.microprofile.jwt-smallrye@19.0.0.Final//org.wildfly.extension.microprofile.jwt.smallrye.JwtActivationProcessor.deploy(JwtActivationProcessor.java:80) at org.jboss.as.server@11.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176) ... 8 more {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13303) Upgrade Hibernate ORM from 5.3.15 to 5.3.16

by Ingo Weiss (Jira)

Ingo Weiss created WFLY-13303: --------------------------------- Summary: Upgrade Hibernate ORM from 5.3.15 to 5.3.16 Key: WFLY-13303 URL: https://issues.redhat.com/browse/WFLY-13303 Project: WildFly Issue Type: Component Upgrade Components: JPA / Hibernate Affects Versions: 19.0.0.Final Reporter: Ingo Weiss Assignee: Scott Marlow Fix For: 20.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13295) REST-AT inbound bridge is not activated for EJB without TransactionalManagement annotation

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-13295?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka commented on WFLY-13295: ----------------------------------------- Yes. The WildFly will include the test to check that the simple EJB without other annotations ({{@TransactionAttribute}} in particular) will be enabling the inbound rts bridge. (the test is here https://github.com/ochaloup/wildfly/commit/c282cb5ebcaad776719e9ea236b791...) > REST-AT inbound bridge is not activated for EJB without TransactionalManagement annotation > ------------------------------------------------------------------------------------------ > > Key: WFLY-13295 > URL: https://issues.redhat.com/browse/WFLY-13295 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 19.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The REST-AT inbound bridge is activated per deployment. It's activated for a deployment which contains a REST endpoint identified with `@Path` annotation where in the same class has to be included either annotation `@Transactional` or `@TransactionAttribute`. > The point is to activate the inbound bridge for deployments which contain a transactional managed method (CDI or EJB) which can receive the txn context, ie. possibly a context of REST-AT transaction as well. > The issue is that EJB beans are transactional by default. The EJB bean class does not need to specify any `@TransactionalAttribute` to be already container managed (from txn perspective) with attribute `REQUIRED`. Which means taking incoming txn context and will work with it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5202) Document Drools runtime commands

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-5202: ------------------------------------------ Summary: Document Drools runtime commands Key: DROOLS-5202 URL: https://issues.redhat.com/browse/DROOLS-5202 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5202) Document Drools runtime commands

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5202?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-5202: --------------------------------------- Sprint: 2020 Week 13-15 (from Mar 23) > Document Drools runtime commands > --------------------------------- > > Key: DROOLS-5202 > URL: https://issues.redhat.com/browse/DROOLS-5202 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4916) Wrongly parse method chain in modify block in executable model

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4916?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4916: -------------------------------------- Summary: Wrongly parse method chain in modify block in executable model (was: Investigate modify parsing bug in executable model) > Wrongly parse method chain in modify block in executable model > -------------------------------------------------------------- > > Key: DROOLS-4916 > URL: https://issues.redhat.com/browse/DROOLS-4916 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Toshiya Kobayashi > Priority: Major > Labels: good-first-issue > > {noformat} > declare Application > categories : Set = new HashSet() > end > {noformat} > Then I had a modify statement scattered about: > {noformat} > modify ($a) { > $a.getCategories().add("hello"); > } > {noformat} > The ExecutableModel did not seem to like any of those. I changed it to: > {noformat} > $a.getCategories().add("hello"); > update($a); > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4761) Move kie-remote and hacep module into droolsjbpm-integration

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4761?page=com.atlassian.jira.plug... ] Massimiliano Dessi commented on DROOLS-4761: -------------------------------------------- https://github.com/kiegroup/droolsjbpm-integration/pull/2040 > Move kie-remote and hacep module into droolsjbpm-integration > ------------------------------------------------------------ > > Key: DROOLS-4761 > URL: https://issues.redhat.com/browse/DROOLS-4761 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 March 2020