[jira] Created: (OFBIZ-338) Conversion of Manufacturing Jasper Reports to Fop

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (OFBIZ-338) Conversion of Manufacturing Jasper Reports to Fop

Nicolas Malin (Jira)
Conversion of Manufacturing Jasper Reports to Fop
-------------------------------------------------

                 Key: OFBIZ-338
                 URL: http://issues.apache.org/jira/browse/OFBIZ-338
             Project: OFBiz (The Open for Business Project)
          Issue Type: Improvement
          Components: manufacturing
    Affects Versions: SVN trunk
            Reporter: Marco Risaliti
            Priority: Minor


Hi Jacopo,

I have converted three manufacturing reports from Jasper Report to Fop and this one of the last steps for removing definitely Jaspert Reports libraries from SVN.
In this patch I have corrected also the createProductionRunsForOrder method that the productId parameter is no necessary and the wrong parameters numbers passed to the method getProductionRunTotResQty.
I have done also some changes for the I18n and some changes to Italian translation (like Ciclo di Produzione into Ordine di Produzione).
The cuttingReport doesn't run because the uiLabelMap was missing but now seems to be corrected.
If you can see this issue when you have time at disposal I will write the steps for apply those changes.

1. Apply the patch manufacturing_reports.patch
2. Add the files ShipmentLabel.fo.ftl, ShipmentPlanStockReport.fo.ftl, ShipmentWorkEffortTasks.fo.ftl into the folder applications\manufacturing\webapp\manufacturing\reports.
3. Add the files ShipmentLabel.bsh, ShipmentPlanStockReport.bsh, ShipmentWorkEffortTasks.bsh into the folder applications\manufacturing\webapp\manufacturing\WEB-INF\actions\reports
4. When everythings is ok, you can also remove the following files used by the old manufacturing JasperReports :
applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReportPrepare.bsh
applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReport.xml
applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabelPrepare.bsh
applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabel.xml
applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasksPrepare.bsh
applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasks.xml
 
If everything will be commit If you want I can create a new issue and relative patch for deleting all the reference to Jasper Report already present into the sources.

P.S.: I will attach also three screenshoots of the results of the new manufacturing fop reports.

Thanks in advance Jacopo

Marco


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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (OFBIZ-338) Conversion of Manufacturing Jasper Reports to Fop

