[
http://mifosforge.jira.com/browse/MIFOS-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63663#action_63663
]
Michael Vorburger edited comment on MIFOS-4429 at 1/15/11 8:59 AM:
-------------------------------------------------------------------
Main problem I ran into on this front was that BIRT as configured in Mifos
insisted in loading *.rptdesign via the filesystem, from where it thought the
WAR was (which in the case of the new Jetty-based workspace 2.0 is a temporary
directory...) instead of using the ServletContext getResource to find the
rptdesign in the (new)
mifos-reporting/src/main/resources/META-INF/resources/report/ via classpath
(Servlet context) instead of FS.
By digging a little bit into the BIRT source, I was able to finally find a
"clean" way to address this: by changing the BIRT_VIEWER_WORKING_FOLDER
context-param in the (formerly) web.xml / (now) a web-fragment.xml to any
relative path (e.g. 'report') instead of being empty, BIRT *will* actually use
ServletContext-based instead of FS-based access, as needed in a multi-module
META-INF/resources Servlet 3.0-approach set-up as in Mifos' new workspace!
We still need to check whether and which other BIRT_VIEWER_*_FOLDER
context-params may need the same change (use some relative folder instead of
leaving them empty as currently configured in Mifos).
In order to avoid BIRT reports failing because it would now be looking for some
report/report/*.rptdesign (note the double 'report'), I'd changed
org.mifos.reports.struts.action.ReportsUserParamsAction's loadAddList else
statement which prefixes the "report/" (lines 155-157). But loadAdminReport()
uses a similar "adminReport/" which I haven't looked into yet - that's probably
still not working? Not sure how to test that... what are admin reports? -- May
be instead of changing the ReportsUserParamsAction code, we should move all the
*.rptdesign under a new sub-dir named e.g. 'birtreports' (and configure that in
BIRT_VIEWER_WORKING_FOLDER instead of 'report'), and so then have
birtreports/report and birtreports/adminReport?
was (Author: vorburger):
Main problem I ran into on this front was that BIRT as configured in Mifos
insisted in loading *.rptdesign via the filesystem, from where I thought the
WAR was (which in the case of the new Jetty-based workspace 2.0 is a temporary
directory...) instead of using the ServletContext getResource to find the
rptdesign in the (new)
mifos-reporting/src/main/resources/META-INF/resources/report/ via classpath
(Servlet context) instead of FS.
By digging a little bit into the BIRT source, I was able to finally find a
"clean" way to address this: by changing the BIRT_VIEWER_WORKING_FOLDER
context-param in the (formerly) web.xml / (now) a web-fragment.xml to instead
of being empty having any relative path (e.g. 'report'), BIRT *will* actually
use ServletContext-based instead of FS-based access, as needed in a Servlet
3.0-approach set-up as ours!
We still need to check whether and which other BIRT_VIEWER_*_FOLDER
context-params may need the same change (use some relative folder instead of
leaving them empty as currently configured in Mifos).
In order to avoid BIRT reports failing because it would now be looking for some
report/report/*.rptdesign, I changed
org.mifos.reports.struts.action.ReportsUserParamsAction's loadAddList else
statement which prefixes the "report/" (lines 155-157). Because
loadAdminReport() uses a similar "adminReport/" which I haven't looked into yet
- that's probably still not working? Not sure how to test that... what are
admin reports? -- May be instead of changing the ReportsUserParamsAction code,
we should move them all into a new sub-dir named e.g. 'birtreports' (and
configure that in BIRT_VIEWER_WORKING_FOLDER instead of 'report'), and so then
have birtreports/report and birtreports/adminReport?
> New module 'reporting' (BIRT)
> -----------------------------
>
> Key: MIFOS-4429
> URL: http://mifosforge.jira.com/browse/MIFOS-4429
> Project: mifos
> Issue Type: Dev Task
> Reporter: Michael Vorburger
>
> What is all the stuff in application/reporting, BIRT?
> How is it used? Does the build make use of it (status unclear, to me) ?
> It won't work in my proposed "new workspace" (without some effort, may be
> possible; haven't investigated).
> Remove?
> Hm.
--
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
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
