Stack trace appears instead of warning message while trying to redo Loan 
account with cycle when client has active another Loan account of the same 
product
-----------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: MIFOS-5413
                 URL: http://mifosforge.jira.com/browse/MIFOS-5413
             Project: mifos
          Issue Type: Bug
          Components: Loan Account
    Affects Versions: 2.3.0-M2
            Reporter: Lukasz Chudy
            Priority: Major
             Fix For: Unscheduled
         Attachments: stackTrace.txt

When you try to redo Loan with cycle, when client has active another Loan of 
the same product, then stack trace appears instead of warning message. 

REPRO:
1. Create Loan Account from product with Loan cycle.
2. Disburse that Loan.
3. Go to Admin, Redo Loan.
4. Select the same Client and the same Loan product.
5. Fill all necessary data.
6. Submit redo Loan.

Expected result:
Validation message appears that Client has active another account of the same 
product.

Actual result:
Page with stack trace appears.

NOTE:
This stack trace can be displayed for all FTL pages.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
http://mifosforge.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to