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

Udai Gupta commented on MIFOS-4087:
-----------------------------------

Q. Was there a change in 1.6 that would make mifos suddenly care about this 
update_flag?
Yes, there were changes in 1.6 at Web layer (WebTierFeeServiceFacade was 
created). There is a FeeBO mapping code which maps FEES.UPDATE_FLAG to DTO 
which was added in 1.6. 
UPDATE_FLAG is only used by Batch job and "Fee edit/update", it is not part of 
"Fee View" or "Fee Create" UI. 
So in 1.5 it never used hit this field, but now in 1.6 the mapping method is 
used by all 3 operations (create/edit/view).
In past(pre 1.5) when fee was created this field used to stay null which is 
showing this behaviour.

Q. Are there any repercussions to manually altering the fees table to get rid 
of null value for fee ELDF?
No, it is safe to replace null with 0 in fees.update_flag.
see org.mifos.accounts.fees.util.helpers.FeeChangeType

This was the stacktrace when  update_flag is null and fees view is opened 
(leaving it blank) 
{code}
org.mifos.framework.exceptions.ServiceException: 
org.mifos.framework.exceptions.PropertyNotFoundException: FeeChangeType
        at 
org.mifos.accounts.fees.servicefacade.WebTierFeeServiceFacade.getProductFees(WebTierFeeServiceFacade.java:85)
        at 
org.mifos.accounts.fees.struts.action.FeeAction.viewAll(FeeAction.java:203)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:274)
        at 
org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:194)
        at 
org.mifos.framework.struts.action.BaseAction.execute(BaseAction.java:140)
        at 
org.mifos.framework.struts.action.MifosRequestProcessor.processActionPerform(MifosRequestProcessor.java:202)
        at 
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
        at 
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
        at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.mifos.security.util.LoginFilter.doFilter(LoginFilter.java:85)
        at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at 
org.mifos.servlet.filters.MifosLogFilter.doFilter(MifosLogFilter.java:73)
        at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at 
org.mifos.framework.persistence.DatabaseInitFilter.doFilter(DatabaseInitFilter.java:51)
        at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
        at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
        at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
        at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.mifos.framework.exceptions.PropertyNotFoundException: 
FeeChangeType
        at 
org.mifos.accounts.fees.util.helpers.FeeChangeType.getFeeChangeType(FeeChangeType.java:45)
        at 
org.mifos.accounts.fees.business.FeeBO.getFeeChangeType(FeeBO.java:181)
        at 
org.mifos.accounts.fees.servicefacade.WebTierFeeServiceFacade.mapFeeDto(WebTierFeeServiceFacade.java:119)
        at 
org.mifos.accounts.fees.servicefacade.WebTierFeeServiceFacade.mapFeeDtos(WebTierFeeServiceFacade.java:101)
        at 
org.mifos.accounts.fees.servicefacade.WebTierFeeServiceFacade.getProductFees(WebTierFeeServiceFacade.java:83)
{code}


> GK has Blank View Fee page
> --------------------------
>
>                 Key: MIFOS-4087
>                 URL: http://mifosforge.jira.com/browse/MIFOS-4087
>             Project: mifos
>          Issue Type: Bug
>          Components: Fee
>    Affects Versions: Release 1.6.0
>            Reporter: jbrewster
>            Assignee: Udai Gupta
>             Fix For: Release E - Iteration 11, Release E
>
>
> Praveen reported seeing a blank View Fee page during 1.6 upgrade testing.
> I was able to repro with GK data internally, but am able to work around the 
> issue by altering their set of fees so the fee ELDF update_flag value is not 
> null. 
>  
> Testing notes:
> I was able to reproduce the error with a GK data backup.  I first tried 
> setting the logging level to INFO to see if anything was logged in mifos.log, 
> but nothing was reported in the log.
> I then compared the fees table from GK's data to a generic test database.  I 
> noticed the null in update_flag.  After manually setting that fee's 
> udate_flag to "0", the view fee page now loads and shows all fees, allows 
> users to drill into fee details.  
> Questions:
> - was there a change in 1.6 that would make mifos suddenly care about this 
> update_flag?
> - are there any repercussions to manually altering the fees table to get rid 
> of null value for fee ELDF?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to