[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] Wrong test result status if rules have not been fired
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5263:
---------------------------------
Summary: [Test Scenario Editor] Wrong test result status if rules have not been fired (was: [Test Scenario Editor] List does not initializing)
> [Test Scenario Editor] Wrong test result status if rules have not been fired
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to legacy test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] List does not initializing
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak reassigned DROOLS-5263:
------------------------------------
Assignee: Yeser Amer (was: Toni Rikkola)
> [Test Scenario Editor] List does not initializing
> -------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to legacy test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] List does not initializing
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5263:
---------------------------------
Description:
Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
Then test passes but rules are not getting fired.
This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
Root case :
We removed initialization of the list by default .
Previously when you have been adding a fact to legacy test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
Now If you add a list fact you are free to left it empty or initialize it with at least one element.
Workaround: put in GIVEN section for the list at least one empty element
Customer case details:
https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
was:
Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
Then test passes but rules are not getting fired.
This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
Root case :
We removed initialization of the list by default .
Previously when you have been adding a fact to test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
Now If you add a list fact you are free to left it empty or initialize it with at least one element.
Workaround: put in GIVEN section for the list at least one empty element
Customer case details:
https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
> [Test Scenario Editor] List does not initializing
> -------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to legacy test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] List does not initializing
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak commented on DROOLS-5263:
--------------------------------------
!screenshot-3.png|thumbnail! Scesim example
> [Test Scenario Editor] List does not initializing
> -------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] List does not initializing
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5263:
---------------------------------
Attachment: screenshot-3.png
> [Test Scenario Editor] List does not initializing
> -------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] List does not initializing
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5263:
---------------------------------
Attachment: screenshot-1.png
> [Test Scenario Editor] List does not initializing
> -------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] List does not initializing
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5263:
---------------------------------
Attachment: screenshot-2.png
> [Test Scenario Editor] List does not initializing
> -------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13379) Redirect after "j_security_check" login does not work if URL has no trailing slash
by Issa Gueye (Jira)
[ https://issues.redhat.com/browse/WFLY-13379?page=com.atlassian.jira.plugi... ]
Issa Gueye edited comment on WFLY-13379 at 4/21/20 10:29 AM:
-------------------------------------------------------------
This is a known issue, and it is related to UNDERTOW-1637
A fix is expected in EAP 7.3.1 as per JBEAP-18488 ; and in EAP 7.2.8 as per JBEAP-18378
There are some simple workarounds also available as per KB Solution https://access.redhat.com/solutions/4677911
was (Author: rhn-support-igueye):
This is a known issue is related to UNDERTOW-1637
A fix is expected in EAP 7.3.1 as per JBEAP-18488 ; and in EAP 7.2.8 as per JBEAP-18378
There are some simple workarounds also available as per KB Solution https://access.redhat.com/solutions/4677911
> Redirect after "j_security_check" login does not work if URL has no trailing slash
> ----------------------------------------------------------------------------------
>
> Key: WFLY-13379
> URL: https://issues.redhat.com/browse/WFLY-13379
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 19.0.0.Final
> Reporter: Wolfgang Knauf
> Assignee: Darran Lofthouse
> Priority: Major
> Attachments: Security.ear, configure.cli, restore-configuration.cli
>
>
> Attached file "Security.ear" contains a web application with a single jsp page "index.jsp" and form based login, which is secured by a Database Identity Store (Elytron).
> When calling the root URL of the webapp without specifiying any page and {color:red}*no*{color} trailing slash (http://localhost:8080/SecurityWeb), on WildFly 11 the login form is shown, and then the welcome file "index.jsp" is shown.
> On WildFly 19, the login form is shown, and after successful login, there is an error message "404 - Not Found", and the URL in the adress bar changes to http://localhost:8080/j_security_check
> It works if the URL is "http://localhost:8080/SecurityWeb/" (trailing slash). It seems WildFly 11 appends the "/" automatically when redirecting to the login form, while WildFly 19 keeps this URL.
> To run the sample, you have to add the Elytron config - the script "configure.cli" can be used for this:
> jboss-cli.bat --file=path_to\configure.cli
> The script "restore-configuration.cli" undoes this configuration.
> Username/Password are e.g. "admin"/"admin" - the sample creates a user table based on an ejb and "import.sql" inserts users.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13379) Redirect after "j_security_check" login does not work if URL has no trailing slash
by Issa Gueye (Jira)
[ https://issues.redhat.com/browse/WFLY-13379?page=com.atlassian.jira.plugi... ]
Issa Gueye commented on WFLY-13379:
-----------------------------------
This is a known issue is related to UNDERTOW-1637
A fix is expected in EAP 7.3.1 as per JBEAP-18488 ; and in EAP 7.2.8 as per JBEAP-18378
There are some simple workarounds also available as per KB Solution https://access.redhat.com/solutions/4677911
> Redirect after "j_security_check" login does not work if URL has no trailing slash
> ----------------------------------------------------------------------------------
>
> Key: WFLY-13379
> URL: https://issues.redhat.com/browse/WFLY-13379
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 19.0.0.Final
> Reporter: Wolfgang Knauf
> Assignee: Darran Lofthouse
> Priority: Major
> Attachments: Security.ear, configure.cli, restore-configuration.cli
>
>
> Attached file "Security.ear" contains a web application with a single jsp page "index.jsp" and form based login, which is secured by a Database Identity Store (Elytron).
> When calling the root URL of the webapp without specifiying any page and {color:red}*no*{color} trailing slash (http://localhost:8080/SecurityWeb), on WildFly 11 the login form is shown, and then the welcome file "index.jsp" is shown.
> On WildFly 19, the login form is shown, and after successful login, there is an error message "404 - Not Found", and the URL in the adress bar changes to http://localhost:8080/j_security_check
> It works if the URL is "http://localhost:8080/SecurityWeb/" (trailing slash). It seems WildFly 11 appends the "/" automatically when redirecting to the login form, while WildFly 19 keeps this URL.
> To run the sample, you have to add the Elytron config - the script "configure.cli" can be used for this:
> jboss-cli.bat --file=path_to\configure.cli
> The script "restore-configuration.cli" undoes this configuration.
> Username/Password are e.g. "admin"/"admin" - the sample creates a user table based on an ejb and "import.sql" inserts users.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months