[ 
http://mifosforge.jira.com/browse/MIFOS-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66287#comment-66287
 ] 

Adam Monsen commented on MIFOS-4112:
------------------------------------

Cool! Is this ready to join the patch queue for review?

> Resolving MIFOS-3859 exposed a bug where typeMismatch.* error messages do not 
> display correctly
> -----------------------------------------------------------------------------------------------
>
>                 Key: MIFOS-4112
>                 URL: http://mifosforge.jira.com/browse/MIFOS-4112
>             Project: mifos
>          Issue Type: Bug
>          Components: Loan Account
>            Reporter: jasmine sandhu
>            Assignee: jasmine sandhu
>              Labels: volunteer
>             Fix For: Mifos Backlog
>
>         Attachments: 
> 0001-MIFOS-4112-added-messages-nontranslated.properties.patch, 
> 0001-MIFOS-4112-fixed-the-display-of-the-error-messages-t.patch, 
> defineLoanProducts-test.html, typeMismatchError_after3859.png, 
> typeMismatchError_after3859.png, typeMismatchErrorOnCI_oldCode.png, 
> typeMismatchErrorOnCI_oldCode.png
>
>          Time Spent: 1 week, 3 days, 2 hours
>  Remaining Estimate: 0 minutes
>
> In fixing: http://mifosforge.jira.com/browse/MIFOS-3859
> the error messages displayed when the defineLoanProducts.flt form is 
> incorrectly filled are validated by LoanProductFormBeanValidator.java. This 
> class constructs the keys for the messages based on the constraint violation, 
> so if the field is null, it constructs a message as:
> NotNull.loanProduct.*
> This message is then read from messages.properties. The messages of the form: 
> typeMismatch.loanProduct.* are not being displayed correctly after this 
> parameterization. 
> As an example, if I enter a string for the first entry in the Last Loan 
> Amount table, it should trigger a typeMismatch error (see attached images).
> In the previous version, it appears the typeMismatch.* key was not being 
> read, but the error was nicer in that it displayed:
> Invalid data
> Now, with the update, the error reads the string from the key but does not 
> replace the parameter correctly. So it shows up as:
> Please Specify the valid Start Range Loan Amount for by last loan at row 
> loanAmountByLastLoanAmount[0].lower
> but it should show up as follows if the error occurred on row 1:
> Please Specify the valid Start Range Loan Amount for by last loan at row 1.
> The commit for Mifos-3859 is: 7d543c9621afadd7754e72b83401678b0bf410ca

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to