July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2535) Standalone Authoring - Project Explorer should show up

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2535?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2535: ----------------------------------- Sprint: 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29, 2018 Week 30-32 (was: 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29) > Standalone Authoring - Project Explorer should show up > ------------------------------------------------------ > > Key: DROOLS-2535 > URL: https://issues.jboss.org/browse/DROOLS-2535 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > When using the Workbench standalone the Project Explorer does not show up for kie-wb.war. It does work for kie-drools-wb.war -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2549) [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2549?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2549: ----------------------------------- Sprint: 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29, 2018 Week 30-32 (was: 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29) > [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase > ------------------------------------------------------------------- > > Key: DROOLS-2549 > URL: https://issues.jboss.org/browse/DROOLS-2549 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Fix For: 7.9.0.Final > > > {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes. > At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}). > Changes required for this JIRA (split into sub-tasks when work starts):- > * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller > * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children > * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/) > * When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}} (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2311) Drools Engine not able to load rules in spring-Boot project

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2311?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2311: ----------------------------------- Sprint: 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29, 2018 Week 30-32 (was: 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29) > Drools Engine not able to load rules in spring-Boot project > ----------------------------------------------------------- > > Key: DROOLS-2311 > URL: https://issues.jboss.org/browse/DROOLS-2311 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.5.0.Final > Reporter: Chandresh Mishra > Assignee: Mario Fusco > Attachments: Drools-Issue.rar > > > am using the Drools 7.5.0-final in the spring Boot project. > I am working on a multi-module Gradle project. Rules and kmodule.xml is present in the sub-module project. This module is packaged as a Jar inside a fat spring boot Jar file. > I am building the container from the classpath. > KieContainer kContainer = kieService.newKieClasspathContainer(); > on server start-up (java -jar) it loads the Kmodule.xml and prints all the kbase and sessionName. > But when I fire rules it returns zero rules fired. > It works fine when I run as spring boot app from Eclipse. Please help. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1825: ----------------------------------- Sprint: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29, 2018 Week 30-32 (was: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29) > [Guided Decision Table] Ability to change HIT policy in a decision table anytime > -------------------------------------------------------------------------------- > > Key: DROOLS-1825 > URL: https://issues.jboss.org/browse/DROOLS-1825 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Ivo Bek > Assignee: Toni Rikkola > Priority: Critical > Labels: UX, UXTeam > Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png, GDTAnalysis(a)2x.png, GDTColumns(a)2x.png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy. > Thus, it should be possible to change HIT policy in a decision table anytime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1946) DMN Editor

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1946?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1946: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29, 2018 Week 30-32 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29) > DMN Editor > ---------- > > Key: DROOLS-1946 > URL: https://issues.jboss.org/browse/DROOLS-1946 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: UX > Fix For: 7.9.0.Final > > > Place holder for all DMN Editor related activities -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2566) [DMN Editor] Integrate Editor into Workbench

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2566?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2566: ----------------------------------- Sprint: 2018 Week 27-29, 2018 Week 30-32 (was: 2018 Week 27-29) > [DMN Editor] Integrate Editor into Workbench > -------------------------------------------- > > Key: DROOLS-2566 > URL: https://issues.jboss.org/browse/DROOLS-2566 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > Following https://issues.jboss.org/browse/DROOLS-2565 we can integrate the DMN Editor into the Workbench - adding support to enable/disable the Editor (disabled by default). > h3. Acceptance test > - Able to open DMN file, validate, build and deploy project (/) > -- https://github.com/jboss-integration/bxms-qe-tests/pull/1595 > - Able to create new DMN file, save, validate, build and deploy project (/) > -- https://github.com/jboss-integration/bxms-qe-tests/pull/1595 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2748) [DMN Designer] Add permissions for DMN Designer

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2748?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2748: ----------------------------------- Sprint: 2018 Week 27-29, 2018 Week 30-32 (was: 2018 Week 27-29) > [DMN Designer] Add permissions for DMN Designer > ----------------------------------------------- > > Key: DROOLS-2748 > URL: https://issues.jboss.org/browse/DROOLS-2748 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > Access to the DMN Designer needs to be disabled by default and permissions added for Users to be able to enable, if required. See [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...] for a starting point! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10654) In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container.

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-10654?page=com.atlassian.jira.plugin... ] Bartosz Baranowski reassigned WFLY-10654: ----------------------------------------- Assignee: Chao Wang > In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container. > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10654 > URL: https://issues.jboss.org/browse/WFLY-10654 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 13.0.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > > Deployment(from management console) of a simple Jar file in EAP 7.1.x causes the ejb cache container to start , which should not be the case . > From EAP 7.1.x onwards @clustered annotation has been depricated and EJB application is required to start clustering , but in contradiction to this even if we deploy ant jar file (let's say ojdbc6.jar ) the container treats it as an EJB application and starts the EJB cache container as seen in the logs below : > ~~~~ > 1,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000078: Starting JGroups channel ejb > 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000078: Starting JGroups channel ejb > 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000078: Starting JGroups channel ejb > 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000078: Starting JGroups channel ejb > 22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia] > 22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia] > 22:14:21,676 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200] > 22:14:21,678 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200] > ~~~~ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10710) Wildfly keycloak and application configuration | how to resolve this error

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-10710?page=com.atlassian.jira.plugin... ] Bartosz Baranowski commented on WFLY-10710: ------------------------------------------- [~wildfly1] could you please attach reproducer? > Wildfly keycloak and application configuration | how to resolve this error > --------------------------------------------------------------------------- > > Key: WFLY-10710 > URL: https://issues.jboss.org/browse/WFLY-10710 > Project: WildFly > Issue Type: Bug > Environment: wildfly 11 final , > Reporter: Lilly rose > Assignee: Jason Greene > > ESC[0mESC[31m16:36:59,379 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /sample/: java.lang.NullPointerException > at java.lang.String.contains(String.java:2133) > at org.keycloak.adapters.saml.elytron.KeycloakHttpServerAuthenticationMechanism.evaluateRequest(KeycloakHttpServerAuthenticationMechanism.java:82) > at org.wildfly.security.http.util.SetMechanismInformationMechanismFactory$1.evaluateRequest(SetMechanismInformationMechanismFactory.java:114) > at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$1.evaluateRequest(SecurityIdentityServerMechanismFactory.java:77) > at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticate(HttpAuthenticator.java:115) > at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.access$100(HttpAuthenticator.java:94) > at org.wildfly.security.http.HttpAuthenticator.authenticate(HttpAuthenticator.java:78) > at org.wildfly.elytron.web.undertow.server.SecurityContextImpl.authenticate(SecurityContextImpl.java:100) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) > 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.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) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2769) callback methods for: before/after invoke BKM/DS

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2769: -------------------------------------- Summary: callback methods for: before/after invoke BKM/DS Key: DROOLS-2769 URL: https://issues.jboss.org/browse/DROOLS-2769 Project: Drools Issue Type: Feature Request Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Priority: Minor {quote}As part of another feature, I would like to create callback methods for both "before/after invoke BKM/DS", so that we can report on actual execution of BKMs and Decision Services. But this is a conversation for another day.{quote} Ref https://github.com/kiegroup/drools/pull/1986#discussion_r204029977 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 July 2018