March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-437) Add config option to fail deployment if private API is used

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-437?page=com.atlassian.jira.plugin... ] Tomaz Cerar reassigned WFCORE-437: ---------------------------------- Assignee: (was: Tomaz Cerar) > Add config option to fail deployment if private API is used > ----------------------------------------------------------- > > Key: WFCORE-437 > URL: https://issues.jboss.org/browse/WFCORE-437 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Pete Muir > > This would allow users to have continuous integration jobs check if their app uses a private API by mistake, and have the job fail if it does. > Needed to automate the check that quickstarts only use public API. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1500) DecisionTable single output typeRef inference

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1500: -------------------------------------- Summary: DecisionTable single output typeRef inference Key: DROOLS-1500 URL: https://issues.jboss.org/browse/DROOLS-1500 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari As for the example below, the low priority value is Referred, so the correct answer should be Declined: {code:xml} <?xml version="1.0" encoding="UTF-8" standalone="no"?> <semantic:definitions xmlns:semantic="http://www.omg.org/spec/DMN/20151101/dmn.xsd" xmlns="http://www.trisotech.com/definitions/_ff54a44d-b8f5-48fc-b2b7-43db767e8a1c" xmlns:feel="http://www.omg.org/spec/FEEL/20140401" xmlns:triso="http://www.trisotech.com/2015/triso/modeling" xmlns:trisofeed="http://trisotech.com/feed" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" exporter="DMN Modeler" exporterVersion="5.1.8.1" id="_ff54a44d-b8f5-48fc-b2b7-43db767e8a1c" name="not quite all or nothing P" namespace="http://www.trisotech.com/definitions/_ff54a44d-b8f5-48fc-b2b7-43db767e8a1c" triso:logoChoice="Default"> <semantic:extensionElements/> <semantic:itemDefinition label="tRiskCategory" name="tRiskCategory"> <semantic:typeRef>feel:string</semantic:typeRef> <semantic:allowedValues triso:constraintsType="enumeration"> <semantic:text>"High","Low","Medium"</semantic:text> </semantic:allowedValues> </semantic:itemDefinition> <semantic:itemDefinition label="tApprovalStatus" name="tApprovalStatus"> <semantic:typeRef>feel:string</semantic:typeRef> <semantic:allowedValues triso:constraintsType="enumeration"> <semantic:text>"Approved","Declined","Referred"</semantic:text> </semantic:allowedValues> </semantic:itemDefinition> <semantic:decision id="_3b2953a3-745f-4d2e-b55d-75c8c5ae653c" name="Approval Status" triso:displayName="Approval Status"> <semantic:variable id="_7fe30427-4140-4e53-a070-2ecfc723d82b" name="Approval Status" typeRef="tApprovalStatus"/> <semantic:informationRequirement> <semantic:requiredDecision href="#_5a4bdb64-f0ef-4978-9e03-6f1ae64a1f17"/> </semantic:informationRequirement> <semantic:informationRequirement> <semantic:requiredInput href="#_8ff18665-84e9-49f2-a8df-8981b1844549"/> </semantic:informationRequirement> <semantic:decisionTable hitPolicy="PRIORITY" id="_c98573c0-08b5-4bc3-baf1-3b065fedf1d1" outputLabel="Approval Status"> <semantic:input id="_0524c2a9-a223-425a-988f-72d39eed9714" label="isAffordable"> <semantic:inputExpression typeRef="feel:boolean"> <semantic:text>isAffordable</semantic:text> </semantic:inputExpression> </semantic:input> <semantic:input id="_705b772e-6ac9-4c09-ace8-5165438454d9" label="RiskCategory"> <semantic:inputExpression typeRef="tRiskCategory"> <semantic:text>RiskCategory</semantic:text> </semantic:inputExpression> </semantic:input> <semantic:output id="_704c6117-4670-4d2f-865e-a4d973db5e9f" /> <semantic:rule id="_c9dd9401-69a6-4da7-bd70-22e062addf06"> <semantic:inputEntry id="_8ba69e42-c77b-4be4-b566-3385fada3a7a"> <semantic:text>true</semantic:text> </semantic:inputEntry> <semantic:inputEntry id="_4f356526-fe33-4e2d-9aab-837ad962ee43"> <semantic:text>"Low"</semantic:text> </semantic:inputEntry> <semantic:outputEntry id="_9b79d813-37cb-4e67-9207-139a00802f39"> <semantic:text>"Approved"</semantic:text> </semantic:outputEntry> </semantic:rule> <semantic:rule id="_4fb0af5e-d777-42ee-a886-c0e31ab3fc31"> <semantic:inputEntry id="_a321bd86-943a-46d4-9eb4-3d68415e695c"> <semantic:text>-</semantic:text> </semantic:inputEntry> <semantic:inputEntry id="_73262932-7275-47e3-9684-91cf5c336af2"> <semantic:text>"Medium"</semantic:text> </semantic:inputEntry> <semantic:outputEntry id="_bdda5b02-fcc6-4a14-b668-c612b654c818"> <semantic:text>"Referred"</semantic:text> </semantic:outputEntry> </semantic:rule> <semantic:rule id="_789b4b82-6bf6-4040-86bc-9237c41b37be"> <semantic:inputEntry id="_9de5765c-f427-4df0-af9f-67a074f9f31f"> <semantic:text>true</semantic:text> </semantic:inputEntry> <semantic:inputEntry id="_bc4319a2-f954-4fe6-a708-49de2a1c051d"> <semantic:text>"High"</semantic:text> </semantic:inputEntry> <semantic:outputEntry id="_7330db40-ec90-4c0e-8989-798251da2187"> <semantic:text>"Declined"</semantic:text> </semantic:outputEntry> </semantic:rule> <semantic:rule id="_a9f2bdca-8e42-4d79-862a-44a027e2b536"> <semantic:inputEntry id="_23b70497-fee9-4dfb-ae24-93f672d9f1d7"> <semantic:text>false</semantic:text> </semantic:inputEntry> <semantic:inputEntry id="_ce7b70c5-b5d2-48a5-9fa9-5ac865092945"> <semantic:text>-</semantic:text> </semantic:inputEntry> <semantic:outputEntry id="_fa497253-0356-4234-9774-2e3d95c171d2"> <semantic:text>"Declined"</semantic:text> </semantic:outputEntry> </semantic:rule> </semantic:decisionTable> </semantic:decision> <semantic:decision id="_5a4bdb64-f0ef-4978-9e03-6f1ae64a1f17" name="RiskCategory" triso:displayName="RiskCategory"> <semantic:variable id="_542fe70e-5c8e-4f30-bec7-ad19a792cfaf" name="RiskCategory" typeRef="tRiskCategory"/> </semantic:decision> <semantic:inputData id="_8ff18665-84e9-49f2-a8df-8981b1844549" name="isAffordable" triso:displayName="isAffordable"> <semantic:variable id="_65f460e7-7bcb-419a-93c2-36b26b95273e" name="isAffordable" typeRef="feel:boolean"/> </semantic:inputData> </semantic:definitions> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2588) Deprecate optional dependencies in manifests and descriptors

