FOP issue

[Jacques Le Roux]

Hi All,

It seems that we have an issue with FOP.
Please have a look at
https://demo.hotwaxmedia.com/ordermgr/control/order.pdf?orderId=DEMO10090
or
https://demo.hotwaxmedia.com/ordermgr/control/shipGroups.pdf?orderId=DEMO10090&shipGroupSeqId=00001

I tried to understand, while working on https://issues.apache.org/jira/browse/OFBIZ-1775 but ran out of time.
At least, at ApacheFopWorker[146] : transformer.setURIResolver(new LocalResolver(transformer.getURIResolver()));
transformer.getURIResolver() returns null

Jacques

[Jacopo Cappellato-3]

Jacques,

thanks for your report and research... it was actually an issue that I  
introduced when I have enhanced (yesterday) the implementation of the  
platform-dependent element... sorry for this.
The problem was that I forgot to change the template type from html to  
xsl-fo
I have fixed everything in rev. 660107
However, after the upgrade, custom and external screen definitions  
will have to be updated as well and this could be annoying... for this  
reason in rev. 660108 I've added code to let the old screens to work  
(and print a warning message in the log).

Jacopo


On May 25, 2008, at 10:54 PM, Jacques Le Roux wrote:

> Hi All,
>
> It seems that we have an issue with FOP.
> Please have a look at
> https://demo.hotwaxmedia.com/ordermgr/control/order.pdf?orderId=DEMO10090
> or
> https://demo.hotwaxmedia.com/ordermgr/control/shipGroups.pdf?orderId=DEMO10090&shipGroupSeqId=00001
>
> I tried to understand, while working on https://issues.apache.org/jira/browse/OFBIZ-1775 
>  but ran out of time.
> At least, at ApacheFopWorker[146] : transformer.setURIResolver(new  
> LocalResolver(transformer.getURIResolver()));
> transformer.getURIResolver() returns null
>
> Jacques

[Jacques Le Roux]

Hi Jacopo,

Thanks for your quick fix

Jacques

From: "Jacopo Cappellato" <[hidden email]>

> Jacques,
>
> thanks for your report and research... it was actually an issue that I  
> introduced when I have enhanced (yesterday) the implementation of the  
> platform-dependent element... sorry for this.
> The problem was that I forgot to change the template type from html to  
> xsl-fo
> I have fixed everything in rev. 660107
> However, after the upgrade, custom and external screen definitions  
> will have to be updated as well and this could be annoying... for this  
> reason in rev. 660108 I've added code to let the old screens to work  
> (and print a warning message in the log).
>
> Jacopo
>
>
> On May 25, 2008, at 10:54 PM, Jacques Le Roux wrote:
>
>> Hi All,
>>
>> It seems that we have an issue with FOP.
>> Please have a look at
>> https://demo.hotwaxmedia.com/ordermgr/control/order.pdf?orderId=DEMO10090
>> or
>> https://demo.hotwaxmedia.com/ordermgr/control/shipGroups.pdf?orderId=DEMO10090&shipGroupSeqId=00001
>>
>> I tried to understand, while working on https://issues.apache.org/jira/browse/OFBIZ-1775 
>>  but ran out of time.
>> At least, at ApacheFopWorker[146] : transformer.setURIResolver(new  
>> LocalResolver(transformer.getURIResolver()));
>> transformer.getURIResolver() returns null
>>
>> Jacques
>