[
https://issues.apache.org/jira/browse/OFBIZ-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736645#comment-13736645 ]
Jacques Le Roux commented on OFBIZ-5267:
----------------------------------------
Hi Taher,
Let me explain the situation with as less words as possible (maybe not for you, but this will clarifies for all of us)
Historically there was only one tool for report rendering (essentially pdf reports): Apache FOP.
Then Birt was introduced in framework and this was causing some issues which were discuted in dev ML. So it was decided to move it out of the framework and to keep only Apache FOP. [You might find some threads there|
http://ofbiz.markmail.org/search/birt+specialpurpose+list:org.apache.ofbiz.dev].
With last releases branches (since 13.07), only the ecommerce component is kept in specialpurpose. Jacopo, with the commit referenced above, moved the birt reports from concerned applications (accounting, facilty and order) controllers to the birt component in specialpurpose. This works well for releases, where the birt reports don't show. But gives the error we are working on in trunk. One solution in trunk is to put an include to the birt controller in concerned applications controllers. But this would generate an error (non blocking, still ugly in log) in releases.
We have few solutions:
# Neglect the error in log for releases (nothing easier but ugly)
# Handle the error in releases. For instance we could add an if-possible attribute to the include element in controller. When sets to true it would not show the error in log (smart? But maybe hard to introduce)
# Dynamically patch the concerned applications controllers when calling reports in trunk by adding the include to the birt controller (ugly and not definitive, a new report in non yet concerned application would mean a new patch, etc.)
# Move out the birt reports from concerned applications to a specific Report webapp in Birt (tedious? But maybe another way to see report)
# ...?
I believe the second option is the lighter and smarter. What is your opinion, other ideas?
> Net before overhead report generates an error
> ---------------------------------------------
>
> Key: OFBIZ-5267
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5267> Project: OFBiz
> Issue Type: Bug
> Components: order
> Affects Versions: SVN trunk
> Reporter: Pierre Smits
> Fix For: SVN trunk
>
>
> When trying to generate a 'Net Before Overhead Report' in ORDERMGR:Reports following error is shown:
> org.ofbiz.webapp.control.RequestHandlerException: Unknown request [NetBeforeOverheadReport.pdf]; this request does not exist or cannot be called directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Locked
