[ http://mifosforge.jira.com/browse/MIFOS-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=70155#comment-70155 ]
keithwoodlock commented on MIFOS-3610:
--------------------------------------
Lukasz, Ferenc,
As far as I can see, the userContext was never populated with the user global no. So I marked the issue as invalid as if ferenc or any other developer wanted access to the user global no they could get that off the PersonnelBO entity itself (infact its DTO equivalent) rather than translating it into another location (UserContext).
Added to this, the UserContext is passed back to .jsp pages but it is not the strategy with .ftl pages. Instead other DTO objects are passed back and the objective going forward was to remove all .jsp pages and release the lock they have on domain objects.
> UserContext.userGlobalNo does not get populated
> -----------------------------------------------
>
> Key: MIFOS-3610
> URL: http://mifosforge.jira.com/browse/MIFOS-3610
> Project: mifos
> Issue Type: Bug
> Components: Personnel
> Affects Versions: Release 1.6.0
> Reporter: Ferenc Kovács
> Assignee: keithwoodlock
> Priority: Trivial
> Fix For: Release 2.2.1
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> PersonnelBO.setUserContext() does not set userGlobalNo attribute of the UserContext. Hence it is not available at jsp side.
--
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
|