[JBoss JIRA] (WFLY-13017) cloud-server layer to extend jaxrs-server layer
by Jean Francois Denise (Jira)
Jean Francois Denise created WFLY-13017:
-------------------------------------------
Summary: cloud-server layer to extend jaxrs-server layer
Key: WFLY-13017
URL: https://issues.redhat.com/browse/WFLY-13017
Project: WildFly
Issue Type: Bug
Components: Build System
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
cloud-server depends on cloud-profile although we want it to be an extension of jaxrs-server layer.
This fix an internal refactoring that doesn't change the capabilities provisioned by the cloud-server layer.
The benefit of this refactoring is that core layers datasources-web-server, jaxrs-server and cloud-server are designed the same way with consistent dependency tree. As an example, a provisioned cloud-server or jaxrs-server server with jpa excluded allows to use datasources support in both cases.
The change imply:
* Make jaxrs optional in jaxrs-server (was optional in cloud-profile).
* Make cloud-server to depend on jaxrs-server.
* Update community documentation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4920) Scenario simulation for DMN with collections throws en error
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4920?page=com.atlassian.jira.plug... ]
Yeser Amer commented on DROOLS-4920:
------------------------------------
[~danielezonca] To solve it, we need to evaluate how to modify (or remove) this statement in DMNScenarioValidation:85
{code:java}
// error if direct mapping (= simple type) but it is a composite
// NOTE: context is a special case so it is composite even if no fields are declared
Type rootType = getRootType((BaseDMNTypeImpl) rootDMNType);
if (!CONTEXT.equals(rootType) && steps.isEmpty() && rootDMNType.isComposite()) {
{code}
> Scenario simulation for DMN with collections throws en error
> ------------------------------------------------------------
>
> Key: DROOLS-4920
> URL: https://issues.redhat.com/browse/DROOLS-4920
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.31.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-08 14-14-05.png, urgent.dmn
>
>
> If a user tries to create a test scenario for [^urgent.dmn] he will get a [1] even when he is creating test scenario for the first time.
> [1]
> !Screenshot from 2020-01-08 14-14-05.png|thumbnail!
> h3. Acceptance criteria
> https://github.com/jboss-integration/bxms-qe-tests/pull/3048
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4973) Defined DMN collection unary checks do not pass
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-4973?page=com.atlassian.jira.plug... ]
Matteo Mortari commented on DROOLS-4973:
----------------------------------------
I can confirm that in FEEL, like in most (common sense) programming languages, List is an (ordered) list of elements.
Also comparing FEEL list with another FEEL list:
!screenshot-1.png|thumbnail!
which is consistent, expects the same elements, in the same order.
> Defined DMN collection unary checks do not pass
> -----------------------------------------------
>
> Key: DROOLS-4973
> URL: https://issues.redhat.com/browse/DROOLS-4973
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Critical
> Labels: drools-tools
> Attachments: MySpace_eshop.zip, screenshot-1.png
>
>
> Import the attached project and click Build, then Test.
> The re are defined 2 groups of 2 equivalent tests. In each group one test has a collection unary check defined with UI editor and one test defined a collection unary check with textual editor. The issue is tests with the unary check defined via textual editor do not pass.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4973) Defined DMN collection unary checks do not pass
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-4973?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-4973:
-----------------------------------
Attachment: screenshot-1.png
> Defined DMN collection unary checks do not pass
> -----------------------------------------------
>
> Key: DROOLS-4973
> URL: https://issues.redhat.com/browse/DROOLS-4973
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Critical
> Labels: drools-tools
> Attachments: MySpace_eshop.zip, screenshot-1.png
>
>
> Import the attached project and click Build, then Test.
> The re are defined 2 groups of 2 equivalent tests. In each group one test has a collection unary check defined with UI editor and one test defined a collection unary check with textual editor. The issue is tests with the unary check defined via textual editor do not pass.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4975) Defined Rule collection unary checks do not pass
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4975?page=com.atlassian.jira.plug... ]
Yeser Amer commented on DROOLS-4975:
------------------------------------
[~jomarko] In this case the cause of the issue is exactly the same explained by [~danielezonca] in https://issues.redhat.com/browse/DROOLS-4950. Guided editor and collection defined by expression can't be considered semantically the same functionality. The second case simply uses the java.equals() to compare the objects (in this case the list) and for this reason the test fails in this case. Guided editor apply a more complex way to compare.
Considering that, I propose to close this ticket and mark it as DUPLICATED of https://issues.redhat.com/browse/DROOLS-4950
> Defined Rule collection unary checks do not pass
> ------------------------------------------------
>
> Key: DROOLS-4975
> URL: https://issues.redhat.com/browse/DROOLS-4975
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Critical
> Labels: drools-tools
> Attachments: MySpace_filtering.zip
>
>
> Import the attached project and click Build, then Test.
> The re are defined equivalent tests. One test has a collection unary check defined with UI editor and one test defined a collection unary check with textual editor. The issue is tests with the unary check defined via textual editor does not pass.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4973) Defined DMN collection unary checks do not pass
by Daniele Zonca (Jira)
[ https://issues.redhat.com/browse/DROOLS-4973?page=com.atlassian.jira.plug... ]
Daniele Zonca commented on DROOLS-4973:
---------------------------------------
[~tari_manga]
Can you please confirm
{{"?=[{Price:2000,Name:"PC"},{Price:3300,Name:"CAR"}]"}}
is a list comparison that consider order too?
> Defined DMN collection unary checks do not pass
> -----------------------------------------------
>
> Key: DROOLS-4973
> URL: https://issues.redhat.com/browse/DROOLS-4973
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Critical
> Labels: drools-tools
> Attachments: MySpace_eshop.zip
>
>
> Import the attached project and click Build, then Test.
> The re are defined 2 groups of 2 equivalent tests. In each group one test has a collection unary check defined with UI editor and one test defined a collection unary check with textual editor. The issue is tests with the unary check defined via textual editor do not pass.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4973) Defined DMN collection unary checks do not pass
by Daniele Zonca (Jira)
[ https://issues.redhat.com/browse/DROOLS-4973?page=com.atlassian.jira.plug... ]
Daniele Zonca edited comment on DROOLS-4973 at 1/27/20 10:48 AM:
-----------------------------------------------------------------
[~tari_manga]
Can you please confirm
{code:java}
"?=[{Price:3300,Name:"CAR"}, {Price:2000,Name:"PC"}]"
{code}
is a list comparison that consider order too?
was (Author: danielezonca):
[~tari_manga]
Can you please confirm
{{"?=[{Price:2000,Name:"PC"},{Price:3300,Name:"CAR"}]"}}
is a list comparison that consider order too?
> Defined DMN collection unary checks do not pass
> -----------------------------------------------
>
> Key: DROOLS-4973
> URL: https://issues.redhat.com/browse/DROOLS-4973
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Critical
> Labels: drools-tools
> Attachments: MySpace_eshop.zip
>
>
> Import the attached project and click Build, then Test.
> The re are defined 2 groups of 2 equivalent tests. In each group one test has a collection unary check defined with UI editor and one test defined a collection unary check with textual editor. The issue is tests with the unary check defined via textual editor do not pass.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4973) Defined DMN collection unary checks do not pass
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4973?page=com.atlassian.jira.plug... ]
Yeser Amer edited comment on DROOLS-4973 at 1/27/20 10:45 AM:
--------------------------------------------------------------
[~jomarko] [~danielezonca] The cause of the issue can be explained with the current logic used by FEEL evaluator to compare two collections. According to this logic, 2 collections are equals if they contain the same elements IN THE SAME ORDER. You can find this logic in
{code:java}
EvalHelper.java
{code}
class, line 651.
Then, to solve the first failed test in the reported case, simply change
{code:java}
"?=[{Price:3300,Name:"CAR"}, {Price:2000,Name:"PC"}]"
{code}
to
{code:java}
"?=[{Price:2000,Name:"PC"},{Price:3300,Name:"CAR"}]"
{code}
and the test will pass with success. Don't know the reason of this logic in FEEL, if is expected or not.
was (Author: yamer):
[~jomarko] [~danielezonca] The cause of the issue can be explained with the current logic used by FEEL evaluator to compare two collections. According to this logic, 2 collections are equals if they contain the same elements IN THE SAME ORDER. You can find this logic in EvalHelper.java class, line 651.
Then, to solve the first failed test in the reported case, simply change
{code:java}
"?=[{Price:3300,Name:"CAR"}, {Price:2000,Name:"PC"}]"
{code}
to
{code:java}
"?=[{Price:2000,Name:"PC"},{Price:3300,Name:"CAR"}]"
{code}
and the test will pass with success. Don't know the reason of this logic in FEEL, if is expected or not.
> Defined DMN collection unary checks do not pass
> -----------------------------------------------
>
> Key: DROOLS-4973
> URL: https://issues.redhat.com/browse/DROOLS-4973
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Critical
> Labels: drools-tools
> Attachments: MySpace_eshop.zip
>
>
> Import the attached project and click Build, then Test.
> The re are defined 2 groups of 2 equivalent tests. In each group one test has a collection unary check defined with UI editor and one test defined a collection unary check with textual editor. The issue is tests with the unary check defined via textual editor do not pass.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4973) Defined DMN collection unary checks do not pass
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4973?page=com.atlassian.jira.plug... ]
Yeser Amer edited comment on DROOLS-4973 at 1/27/20 10:44 AM:
--------------------------------------------------------------
[~jomarko] [~danielezonca] The cause of the issue can be explained with the current logic used by FEEL evaluator to compare two collections. According to this logic, 2 collections are equals if they contain the same elements IN THE SAME ORDER. You can find this logic in EvalHelper.java class, line 651.
Then, to solve the first failed test in the reported case, simply change
{code:java}
"?=[{Price:3300,Name:"CAR"}, {Price:2000,Name:"PC"}]"
{code}
to
{code:java}
"?=[{Price:2000,Name:"PC"},{Price:3300,Name:"CAR"}]"
{code}
and the test will pass with success. Don't know the reason of this logic in FEEL, if is expected or not.
was (Author: yamer):
[~jomarko] [~danielezonca] The cause of the issue can be explained with the current logic used by FEEL evaluator to compare two collections. According to this logic, 2 collections are equals if they contain the same elements IN THE SAME ORDER. You can find this logic in EvalHelper.java class, line 651.
Then, to solve the first failed test in the reported case, simply change "?=[{Price:3300,Name:"CAR"}, {Price:2000,Name:"PC"}]" to "?=[{Price:2000,Name:"PC"},{Price:3300,Name:"CAR"}]" and the test will pass with success. Don't know the reason of this logic in FEEL, if is expected or not.
> Defined DMN collection unary checks do not pass
> -----------------------------------------------
>
> Key: DROOLS-4973
> URL: https://issues.redhat.com/browse/DROOLS-4973
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Critical
> Labels: drools-tools
> Attachments: MySpace_eshop.zip
>
>
> Import the attached project and click Build, then Test.
> The re are defined 2 groups of 2 equivalent tests. In each group one test has a collection unary check defined with UI editor and one test defined a collection unary check with textual editor. The issue is tests with the unary check defined via textual editor do not pass.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months