by Richard Opalka (JIRA)

Richard Opalka created WFCORE-2588: -------------------------------------- Summary: Deprecate optional dependencies in manifests and descriptors Key: WFCORE-2588 URL: https://issues.jboss.org/browse/WFCORE-2588 Project: WildFly Core Issue Type: Enhancement Affects Versions: 3.0.0.Beta11 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 3.0.0.Beta12 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7361) data-source attribute should not be an attribute of all JGroups protocols

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7361?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-7361. ------------------------------ Resolution: Done This was completed as part of https://issues.jboss.org/browse/WFLY-7882 > data-source attribute should not be an attribute of all JGroups protocols > ------------------------------------------------------------------------- > > Key: WFLY-7361 > URL: https://issues.jboss.org/browse/WFLY-7361 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > We should create a custom JDBCProtocolResourceDefinition that extends ProtocolResourceDefinition that adds a data-source attribute and capability reference. > This can be registered separately from the generic protocol resource definition. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-470) Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest))

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-470?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-470: ------------------------------------------ Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta8) > Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest)) > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-470 > URL: https://issues.jboss.org/browse/DROOLS-470 > Project: Drools > Issue Type: Enhancement > Components: decision tables > Affects Versions: 6.1.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Michael Anstis > Labels: optaplanner-request-for-drools > Fix For: 7.0.0.CR1 > > > This DT should work: > ||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation(isNeighborOf($guest))|| > |guestName == "$param"|guestName == "$param"|doSomething();| > It crashes because of the "SeatDesignation(isNeighborOf($guest))". Only empty parenthesis are allowed. > Failing workaround 1: This workaround (as specified by the docs), does NOT work well, because it adds the same condition (isNeighborOf($guest)) multiple times in the same rule: > ||CONDITION||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation()||| > |guestName == "$param"|isNeighborOf($guest), guestName == "$param"|isNeighborOf($guest), guestAge == "$param"|doSomething();| > Failing workaround 2: Adding an extra, hidden column with that condition does not work when new rows are added because condition columns with an empty cell are ignored. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-453) Allow KieSession globals configurable via kmodule.xml

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-453?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-453: ------------------------------------------ Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta8) > Allow KieSession globals configurable via kmodule.xml > ----------------------------------------------------- > > Key: DROOLS-453 > URL: https://issues.jboss.org/browse/DROOLS-453 > Project: Drools > Issue Type: Enhancement > Affects Versions: 6.0.0.Final > Reporter: Anton Giertli > Assignee: Mark Proctor > Fix For: 7.0.0.CR1 > > > Looking at the current xsd of kmodule.xml > https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/6.0.x/kie-api/src... > It is not possible to configure KieSession globals variables via kmodule.xml. > Given the fact it is already possible to configure almost every KieSession related features like listeners, handlers, loggers, globals, also session related, should be configurable through the kmodule.xml too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-817) Extremely poor performance of the topological sorting implementation for type declarations performs

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-817?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-817: ------------------------------------------ Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta8) > Extremely poor performance of the topological sorting implementation for type declarations performs > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-817 > URL: https://issues.jboss.org/browse/DROOLS-817 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.Final, 6.3.0.Beta1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Minor > Fix For: 7.0.0.CR1 > > > The current implementation suffers from thrashing. > In case of large business object models (e.g. derived from an ontology), > the analysis at package build time may take orders of magnitude more > than necessary -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1419) Make interface AccumulateFunction<S extends Serializable> to avoid downcasting verbosity in implementations

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1419?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-1419: ------------------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta8) > Make interface AccumulateFunction<S extends Serializable> to avoid downcasting verbosity in implementations > ----------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1419 > URL: https://issues.jboss.org/browse/DROOLS-1419 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 6.5.0.Final > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Minor > Fix For: 7.0.0.CR1 > > > Fix will NOT break backwards compatibility. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-744) Rule Generation Feature Request

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-744?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-744: ------------------------------------------ Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta8) > Rule Generation Feature Request > ------------------------------- > > Key: DROOLS-744 > URL: https://issues.jboss.org/browse/DROOLS-744 > Project: Drools > Issue Type: Feature Request > Components: core engine, kie server > Affects Versions: 6.2.0.Final > Reporter: Justin Holmes > Assignee: Mario Fusco > Fix For: 7.0.0.CR1 > > > As a developer using Drools, I want a rule generation java api that supports control logic in the rule templates (e.g. for loops, if/else) and integrates with the rule workbench in order to build highly dynamic business rules driven systems. > The initial thought process around implementation is to build two things 1) a simple way to author mvel templates in business central, the existing text editor could be used at first and 2) a simple embedded java api in it's own maven module which can checkout the git project that has the mvel template, apply a set of domain objects to the template, check in the resulting rule files to the local git repo and then push the changes back to business central. This allows us to leverage the power of the existing MVEL and JGit tech stack while pushing the complexity to a java api, where we are stronger than the workbench itself. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-680) "contains" operator behaves inconsistently when used with Maps

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-680?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-680: ------------------------------------------ Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta8) > "contains" operator behaves inconsistently when used with Maps > -------------------------------------------------------------- > > Key: DROOLS-680 > URL: https://issues.jboss.org/browse/DROOLS-680 > Project: Drools > Issue Type: Bug > Affects Versions: 5.6.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4 > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 7.0.0.CR1 > > > In a rule > {code} > Bean( map contains "x" ) // assuming "map" is a property of type Map > {code} > "contains" is arbitrarily interpreted as "containsKey" > The constrain will then fail after being jitted > The documentation explicitly states that "contains" applies to collections -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017