Re: Problems upgrading to FOP 0.20.3
OK, great comments. I had forgotten to update the included syle sheet. Unfortunately, still problems. Now I get the following error: [ERROR]: Logger not set [INFO]: building formatting object tree [INFO]: [1] [WARN]: table-layout=auto is not supported, using fixed! [WARN]: table-layout=auto is not supported, using fixed! [INFO]: [2] java.lang.RuntimeException: java.lang.NullPointerException So now the NullPointerException is back. Worse yet, when I run the transformed XSL:FO through the command line, it works OK. Why isn't it working within the servlet environment?? Am there more JARs I need to add to the classpath?? For what it's worth, the xsl:fo appears below. http://www.w3.org/1999/XSL/Format";> Cover Page Preferred Insured, Inc. Eveluation Date: 00/00/ Report Description: Monthly Loss Report Look and Feel: High Level Coverage Report Type: One Time Report Format: Detail Reporting Level: Occurence Claim Status: Inception Date Filter by Date: Inception Date Open Claim Begin and End Dates: 00/00/-00/00/ Closed Claim Begin and End Dates: 00/00/-00/00/ Show Claiment Name: Yes Incured Filter: None Policies Included: CC12345678, EE12345677 Coverages Included: Liability, Auto, Workers Comp Locations Included: 1004, 1297, 1020 Coverage Detail Filter On: Policy Inception Date Prefered Insured, Inc Open Claim Range: 00/00/-00/00/
Re: Problems upgrading to FOP 0.20.3
[EMAIL PROTECTED] wrote: [ERROR]: Logger not set This can be sefaly ignored. [INFO]: building formatting object tree java.lang.RuntimeException: org.apache.fop.apps.FOPException: 'master-reference' for 'fo:page-sequence'matches no 'simple-page-master' or 'page-sequence-master' There is a fo:page-sequence which probably uses still master-name instead of master-reference. In case it helps, the xsl:fo style sheet appears below. The result of the transformation is almost always of more help than the style sheet, especially after unnecessary stuff has been deleted. Because of: No such file. No template matching this element. Probably in the included file. This is most likely the problem, because in order to make sense, the template has to produce a fo:page-sequence, which you most likely forgot to update. J.Pietschmann
Re: Problems upgrading to FOP 0.20.3
of Occurences:
Recovery
*
*
*
*
*
Info Here
Incurred
*
*
Info Here
Info Here
Info Here
Claim Category:
Loss Description:
Christian Geisert
<[EMAIL PROTECTED]To: [EMAIL PROTECTED]
su-gmbh.de> cc:
Subject: Re: Problems
upgrading to FOP 0.20.3
06/20/2002 02:43 PM
Please respond to
fop-user
[EMAIL PROTECTED] schrieb:
> Hello,
>
> I am trying to upgrade from FOP 0.20.1 0.20.3. As per the release notes,
> changing "master-name" properties to "master-reference" eliminated some
> errors.
You did change to much .. read again ;-)
(or see below)
> I running FOP in a servlet environment on WebSphere 3.5.3, which I
believe
> runs JDK 1.2.2. The same stylesheet and everything worked on 0.20.1.
>
> Does anybody know what the problem is? The stylesheet appears below.
This
Re: Problems upgrading to FOP 0.20.3
[EMAIL PROTECTED] schrieb: Hello, I am trying to upgrade from FOP 0.20.1 0.20.3. As per the release notes, changing "master-name" properties to "master-reference" eliminated some errors. You did change to much .. read again ;-) (or see below) I running FOP in a servlet environment on WebSphere 3.5.3, which I believe runs JDK 1.2.2. The same stylesheet and everything worked on 0.20.1. Does anybody know what the problem is? The stylesheet appears below. This Christian