Nicolas Malin (Jira)
     [ http://issues.apache.org/jira/browse/OFBIZ-338?page=all ]

Marco Risaliti updated OFBIZ-338:
---------------------------------

    Attachment: manufacturing_reports.patch
                ShipmentLabel.fo.ftl
                ShipmentPlanStockReport.fo.ftl

> Conversion of Manufacturing Jasper Reports to Fop
> -------------------------------------------------
>
>                 Key: OFBIZ-338
>                 URL: http://issues.apache.org/jira/browse/OFBIZ-338
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>          Components: manufacturing
>    Affects Versions: SVN trunk
>            Reporter: Marco Risaliti
>            Priority: Minor
>         Attachments: manufacturing_reports.patch, ShipmentLabel.bsh, ShipmentLabel.fo.ftl, ShipmentPlanStockReport.bsh, ShipmentPlanStockReport.fo.ftl, ShipmentWorkEffortTasks.fo.ftl
>
>
> Hi Jacopo,
> I have converted three manufacturing reports from Jasper Report to Fop and this one of the last steps for removing definitely Jaspert Reports libraries from SVN.
> In this patch I have corrected also the createProductionRunsForOrder method that the productId parameter is no necessary and the wrong parameters numbers passed to the method getProductionRunTotResQty.
> I have done also some changes for the I18n and some changes to Italian translation (like Ciclo di Produzione into Ordine di Produzione).
> The cuttingReport doesn't run because the uiLabelMap was missing but now seems to be corrected.
> If you can see this issue when you have time at disposal I will write the steps for apply those changes.
> 1. Apply the patch manufacturing_reports.patch
> 2. Add the files ShipmentLabel.fo.ftl, ShipmentPlanStockReport.fo.ftl, ShipmentWorkEffortTasks.fo.ftl into the folder applications\manufacturing\webapp\manufacturing\reports.
> 3. Add the files ShipmentLabel.bsh, ShipmentPlanStockReport.bsh, ShipmentWorkEffortTasks.bsh into the folder applications\manufacturing\webapp\manufacturing\WEB-INF\actions\reports
> 4. When everythings is ok, you can also remove the following files used by the old manufacturing JasperReports :
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReportPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReport.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabelPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabel.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasksPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasks.xml
>  
> If everything will be commit If you want I can create a new issue and relative patch for deleting all the reference to Jasper Report already present into the sources.
> P.S.: I will attach also three screenshoots of the results of the new manufacturing fop reports.
> Thanks in advance Jacopo
> Marco

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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (OFBIZ-338) Conversion of Manufacturing Jasper Reports to Fop

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)
     [ http://issues.apache.org/jira/browse/OFBIZ-338?page=all ]

Marco Risaliti updated OFBIZ-338:
---------------------------------

    Attachment: ShipmentWorkEffortTasks.fo.ftl
                ShipmentLabel.bsh
                ShipmentPlanStockReport.bsh

> Conversion of Manufacturing Jasper Reports to Fop
> -------------------------------------------------
>
>                 Key: OFBIZ-338
>                 URL: http://issues.apache.org/jira/browse/OFBIZ-338
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>          Components: manufacturing
>    Affects Versions: SVN trunk
>            Reporter: Marco Risaliti
>            Priority: Minor
>         Attachments: manufacturing_reports.patch, ShipmentLabel.bsh, ShipmentLabel.fo.ftl, ShipmentPlanStockReport.bsh, ShipmentPlanStockReport.fo.ftl, ShipmentWorkEffortTasks.fo.ftl
>
>
> Hi Jacopo,
> I have converted three manufacturing reports from Jasper Report to Fop and this one of the last steps for removing definitely Jaspert Reports libraries from SVN.
> In this patch I have corrected also the createProductionRunsForOrder method that the productId parameter is no necessary and the wrong parameters numbers passed to the method getProductionRunTotResQty.
> I have done also some changes for the I18n and some changes to Italian translation (like Ciclo di Produzione into Ordine di Produzione).
> The cuttingReport doesn't run because the uiLabelMap was missing but now seems to be corrected.
> If you can see this issue when you have time at disposal I will write the steps for apply those changes.
> 1. Apply the patch manufacturing_reports.patch
> 2. Add the files ShipmentLabel.fo.ftl, ShipmentPlanStockReport.fo.ftl, ShipmentWorkEffortTasks.fo.ftl into the folder applications\manufacturing\webapp\manufacturing\reports.
> 3. Add the files ShipmentLabel.bsh, ShipmentPlanStockReport.bsh, ShipmentWorkEffortTasks.bsh into the folder applications\manufacturing\webapp\manufacturing\WEB-INF\actions\reports
> 4. When everythings is ok, you can also remove the following files used by the old manufacturing JasperReports :
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReportPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReport.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabelPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabel.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasksPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasks.xml
>  
> If everything will be commit If you want I can create a new issue and relative patch for deleting all the reference to Jasper Report already present into the sources.
> P.S.: I will attach also three screenshoots of the results of the new manufacturing fop reports.
> Thanks in advance Jacopo
> Marco

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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (OFBIZ-338) Conversion of Manufacturing Jasper Reports to Fop

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)
     [ http://issues.apache.org/jira/browse/OFBIZ-338?page=all ]

Marco Risaliti updated OFBIZ-338:
---------------------------------

    Attachment: ShipmentWorkEffortTasks.bsh
                ShipmentLabel.pdf
                ShipmentPlanStockReport.pdf

> Conversion of Manufacturing Jasper Reports to Fop
> -------------------------------------------------
>
>                 Key: OFBIZ-338
>                 URL: http://issues.apache.org/jira/browse/OFBIZ-338
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>          Components: manufacturing
>    Affects Versions: SVN trunk
>            Reporter: Marco Risaliti
>            Priority: Minor
>         Attachments: manufacturing_reports.patch, ShipmentLabel.bsh, ShipmentLabel.fo.ftl, ShipmentLabel.pdf, ShipmentPlanStockReport.bsh, ShipmentPlanStockReport.fo.ftl, ShipmentPlanStockReport.pdf, ShipmentWorkEffortTasks.bsh, ShipmentWorkEffortTasks.fo.ftl, ShipmentWorkEffortTasks.pdf
>
>
> Hi Jacopo,
> I have converted three manufacturing reports from Jasper Report to Fop and this one of the last steps for removing definitely Jaspert Reports libraries from SVN.
> In this patch I have corrected also the createProductionRunsForOrder method that the productId parameter is no necessary and the wrong parameters numbers passed to the method getProductionRunTotResQty.
> I have done also some changes for the I18n and some changes to Italian translation (like Ciclo di Produzione into Ordine di Produzione).
> The cuttingReport doesn't run because the uiLabelMap was missing but now seems to be corrected.
> If you can see this issue when you have time at disposal I will write the steps for apply those changes.
> 1. Apply the patch manufacturing_reports.patch
> 2. Add the files ShipmentLabel.fo.ftl, ShipmentPlanStockReport.fo.ftl, ShipmentWorkEffortTasks.fo.ftl into the folder applications\manufacturing\webapp\manufacturing\reports.
> 3. Add the files ShipmentLabel.bsh, ShipmentPlanStockReport.bsh, ShipmentWorkEffortTasks.bsh into the folder applications\manufacturing\webapp\manufacturing\WEB-INF\actions\reports
> 4. When everythings is ok, you can also remove the following files used by the old manufacturing JasperReports :
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReportPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReport.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabelPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabel.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasksPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasks.xml
>  
> If everything will be commit If you want I can create a new issue and relative patch for deleting all the reference to Jasper Report already present into the sources.
> P.S.: I will attach also three screenshoots of the results of the new manufacturing fop reports.
> Thanks in advance Jacopo
> Marco

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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (OFBIZ-338) Conversion of Manufacturing Jasper Reports to Fop

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)
     [ http://issues.apache.org/jira/browse/OFBIZ-338?page=all ]

Marco Risaliti updated OFBIZ-338:
---------------------------------

    Attachment: ShipmentWorkEffortTasks.pdf

> Conversion of Manufacturing Jasper Reports to Fop
> -------------------------------------------------
>
>                 Key: OFBIZ-338
>                 URL: http://issues.apache.org/jira/browse/OFBIZ-338
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>          Components: manufacturing
>    Affects Versions: SVN trunk
>            Reporter: Marco Risaliti
>            Priority: Minor
>         Attachments: manufacturing_reports.patch, ShipmentLabel.bsh, ShipmentLabel.fo.ftl, ShipmentLabel.pdf, ShipmentPlanStockReport.bsh, ShipmentPlanStockReport.fo.ftl, ShipmentPlanStockReport.pdf, ShipmentWorkEffortTasks.bsh, ShipmentWorkEffortTasks.fo.ftl, ShipmentWorkEffortTasks.pdf
>
>
> Hi Jacopo,
> I have converted three manufacturing reports from Jasper Report to Fop and this one of the last steps for removing definitely Jaspert Reports libraries from SVN.
> In this patch I have corrected also the createProductionRunsForOrder method that the productId parameter is no necessary and the wrong parameters numbers passed to the method getProductionRunTotResQty.
> I have done also some changes for the I18n and some changes to Italian translation (like Ciclo di Produzione into Ordine di Produzione).
> The cuttingReport doesn't run because the uiLabelMap was missing but now seems to be corrected.
> If you can see this issue when you have time at disposal I will write the steps for apply those changes.
> 1. Apply the patch manufacturing_reports.patch
> 2. Add the files ShipmentLabel.fo.ftl, ShipmentPlanStockReport.fo.ftl, ShipmentWorkEffortTasks.fo.ftl into the folder applications\manufacturing\webapp\manufacturing\reports.
> 3. Add the files ShipmentLabel.bsh, ShipmentPlanStockReport.bsh, ShipmentWorkEffortTasks.bsh into the folder applications\manufacturing\webapp\manufacturing\WEB-INF\actions\reports
> 4. When everythings is ok, you can also remove the following files used by the old manufacturing JasperReports :
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReportPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReport.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabelPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabel.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasksPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasks.xml
>  
> If everything will be commit If you want I can create a new issue and relative patch for deleting all the reference to Jasper Report already present into the sources.
> P.S.: I will attach also three screenshoots of the results of the new manufacturing fop reports.
> Thanks in advance Jacopo
> Marco

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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (OFBIZ-338) Conversion of Manufacturing Jasper Reports to Fop

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)
     [ http://issues.apache.org/jira/browse/OFBIZ-338?page=all ]

Jacopo Cappellato reassigned OFBIZ-338:
---------------------------------------

    Assignee: Jacopo Cappellato

> Conversion of Manufacturing Jasper Reports to Fop
> -------------------------------------------------
>
>                 Key: OFBIZ-338
>                 URL: http://issues.apache.org/jira/browse/OFBIZ-338
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>          Components: manufacturing
>    Affects Versions: SVN trunk
>            Reporter: Marco Risaliti
>         Assigned To: Jacopo Cappellato
>            Priority: Minor
>         Attachments: manufacturing_reports.patch, ShipmentLabel.bsh, ShipmentLabel.fo.ftl, ShipmentLabel.pdf, ShipmentPlanStockReport.bsh, ShipmentPlanStockReport.fo.ftl, ShipmentPlanStockReport.pdf, ShipmentWorkEffortTasks.bsh, ShipmentWorkEffortTasks.fo.ftl, ShipmentWorkEffortTasks.pdf
>
>
> Hi Jacopo,
> I have converted three manufacturing reports from Jasper Report to Fop and this one of the last steps for removing definitely Jaspert Reports libraries from SVN.
> In this patch I have corrected also the createProductionRunsForOrder method that the productId parameter is no necessary and the wrong parameters numbers passed to the method getProductionRunTotResQty.
> I have done also some changes for the I18n and some changes to Italian translation (like Ciclo di Produzione into Ordine di Produzione).
> The cuttingReport doesn't run because the uiLabelMap was missing but now seems to be corrected.
> If you can see this issue when you have time at disposal I will write the steps for apply those changes.
> 1. Apply the patch manufacturing_reports.patch
> 2. Add the files ShipmentLabel.fo.ftl, ShipmentPlanStockReport.fo.ftl, ShipmentWorkEffortTasks.fo.ftl into the folder applications\manufacturing\webapp\manufacturing\reports.
> 3. Add the files ShipmentLabel.bsh, ShipmentPlanStockReport.bsh, ShipmentWorkEffortTasks.bsh into the folder applications\manufacturing\webapp\manufacturing\WEB-INF\actions\reports
> 4. When everythings is ok, you can also remove the following files used by the old manufacturing JasperReports :
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReportPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReport.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabelPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabel.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasksPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasks.xml
>  
> If everything will be commit If you want I can create a new issue and relative patch for deleting all the reference to Jasper Report already present into the sources.
> P.S.: I will attach also three screenshoots of the results of the new manufacturing fop reports.
> Thanks in advance Jacopo
> Marco

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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (OFBIZ-338) Conversion of Manufacturing Jasper Reports to Fop

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)
     [ http://issues.apache.org/jira/browse/OFBIZ-338?page=all ]

Jacopo Cappellato closed OFBIZ-338.
-----------------------------------

    Resolution: Fixed

Marco,

this is really a great contribution, thanks.
Your patch is in svn with rev. 451270

About removing JasperReports stuff: I think that there are just two (Jasper) reports left (in the order component)... once they are gone we can simply remove the line:

<handler name="jasperreportspdf" type="view" class="org.ofbiz.webapp.view.JasperReportsPdfViewHandler"/>

in the order component controller.xml file; after this is done, we will not get warning messages at startup and I think that JasperReport conversion will be completed: there is no need to remove the other classes (it's better to leave the older tools in even if they are not used).

Again, thanks,

Jacopo

> Conversion of Manufacturing Jasper Reports to Fop
> -------------------------------------------------
>
>                 Key: OFBIZ-338
>                 URL: http://issues.apache.org/jira/browse/OFBIZ-338
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>          Components: manufacturing
>    Affects Versions: SVN trunk
>            Reporter: Marco Risaliti
>         Assigned To: Jacopo Cappellato
>            Priority: Minor
>         Attachments: manufacturing_reports.patch, ShipmentLabel.bsh, ShipmentLabel.fo.ftl, ShipmentLabel.pdf, ShipmentPlanStockReport.bsh, ShipmentPlanStockReport.fo.ftl, ShipmentPlanStockReport.pdf, ShipmentWorkEffortTasks.bsh, ShipmentWorkEffortTasks.fo.ftl, ShipmentWorkEffortTasks.pdf
>
>
> Hi Jacopo,
> I have converted three manufacturing reports from Jasper Report to Fop and this one of the last steps for removing definitely Jaspert Reports libraries from SVN.
> In this patch I have corrected also the createProductionRunsForOrder method that the productId parameter is no necessary and the wrong parameters numbers passed to the method getProductionRunTotResQty.
> I have done also some changes for the I18n and some changes to Italian translation (like Ciclo di Produzione into Ordine di Produzione).
> The cuttingReport doesn't run because the uiLabelMap was missing but now seems to be corrected.
> If you can see this issue when you have time at disposal I will write the steps for apply those changes.
> 1. Apply the patch manufacturing_reports.patch
> 2. Add the files ShipmentLabel.fo.ftl, ShipmentPlanStockReport.fo.ftl, ShipmentWorkEffortTasks.fo.ftl into the folder applications\manufacturing\webapp\manufacturing\reports.
> 3. Add the files ShipmentLabel.bsh, ShipmentPlanStockReport.bsh, ShipmentWorkEffortTasks.bsh into the folder applications\manufacturing\webapp\manufacturing\WEB-INF\actions\reports
> 4. When everythings is ok, you can also remove the following files used by the old manufacturing JasperReports :
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReportPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentPlanStockReport.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabelPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentLabel.xml
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasksPrepare.bsh
> applications\manufacturing\webapp\manufacturing\jobshopmgt\ShipmentWorkEffortTasks.xml
>  
> If everything will be commit If you want I can create a new issue and relative patch for deleting all the reference to Jasper Report already present into the sources.
> P.S.: I will attach also three screenshoots of the results of the new manufacturing fop reports.
> Thanks in advance Jacopo
> Marco

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