[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 (was: 2017 Week 45-46, 2017 Week 47-48)
> [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
> 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)
8 years, 5 months
[JBoss JIRA] (DROOLS-1609) Augment FEEL AST node at compilation with return type
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1609?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1609:
-----------------------------------
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 (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)
> Augment FEEL AST node at compilation with return type
> -----------------------------------------------------
>
> Key: DROOLS-1609
> URL: https://issues.jboss.org/browse/DROOLS-1609
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Minor
>
> This is needed so to be able to determine the result of a boxed function at compile time, in turn to be able at compile time to determine a valid compilation without error of a BKM for instance.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-1959) [DMN Editor] Extend marshaller support for Expressions
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1959?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1959:
-----------------------------------
Sprint: 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 (was: 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)
> [DMN Editor] Extend marshaller support for Expressions
> ------------------------------------------------------
>
> Key: DROOLS-1959
> URL: https://issues.jboss.org/browse/DROOLS-1959
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
> When UI support for DMN Expression is available, the marshaller shall be extended to support marshalling between DMN xml and the stunner representation of the expression.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-1553) Write documentation for the DMN and FEEL components
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1553?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1553:
-----------------------------------
Sprint: 2017 Week 22-23, 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 (was: 2017 Week 22-23, 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)
> Write documentation for the DMN and FEEL components
> ---------------------------------------------------
>
> Key: DROOLS-1553
> URL: https://issues.jboss.org/browse/DROOLS-1553
> Project: Drools
> Issue Type: Task
> Components: dmn engine
> Affects Versions: 7.0.0.CR3
> Reporter: Edson Tirelli
> Assignee: Edson Tirelli
> Fix For: 7.5.0.Final
>
>
> Write the documentation for both FEEL and DMN engines.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[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 (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)
> 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.5.0.Final
>
>
> Place holder for all DMN Editor related activities
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFCORE-3442) CLI can't reload if authentication configuration changed
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-3442:
--------------------------------------------
Summary: CLI can't reload if authentication configuration changed
Key: WFCORE-3442
URL: https://issues.jboss.org/browse/WFCORE-3442
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
The context:
- Legacy ManagementRealm, no local-auth enabled, only users located properties file.
- SASL authentication factory, digest with FooRealm, userName/password in other properties file
The http management interface
- Reference ManagementRealm and upgrade references SAL factory.
>From CLI:
1) User connects using credentials required for FooRealm
2) User disables SASL authentication : /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory,value=undefined
3) User reloads ==> Connection fails.
The user should be prompted for ManagementRealm credentials (if the current ones are not valid in the context of this realm).
Furthermore, ConnectionInfo should expose the realm the CLI is connected to.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (HAWKULARQE-202) Introduce usage of TestCaseNeeded to bugzilla workflow
by Filip Brychta (JIRA)
Filip Brychta created HAWKULARQE-202:
----------------------------------------
Summary: Introduce usage of TestCaseNeeded to bugzilla workflow
Key: HAWKULARQE-202
URL: https://issues.jboss.org/browse/HAWKULARQE-202
Project: Hawkular QE
Issue Type: Task
Reporter: Filip Brychta
Assignee: Michael Foley
We need to introduce TestCaseNeeded bugzilla keyword to our workflow.
This keyword should be used for all issues which are not covered by polarion test cases yet.
Following should be done:
* introduce the usage to our bugzilla workflow documents
* notify team to start using it
* got through older issues and add the keyword where necessary
* prepare query which will list issues with this keyword sorted by severity and share it with the team so every team member can pick some issue from the list and create polarion case
* when the case is crated the keyword should be removed
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFCORE-887) "Deprecate" using an expression in model refs to interfaces
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-887?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-887:
-----------------------------------------
Discussion of WFLY-9587 shows a possible other scenario where this kind of "deprecation" might be useful. So we should try to make the facility generic.
> "Deprecate" using an expression in model refs to interfaces
> -----------------------------------------------------------
>
> Key: WFCORE-887
> URL: https://issues.jboss.org/browse/WFCORE-887
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 4.0.0.Alpha5
>
>
> SocketBindingGroupResourceDefinition and OutboundSocketBindingResourceDefinition both have attributes that represent model refs to interface resources, but which also allow expressions.
> Model references should not allow expressions. These were "grandfathered in" when the large scale expression support roll out happened for AS 7.2 / EAP 6.1.
> There's no metadata facility to record that expression support is deprecated, but the add handler for these should log a WARN if they encounter an expression. Hopefully in EAP 8 we can then remove expression support.
> We should look for other cases like this too, although those changes should be separate JIRAs.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-9587) Investigate and introduce capabilities for the transactional subsytems transations/xts/rts
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9587?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-9587:
----------------------------------------
Re: jts, for expressions we had a pretty simple policy. All attributes must support expressions except those whose value:
1) Is a model reference (e.g. socket-binding=http).
2) Is a class or module name.
We had a simple policy because otherwise we'd end up with a really inconsistent API where different devs make different decisions about expression support, often coming down to "I don't think it's really needed for this one." That's what we had in AS 7.1 / EAP 6.0 which led to quite a number of bug reports where users disagreed and wanted the expression. We added the current policy in AS 7.2.
Now I think we need a 3rd category:
3) Controls whether an optional capability is installed or an optional requirement is added.
I believe there are only a few such attributes, maybe just this one. But I'm reluctant to break compatibility and drop expressions support altogether, not when it can be made to work for all but the real corner case of using a vault expression. Logging some sort of "expression deprecation" thing would be good though; something to help state that we advise against using an expression, helping to drive users away from it so that if we need to in some future release we can drop support and clean things out. For WFCORE-887 I have a similar need. I'll look into making the solution to that easily adapted to other cases. For example, just call setExpressionDeprecated() on the AttributeDefinition builder and then the kernel handles the logging.
> Investigate and introduce capabilities for the transactional subsytems transations/xts/rts
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-9587
> URL: https://issues.jboss.org/browse/WFLY-9587
> Project: WildFly
> Issue Type: Feature Request
> Components: Transactions, XTS
> Affects Versions: 11.0.0.Final
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
>
> The notion of capability is not introduced to the transactional system. The WFLY integration expecting subsystem providing it. The transaction subsystems should support so.
> https://docs.jboss.org/author/display/WFLY/Working+with+WildFly+Capabilities
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-2161) Recursive function definitions in context entries are raising compile time errors
by Fedor Gavrilov (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2161?page=com.atlassian.jira.plugi... ]
Fedor Gavrilov edited comment on DROOLS-2161 at 12/4/17 9:30 AM:
-----------------------------------------------------------------
java.lang.AssertionError: DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Variable named 'h' is missing its type reference on node 'x'', sourceId='_95c8b5cc-4dd3-4a7b-bd93-d2f709c88bf2', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Variable named 'g' is missing its type reference on node 'x'', sourceId='_9e512834-3b21-47ec-902b-5e9525b01f07', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Variable named 'new list' is missing its type reference on node 'x'', sourceId='_7aad66b5-f3a7-4eae-a717-3c94eeb3858d', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Variable named 'x' is missing its type reference on node 'x'', sourceId='_eb1123e4-ddd4-44d7-8103-7a8d1523c7d0', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Parameter named 'list' is missing its type reference on node 'x'', sourceId='_234ad53b-b2e2-4cb4-b578-1d22546d06af', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Parameter named 'limit' is missing its type reference on node 'x'', sourceId='_632ea9f5-c827-47ee-926f-0973466e99b6', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Parameter named 'n' is missing its type reference on node 'x'', sourceId='_a4180fb5-08f5-4bff-a56c-bc9ee9e98939', exception='', feelEvent=''}
DMNMessage{ severity=ERROR, type=TYPE_DEF_NOT_FOUND, message='Unable to resolve type reference 'tNumberList' on node 'x'', sourceId='_2f139270-6d81-4f0b-bf26-c85bd90033b1', exception='', feelEvent=''}
DMNMessage{ severity=ERROR, type=TYPE_DEF_NOT_FOUND, message='Unable to resolve type reference 'tNumberList' on node 'x'', sourceId='_8fe8d041-5a54-4377-ae5f-83e1b632e033', exception='', feelEvent=''}
DMNMessage{ severity=ERROR, type=ERR_COMPILING_FEEL, message='Error compiling FEEL expression 'append( list, n )' for name 'new list' on node 'x': Exception raised: NullPointerException', sourceId='_ce0a3445-cc1f-47a9-88b5-bd3f1c00c752', exception='NullPointerException : null', feelEvent=''}
DMNMessage{ severity=ERROR, type=ERR_COMPILING_FEEL, message='Error compiling FEEL expression 'if n + 1 > limit then
new list
else
f( n+1, limit, new list )' for name 'f' on node 'x': Exception raised: NullPointerException', sourceId='_89fb1571-a993-46fe-a8a7-0b51e11614a0', exception='NullPointerException : null', feelEvent=''}
DMNMessage{ severity=ERROR, type=ERR_COMPILING_FEEL, message='Error compiling FEEL expression 'function( n, limit, list ) {
new list : append( list, n ),
result : if n + 1 > limit then
new list
else
g( n+1, limit, new list )
}.result' for name 'g' on node 'x': Exception raised: NullPointerException', sourceId='_608dfc35-d13e-459a-998b-08ce33a48ca8', exception='NullPointerException : null', feelEvent=''}
DMNMessage{ severity=ERROR, type=ERR_COMPILING_FEEL, message='Error compiling FEEL expression 'if n + 1 > limit then
append( list, n )
else
h( n+1, limit, append( list, n ) )' for name 'h' on node 'x': Exception raised: NullPointerException', sourceId='_a8c548dd-77e4-4a9e-8490-4485754433f4', exception='NullPointerException : null', feelEvent=''}
DMNMessage{ severity=ERROR, type=ERR_COMPILING_FEEL, message='Error compiling FEEL expression '[ f( 1, 3, []), g( 1, 3, []), h( 1, 3, []) ]' for name 'x' on node 'x': Exception raised: NullPointerException', sourceId='_7e88403e-717f-4753-a747-a65368f7cd05', exception='NullPointerException : null', feelEvent=''}
was (Author: fedor.gavrilov):
java.lang.AssertionError: DMNMessage{ severity=ERROR, type=FAILED_XML_VALIDATION, message='Failed XML validation of DMN file: cvc-elt.1: Cannot find the declaration of element 'semantic:definitions'.', sourceId='null', exception='SAXParseException : cvc-elt.1: Cannot find the declaration of element 'semantic:definitions'.', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Variable named 'h' is missing its type reference on node 'x'', sourceId='_95c8b5cc-4dd3-4a7b-bd93-d2f709c88bf2', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Variable named 'g' is missing its type reference on node 'x'', sourceId='_9e512834-3b21-47ec-902b-5e9525b01f07', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Variable named 'new list' is missing its type reference on node 'x'', sourceId='_7aad66b5-f3a7-4eae-a717-3c94eeb3858d', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Variable named 'x' is missing its type reference on node 'x'', sourceId='_eb1123e4-ddd4-44d7-8103-7a8d1523c7d0', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Parameter named 'list' is missing its type reference on node 'x'', sourceId='_234ad53b-b2e2-4cb4-b578-1d22546d06af', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Parameter named 'limit' is missing its type reference on node 'x'', sourceId='_632ea9f5-c827-47ee-926f-0973466e99b6', exception='', feelEvent=''}
DMNMessage{ severity=WARN, type=MISSING_TYPE_REF, message='Parameter named 'n' is missing its type reference on node 'x'', sourceId='_a4180fb5-08f5-4bff-a56c-bc9ee9e98939', exception='', feelEvent=''}
DMNMessage{ severity=ERROR, type=ERR_COMPILING_FEEL, message='Error compiling FEEL expression 'if n + 1 > limit then
new list
else
f( n+1, limit, new list )' for name 'f' on node 'x': Unknown variable 'f'', sourceId='_89fb1571-a993-46fe-a8a7-0b51e11614a0', exception='', feelEvent='UnknownVariableErrorEvent : Unknown variable 'f''}
DMNMessage{ severity=ERROR, type=ERR_COMPILING_FEEL, message='Error compiling FEEL expression 'if n + 1 > limit then
append( list, n )
else
h( n+1, limit, append( list, n ) )' for name 'h' on node 'x': Unknown variable 'h'', sourceId='_a8c548dd-77e4-4a9e-8490-4485754433f4', exception='', feelEvent='UnknownVariableErrorEvent : Unknown variable 'h''}
> Recursive function definitions in context entries are raising compile time errors
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-2161
> URL: https://issues.jboss.org/browse/DROOLS-2161
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.4.1.Final
> Reporter: Edson Tirelli
> Assignee: Fedor Gavrilov
> Attachments: ContextRecursion.dmn
>
>
> Recursive function definitions in contexts are raising compile time errors but are executing correctly.
> See attached model for example. Functions "f" and "h" raise compile time errors.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months