[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Yeser Amer (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Yeser Amer updated DROOLS-4503:
-------------------------------
Component/s: Scenario Simulation and Testing
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Attachments: ErrorPopup.png, FollowError.png, InsertedValue.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4503:
-------------------------------------
Attachment: FollowError.png
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Attachments: ErrorPopup.png, FollowError.png, InsertedValue.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4503:
-------------------------------------
Description:
When the expected value for a field is a java long, the error popup reports
"The expected value is '2' but the actual one is '3L'."
That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
This is a little bit inconsistent and confusing, especially for someone not knowing java.
The worst consequence is that when user click "Apply", that literal is put inside the cell,
!InsertedValue.png|thumbnail!
and when sent to server it raise error (because server is expecting a number, not a string)
!FollowError.png|thumbnail!
was:
When the expected value for a field is a java long, the error popup reports
"The expected value is '2' but the actual one is '3L'."
That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
This is a little bit inconsistent and confusing, especially for someone not knowing java.
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Attachments: ErrorPopup.png, FollowError.png, InsertedValue.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
> The worst consequence is that when user click "Apply", that literal is put inside the cell,
> !InsertedValue.png|thumbnail!
> and when sent to server it raise error (because server is expecting a number, not a string)
> !FollowError.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4503:
-------------------------------------
Description:
When the expected value for a field is a java long, the error popup reports
"The expected value is '2' but the actual one is '3L'."
!ErrorPopup.png|thumbnail!
That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
This is a little bit inconsistent and confusing, especially for someone not knowing java.
The worst consequence is that when user click "Apply", that literal is put inside the cell,
!InsertedValue.png|thumbnail!
and when sent to server it raise error (because server is expecting a number, not a string)
!FollowError.png|thumbnail!
was:
When the expected value for a field is a java long, the error popup reports
"The expected value is '2' but the actual one is '3L'."
That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
This is a little bit inconsistent and confusing, especially for someone not knowing java.
The worst consequence is that when user click "Apply", that literal is put inside the cell,
!InsertedValue.png|thumbnail!
and when sent to server it raise error (because server is expecting a number, not a string)
!FollowError.png|thumbnail!
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Attachments: ErrorPopup.png, FollowError.png, InsertedValue.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> !ErrorPopup.png|thumbnail!
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
> The worst consequence is that when user click "Apply", that literal is put inside the cell,
> !InsertedValue.png|thumbnail!
> and when sent to server it raise error (because server is expecting a number, not a string)
> !FollowError.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4503:
-------------------------------------
Attachment: InsertedValue.png
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Attachments: ErrorPopup.png, InsertedValue.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4503:
-------------------------------------
Priority: Major (was: Minor)
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Attachments: ErrorPopup.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4503:
-------------------------------------
Description:
When the expected value for a field is a java long, the error popup reports
"The expected value is '2' but the actual one is '3L'."
That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
This is a little bit inconsistent and confusing, especially for someone not knowing java.
was:
When the expected value for a field is a java long, the error popup reports
"The expected value is '2' but the actual one is '3L'."
That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct.
This is a little bit inconsistent and confusing, especially for someone not knowing java.
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Minor
> Attachments: ErrorPopup.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4503:
-------------------------------------
Description:
When the expected value for a field is a java long, the error popup reports
"The expected value is '2' but the actual one is '3L'."
That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct.
This is a little bit inconsistent and confusing, especially for someone not knowing java.
was:
When the expected value for a filed is a java long, the error popup reports
"The expected value is '2' but the actual one is '3L'."
That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct.
This is a little bit inconsistent and confusing, especially for someone not knowing java.
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Minor
> Attachments: ErrorPopup.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct.
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-4503:
----------------------------------------
Summary: "Error" popup report java literal for suggested number
Key: DROOLS-4503
URL: https://issues.jboss.org/browse/DROOLS-4503
Project: Drools
Issue Type: Bug
Reporter: Gabriele Cardosi
Assignee: Yeser Amer
Attachments: ErrorPopup.png
When the expected value for a filed is a java long, the error popup reports
"The expected value is '2' but the actual one is '3L'."
That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct.
This is a little bit inconsistent and confusing, especially for someone not knowing java.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months