[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by tao zhu (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
tao zhu edited comment on DROOLS-3674 at 2/21/19 4:37 AM:
----------------------------------------------------------
Hi [~danielezonca] Here is my solution.
As user after a test run, he will see not only the cell that are not correct with red background but also a red info icon. User could click the “red info icon“, then there will be a popup message to review the error reason.
!Error reporting after test run.png|thumbnail! !Error reporting after test run-popup.png|thumbnail!
https://redhat.invisionapp.com/share/MAQMQR75NPB
What do you think about it?
was (Author: zhutaojiajia):
Hi [~danielezonca] Here is my solution.
As user after a test run, user will see not only the cell that are not correct with red background but also a red info icon. User could click the “red info icon“, then there will be a popup message to review the error reason.
!Error reporting after test run.png|thumbnail! !Error reporting after test run-popup.png|thumbnail!
https://redhat.invisionapp.com/share/MAQMQR75NPB
What do you think about it?
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-popup.png, Error reporting after test run.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by tao zhu (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
tao zhu edited comment on DROOLS-3674 at 2/21/19 4:37 AM:
----------------------------------------------------------
Hi [~danielezonca] Here is my solution.
As a user after a test run, he will see not only the cell that are not correct with red background but also a red info icon. User could click the “red info icon“, then there will be a popup message to review the error reason.
!Error reporting after test run.png|thumbnail! !Error reporting after test run-popup.png|thumbnail!
https://redhat.invisionapp.com/share/MAQMQR75NPB
What do you think about it?
was (Author: zhutaojiajia):
Hi [~danielezonca] Here is my solution.
As user after a test run, he will see not only the cell that are not correct with red background but also a red info icon. User could click the “red info icon“, then there will be a popup message to review the error reason.
!Error reporting after test run.png|thumbnail! !Error reporting after test run-popup.png|thumbnail!
https://redhat.invisionapp.com/share/MAQMQR75NPB
What do you think about it?
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-popup.png, Error reporting after test run.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by tao zhu (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
tao zhu commented on DROOLS-3674:
---------------------------------
Hi [~danielezonca] Here is my solution.
As user after a test run, user will see not only the cell that are not correct with red background but also a red info icon. After user click the “red info icon“,there will be a popup message to review the error reason.
!Error reporting after test run.png|thumbnail! !Error reporting after test run-popup.png|thumbnail!
https://redhat.invisionapp.com/share/MAQMQR75NPB
What do you think about it?
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-popup.png, Error reporting after test run.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by tao zhu (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
tao zhu updated DROOLS-3674:
----------------------------
Attachment: Error reporting after test run-popup.png
Error reporting after test run.png
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-popup.png, Error reporting after test run.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11630) JDBC datasource should be granted the connect SocketPermission
by Ivo Studensky (Jira)
[ https://issues.jboss.org/browse/WFLY-11630?page=com.atlassian.jira.plugin... ]
Ivo Studensky reassigned WFLY-11630:
------------------------------------
Assignee: Ivo Studensky (was: Flavia Rainone)
> JDBC datasource should be granted the connect SocketPermission
> --------------------------------------------------------------
>
> Key: WFLY-11630
> URL: https://issues.jboss.org/browse/WFLY-11630
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Security
> Affects Versions: 16.0.0.Beta1
> Reporter: Ondrej Kotek
> Assignee: Ivo Studensky
> Priority: Major
> Labels: security-manager
> Attachments: DataSourceDefinitionJPATestCase-output-missing_SocketPermission_Connect.txt
>
>
> When a deployment uses connection on a JDBC datasource, the deployment needs the {{connect}} {{SocketPermission}} granted.
> For example
> {noformat}
> ...
> DataSource ds = (DataSource) ctx.lookup("java:jboss/datasources/ExampleDS");
> Connection conn = ds.getConnection();
> ...
> {noformat}
> may require {{permissions.xml}} like
> {noformat}
> <permissions version="7">
> <!-- Connections to databases -->
> <permission>
> <class-name>java.net.SocketPermission</class-name>
> <name>*</name> <!-- This can be hardened by using specific URLs/IPs -->
> <actions>resolve,connect</actions>
> </permission>
> </permissions>
> {noformat}
> However, {{resolve}} {{SocketPermission}} should be enough. The JCA spec states, at the 21.2 session (SecurityPermissions), the rar should always be granted the {{connect}} {{SocketPermission.}} JDBC extends the JCA spec.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3678) MVELConcequenceBuilder treats '#' within String incorrectly as a comment at 2nd appearance
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-3678?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-3678:
---------------------------------
Description:
The rule below expects that "B#" is set to value of the fact. However, "B;#"(i.e. ';' added before '#") is set incorrectly
{noformat}
dialect "mvel"
rule "testRule"
when
$fact : Fact();
then
$fact.name = "A#";
$fact.value = "B#";
System.out.println( $fact );
end
{noformat}
Here is output.
{noformat}
Fact [name=A#, value=B;#]
{noformat}
'#' within the value at 2nd appearance is treated as a start of comment.
was:
The rule below expects that "B#" is set to value of the fact. However, "B;#"(i.e. ';' added before '#") is set incorrectly
{noformat}
dialect "mvel"
rule "testRule"
when
$fact : Fact();
then
$fact.name = "A#";"B#"
$fact.value = "B#";
System.out.println( $fact );
end
{noformat}
Here is output.
{noformat}
Fact [name=A#, value=B;#]
{noformat}
'#' within the value at 2nd appearance is treated as a start of comment.
> MVELConcequenceBuilder treats '#' within String incorrectly as a comment at 2nd appearance
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-3678
> URL: https://issues.jboss.org/browse/DROOLS-3678
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.14.0.Final
> Environment: RHDM 7.2.0
> dialect mvel
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
>
> The rule below expects that "B#" is set to value of the fact. However, "B;#"(i.e. ';' added before '#") is set incorrectly
> {noformat}
> dialect "mvel"
>
> rule "testRule"
> when
> $fact : Fact();
> then
> $fact.name = "A#";
> $fact.value = "B#";
> System.out.println( $fact );
> end
> {noformat}
> Here is output.
> {noformat}
> Fact [name=A#, value=B;#]
> {noformat}
> '#' within the value at 2nd appearance is treated as a start of comment.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3679) MVELConcequenceBuilder treats '#' within String incorrectly as a comment at 2nd appearance
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-3679:
------------------------------------
Summary: MVELConcequenceBuilder treats '#' within String incorrectly as a comment at 2nd appearance
Key: DROOLS-3679
URL: https://issues.jboss.org/browse/DROOLS-3679
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.14.0.Final
Environment: RHDM 7.2.0
dialect mvel
Reporter: Hiroko Miura
Assignee: Mario Fusco
The rule below expects that "B#" is set to value of the fact. However, "B;#"(i.e. ';' added before '#") is set incorrectly
{noformat}
dialect "mvel"
rule "testRule"
when
$fact : Fact();
then
$fact.name = "A#";"B#"
$fact.value = "B#";
System.out.println( $fact );
end
{noformat}
Here is output.
{noformat}
Fact [name=A#, value=B;#]
{noformat}
'#' within the value at 2nd appearance is treated as a start of comment.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3678) MVELConcequenceBuilder treats '#' within String incorrectly as a comment at 2nd appearance
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-3678?page=com.atlassian.jira.plugi... ]
Hiroko Miura reassigned DROOLS-3678:
------------------------------------
Assignee: Mario Fusco (was: Ant Stephenson)
> MVELConcequenceBuilder treats '#' within String incorrectly as a comment at 2nd appearance
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-3678
> URL: https://issues.jboss.org/browse/DROOLS-3678
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.14.0.Final
> Environment: RHDM 7.2.0
> dialect mvel
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
>
> The rule below expects that "B#" is set to value of the fact. However, "B;#"(i.e. ';' added before '#") is set incorrectly
> {noformat}
> dialect "mvel"
>
> rule "testRule"
> when
> $fact : Fact();
> then
> $fact.name = "A#";"B#"
> $fact.value = "B#";
> System.out.println( $fact );
> end
> {noformat}
> Here is output.
> {noformat}
> Fact [name=A#, value=B;#]
> {noformat}
> '#' within the value at 2nd appearance is treated as a start of comment.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months