[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)
6 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)
6 years, 5 months
[JBoss JIRA] (DROOLS-2157) DMN Editor: Contexts: Add special behaviour of last row
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2157?page=com.atlassian.jira.plugi... ]
Michael Anstis resolved DROOLS-2157.
------------------------------------
Resolution: Done
> DMN Editor: Contexts: Add special behaviour of last row
> -------------------------------------------------------
>
> Key: DROOLS-2157
> URL: https://issues.jboss.org/browse/DROOLS-2157
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> The last row of a {{Context}} should span all columns and populate the last {{ContextEntry}} in the {{Context}}. It should not have a variable. This is the XML for a _regular_ row and the _final_ row:
> {code}
> <semantic:context id="_f4f86e5f-e3e3-4b99-9260-8086764e598f">
> <semantic:contextEntry>
> <semantic:variable id="_779ca919-15d8-48d0-a9f0-e0203e60fac6" name="in1"/>
> <semantic:literalExpression id="_4b8b8cc1-a56c-4673-8334-96e178cd04a4">
> <semantic:text>"literal exp" </semantic:text>
> </semantic:literalExpression>
> </semantic:contextEntry>
> <semantic:contextEntry>
> <semantic:literalExpression id="_297181da-d0d5-4137-960b-34836d5570e5">
> <semantic:text>"result" </semantic:text>
> </semantic:literalExpression>
> </semantic:contextEntry>
> </semantic:context>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (WFLY-9592) Arrays in Method Parameters are causing EJBAccessException for @PermitAll Methods
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9592?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar closed WFLY-9592.
-----------------------------
Resolution: Out of Date
Please check if it works in WildFly 11 and reopen if it does.
WF11 has completely new security layer.
> Arrays in Method Parameters are causing EJBAccessException for @PermitAll Methods
> ---------------------------------------------------------------------------------
>
> Key: WFLY-9592
> URL: https://issues.jboss.org/browse/WFLY-9592
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.1.0.Final
> Environment: Wildfly 10.1.0.Final in an Arquillian Managed Container Test
> Reporter: Marcus Handte
> Priority: Minor
>
> EJB methods with array parameters are causing EJBAccessExceptions when they are annotated with @PermitAll. This bug seemed to be present in 8.0.0.Alpha2 and was fixed (see WFLY-1658). But it seems to be present again in 10.1.0.Final.
> For my own use case, this is not a problem since I can simply change the method signatures to use lists instead of arrays. However, I can imagine that this could be a more significant problem for people trying to run existing code that they do not want to (or cannot) touch.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 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 commented on DROOLS-2161:
----------------------------------------
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)
6 years, 5 months
[JBoss JIRA] (WFCORE-2780) Improve buffer-pool model description
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2780?page=com.atlassian.jira.plugi... ]
Romain Pelisse updated WFCORE-2780:
-----------------------------------
Description:
Current state of buffer-pool model description:
{code}
[standalone@localhost:9990 /] /subsystem=io/buffer-pool=foo:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "Defines buffer pool",
"capabilities" => [{
"name" => "org.wildfly.io.buffer-pool",
"dynamic" => true
}],
"attributes" => {
"buffer-size" => {
"type" => INT,
"description" => "The size of each buffer slice in bytes, if not set optimal value is calculated based on available RAM resources in your system.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
},
"buffers-per-slice" => {
"type" => INT,
"description" => "How many buffers per slice, if not set optimal value is calculated based on available RAM resources in your system.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
},
"direct-buffers" => {
"type" => BOOLEAN,
"description" => "Does the buffer pool use direct buffers, some platforms don't support direct buffers",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
}
},
"operations" => undefined,
"notifications" => undefined,
"children" => {}
}
}
{code}
Following improvements should be done to it:
* In {{buffer-size}} and {{buffers-per-slice}} description there is mentioned something called 'slice'. Nowhere is described what it is. Suggested improvement: Explain what slice is, preferably in buffer-pool model description.
* In {{buffer-size}} and {{buffers-per-slice}} description there is this sentence: ''...if not set optimal value is calculated based on available RAM resources in your system" - how it is calculated? Is there any default fixed value? User would like to know this. Suggestion: Add explanation about default value.
* In {{direct-buffers}} description there is mentioned that some platforms don't support direct buffers? Is there mentioned which one or what determines whether direct buffers are supported on given platform? Suggested improvement: Explain what element determines whether direct buffers are supported.
> Improve buffer-pool model description
> -------------------------------------
>
> Key: WFCORE-2780
> URL: https://issues.jboss.org/browse/WFCORE-2780
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Romain Pelisse
> Assignee: Romain Pelisse
> Priority: Minor
>
> Current state of buffer-pool model description:
> {code}
> [standalone@localhost:9990 /] /subsystem=io/buffer-pool=foo:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "Defines buffer pool",
> "capabilities" => [{
> "name" => "org.wildfly.io.buffer-pool",
> "dynamic" => true
> }],
> "attributes" => {
> "buffer-size" => {
> "type" => INT,
> "description" => "The size of each buffer slice in bytes, if not set optimal value is calculated based on available RAM resources in your system.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> "buffers-per-slice" => {
> "type" => INT,
> "description" => "How many buffers per slice, if not set optimal value is calculated based on available RAM resources in your system.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> "direct-buffers" => {
> "type" => BOOLEAN,
> "description" => "Does the buffer pool use direct buffers, some platforms don't support direct buffers",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {}
> }
> }
> {code}
> Following improvements should be done to it:
> * In {{buffer-size}} and {{buffers-per-slice}} description there is mentioned something called 'slice'. Nowhere is described what it is. Suggested improvement: Explain what slice is, preferably in buffer-pool model description.
> * In {{buffer-size}} and {{buffers-per-slice}} description there is this sentence: ''...if not set optimal value is calculated based on available RAM resources in your system" - how it is calculated? Is there any default fixed value? User would like to know this. Suggestion: Add explanation about default value.
> * In {{direct-buffers}} description there is mentioned that some platforms don't support direct buffers? Is there mentioned which one or what determines whether direct buffers are supported on given platform? Suggested improvement: Explain what element determines whether direct buffers are supported.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (WFLY-9592) Arrays in Method Parameters are causing EJBAccessException for @PermitAll Methods
by Marcus Handte (JIRA)
Marcus Handte created WFLY-9592:
-----------------------------------
Summary: Arrays in Method Parameters are causing EJBAccessException for @PermitAll Methods
Key: WFLY-9592
URL: https://issues.jboss.org/browse/WFLY-9592
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 10.1.0.Final
Environment: Wildfly 10.1.0.Final in an Arquillian Managed Container Test
Reporter: Marcus Handte
Priority: Minor
EJB methods with array parameters are causing EJBAccessExceptions when they are annotated with @PermitAll. This bug seemed to be present in 8.0.0.Alpha2 and was fixed (see WFLY-1658). But it seems to be present again in 10.1.0.Final.
For my own use case, this is not a problem since I can simply change the method signatures to use lists instead of arrays. However, I can imagine that this could be a more significant problem for people trying to run existing code that they do not want to (or cannot) touch.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (DROOLS-2162) Error evaluating constraint
by Herve Remisio (JIRA)
Herve Remisio created DROOLS-2162:
-------------------------------------
Summary: Error evaluating constraint
Key: DROOLS-2162
URL: https://issues.jboss.org/browse/DROOLS-2162
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.4.1.Final
Reporter: Herve Remisio
Assignee: Mario Fusco
Priority: Blocker
Attachments: 2017-12-04_12-33-29.png
We detected a very strange behavior when processing Rules that contain expressions like "...startsWith(..".
!2017-12-04_12-33-29.png|thumbnail!
Sometimes this error disappears when we simply re-upload the Rule file and it gets recompiled.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months