[
https://issues.jboss.org/browse/RTGOV-359?page=com.atlassian.jira.plugin....
]
Gary Brown commented on RTGOV-359:
----------------------------------
Aim is to currently allow the UI to be deployed on the current version of the product,
which has this column length limitation. Also not sure having a complete stack trace is
ideal - the field should just be providing an indication of the problem.
The problem with the 'successful' status is that it is not being reported in the
UI - the result field only appears to be used for reporting the failure result.
It might be nice if the basic message just reports success or failure (with the by and
date/time fields), but provide a hoverover/popup with the failure details when relevant?
"Value too long" error when storing resubmit failure
result
-----------------------------------------------------------
Key: RTGOV-359
URL:
https://issues.jboss.org/browse/RTGOV-359
Project: RTGov (Run Time Governance)
Issue Type: Bug
Components: User Interface
Reporter: Gary Brown
Assignee: Michael Clay
Related to RTGOV-332.
When a failure occurs resubmitting the message, the result is stored in a property
associated with the situation. However there is a length restriction of VARCHAR(255) on
this field:
10:08:01,249 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper]
(http-/127.0.0.1:8080-3) Value too long for column "VALUE VARCHAR(255)":
"STRINGDECODE('org.overlord.rtgov.ui.client.model.UiException:
org.switchyard.HandlerException: SWITCHYARD014000: Validator ''org...
(12795)"; SQL statement:
insert into RTGOV_SITUATION_PROPERTIES (id, name, value) values (?, ?, ?) [22001-168]
The original intention of the result field was to report whether the message had been
resubmitted successfully or not. Therefore we have a few options:
1) Just report 'successful' or 'failed' in this field - however this
doesn't give an indication of why the resubmit failed. Although the failure is
reported at the time when the resubmit is performed, so just depends whether we actually
want the resubmission error to be persisted?
2) Truncate the error message - probably 250 characters would be enough anyway? However
we should prefix the result with "Failed: ".
Probably option 2 is best, although need to also ensure that a 'Successful'
result is also recorded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira