July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-1663: --------------------------------------- Thank you for opening the ticket. I will look into it. Just to clarify: the DMN engine is not the same as the core engine. The DMN engine does not have an agenda. When a DMN service is invoked, the requirements are resolved and executed in the proper order, but there is no agenda. > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Edson Tirelli > Fix For: 7.2.0.Final > > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1663: ---------------------------------- Fix Version/s: 7.2.0.Final > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Edson Tirelli > Fix For: 7.2.0.Final > > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1663: ---------------------------------- Issue Type: Enhancement (was: Bug) > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Edson Tirelli > Fix For: 7.2.0.Final > > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9085) Upgrade Narayana to 5.5.28.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-9085?page=com.atlassian.jira.plugin.... ] Tom Jenkinson moved JBEAP-12133 to WFLY-9085: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9085 (was: JBEAP-12133) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Transactions (was: Transactions) > Upgrade Narayana to 5.5.28.Final > -------------------------------- > > Key: WFLY-9085 > URL: https://issues.jboss.org/browse/WFLY-9085 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Alexandros Koufoudakis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Alexandros Koufoudakis edited comment on DROOLS-1663 at 7/14/17 6:33 AM: ------------------------------------------------------------------------- A small clarification needed. Currently, DMN specification supports the following "types" of import: - DMN Import - import of decisions, BKMs, item definitions, etc. - XML Import - import of data tables defined in other XML files - XSD Import - import of XSD type definitions. This is stated in the "DMN Method and Style", B. Silver. Please, check the attached pages. !IMG_2197.jpg|thumbnail! !IMG_2198.jpg|thumbnail! !IMG_2199.jpg|thumbnail! The specification, however, does not mention any specific type (DMN, XML, XSD). Of course, you can find combination of words "XSD import" here and there in the Specs, but, again, as I said, there's nothing specific about what you can exactly import. Should we focus on DMN import only for the "beginning"? was (Author: akoufoudakis): A small clarification. Currently, DMN specification supports the following "types" of import: - DMN Import - import of decisions, BKMs, item definitions, etc. - XML Import - import of data tables defined in other XML files - XSD Import - import of XSD type definitions. This is stated in the "DMN Method and Style", B. Silver. Please, check the attached pages. !IMG_2197.jpg|thumbnail! !IMG_2198.jpg|thumbnail! !IMG_2199.jpg|thumbnail! The specification, however, does not mention any specific type (DMN, XML, XSD). Of course, you can find combination of words "XSD import" here and there in the Specs, but, again, as I said, there's nothing specific about what you can exactly import. Should we focus on DMN import only for the "beginning"? > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Edson Tirelli > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Alexandros Koufoudakis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Alexandros Koufoudakis updated DROOLS-1663: ------------------------------------------- Attachment: IMG_2197.jpg IMG_2198.jpg IMG_2199.jpg > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Edson Tirelli > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Alexandros Koufoudakis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Alexandros Koufoudakis commented on DROOLS-1663: ------------------------------------------------ A small clarification. Currently, DMN specification supports the following "types" of import: - DMN Import - import of decisions, BKMs, item definitions, etc. - XML Import - import of data tables defined in other XML files - XSD Import - import of XSD type definitions. This is stated in the "DMN Method and Style", B. Silver. Please, check the attached pages. !IMG_2197.jpg|thumbnail! !IMG_2198.jpg|thumbnail! !IMG_2199.jpg|thumbnail! The specification, however, does not mention any specific type (DMN, XML, XSD). Of course, you can find combination of words "XSD import" here and there in the Specs, but, again, as I said, there's nothing specific about what you can exactly import. Should we focus on DMN import only for the "beginning"? > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Edson Tirelli > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2787) Add test cases for one way and two way SSL for slave connecting to master (Elytron)

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2787?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2787: ------------------------------- Fix Version/s: 3.0.0.Beta29 (was: 3.0.0.Beta24) > Add test cases for one way and two way SSL for slave connecting to master (Elytron) > ----------------------------------------------------------------------------------- > > Key: WFCORE-2787 > URL: https://issues.jboss.org/browse/WFCORE-2787 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Richard Janík > Assignee: Richard Janík > Fix For: 3.0.0.Beta29 > > > WFCORE already contains tests of this kind with the old security implementation. Extend this to Elytron. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1287) Update CLIENT_CERT mechanism to use Scope.SSL_SESSION instead of SSLSession

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1287: ------------------------------------- Summary: Update CLIENT_CERT mechanism to use Scope.SSL_SESSION instead of SSLSession Key: ELY-1287 URL: https://issues.jboss.org/browse/ELY-1287 Project: WildFly Elytron Issue Type: Enhancement Components: HTTP Reporter: Darran Lofthouse Fix For: 2.0.0.Alpha1 This would mean even if the actual SSLSession is unavailable the integration still has the opportunity to provide a scope that represents the session. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Stylianos Koussouris (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Stylianos Koussouris commented on DROOLS-1663: ---------------------------------------------- AGENDA Behavior Right now we would need to know that Decision Top relies on Decision S-1, Decision S-2 etc. AND for the order these decisions exist in the DRD in order to have (without the import) the necessary conclusions in place when we "go up" the decision tree. However, (I will add this to the JIRA for consideration) when we have IMPORT how does Agenda behaves? ie. in drools I would expect Decision-Top wouldn't be entered into the Agenda until its pre-condition (ie. left-hand side of decisions) have been met But if I had inputs for the sub-decisions these would execute first activating other decisions until reaching the satisfaction of the Decision Top on DMN I don't think, even if we had IMPORT, the DECISION "activation" would work that way, right? I need to know ALL the supporting decisions which my Decision Top relies upon and execute those first before attempting it, correct? > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Edson Tirelli > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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