RE: two more class renamings
-Original Message- From: Glen Mazza [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 9:59 AM 1. fo:static-content is to be repeated from its start on every page, and truncated if it doesn't fit. You state this very simply and clearly here, but it has always struck me curiously. There appears to be a gaping hole in the specification that does not satisfy the need to have content repeat on every page that does *not* truncate when it does not fit. The extent attribute on all regions that surround the page explicitly defines the size, but I've found it interesting that there was not an option to have an auto setting that would resize the region to fit the content. I first thought that this was a 1.0 thing and that in the next version it would be addressed, but this comment you made that explicitly says the desired behavior of static-content is to truncate when it does not fit and that there are no plans to address it. Do you or anyone else on the developer list know of a compelling reason why this is the case? CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --
RE: Print JPEG HeadlessException - Please Help
Just in case it means something, I ran into this problem when java.awt.headless was specified as true on the startup configuration for the OAS platform. Since we were running on a Windows PC we were successfully able to run Batik (and thereby FOP) by just changing java.awt.headless=false (or removing all together). From my investigation at the time (albeit on FOP 0.20.5 and Batik 1.5beta4), the only way to successfully make it work was to run in a non-headless environment. In short, I did not find a way for FOP (and more specifically Batik) to work in a headless environment, regardless of what you set your properties to. -Original Message- From: Surj [mailto:[EMAIL PROTECTED] Sent: Friday, July 18, 2008 4:50 AM To: fop-dev@xmlgraphics.apache.org Subject: Re: Print JPEG HeadlessException - Please Help Looks like this is set for sure. I even tried running with Java 1.5. I think I might be beyond help, time to look for a new trade. Andreas Delmelle-2 wrote: - Oorspronkelijk bericht - Van: Surj [mailto:[EMAIL PROTECTED] Verzonden: vrijdag, juni 13, 2008 09:23 PM Yes the 'java.awt.headless=true' specified as a parameter when starting up the weblogic container, is there any other way of setting this i.e. programmatically during startup. Can you also verify from within your code whether the setting was correctly processed? This you could check via: System.out.print(java.awt.headless= + System.getProperty(java.awt.headless, false)); In theory, you could use System.setProperty(java.awt.headless, true) to set the value, but as is often the case with properties on the system-level, it could be that setting it programmatically has no effect at all. HTH! Cheers Andreas -- View this message in context: http://www.nabble.com/Print-JPEG-HeadlessException---Please-Help-tp17821038p18525612.html Sent from the FOP - Dev mailing list archive at Nabble.com. -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
FOP 0.95 and Maven2
Developers, Are there any plans to push the new FOP 0.95 release to the central Maven repo? Sean Griffin | Clinical Reporting Architect | Cerner Corporation | 816.201.1599 | [EMAIL PROTECTED] | www.cerner.com -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
RE: FOP 0.95 and Maven2
Worked like a charm. Thanks! Any thoughts of publishing the source and javadoc JARs with the binary? I notice this isn't done across the board for some other apache jars I looked at, like xmlgraphics-commons and batik, but it can make debugging issues considerably easier. From: Max Berger [mailto:[EMAIL PROTECTED] On Behalf Of Max Berger Sent: Saturday, September 27, 2008 4:39 PM To: fop-dev@xmlgraphics.apache.org Subject: Re: FOP 0.95 and Maven2 Dear Sean, should be uploaded now, and sync with the main repository within 24 hours. Please let me know if you encounter any problems. Max Am 26.09.2008 um 20:20 schrieb Griffin,Sean: Developers, Are there any plans to push the new FOP 0.95 release to the central Maven repo? Sean Griffin | Clinical Reporting Architect | Cerner Corporation | 816.201.1599 | [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] | www.cerner.com http://www.cerner.com CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
RE: [FOP0.95]Group-by not functioning
Jos, XSLT processing and XSL-FO processing are two completely separate steps. FOP simply provides an XML/XSLT input as a convenience for feeding the result of an XSLT transformation that generates an XSL-FO document as its output directly into FOP. The group-by functionality that you're referencing is only available in an XSLT 2.0-capable processor. The only processor at this time that can do XSLT 2.0 is Saxon 8.x+. When running in XML Spy you must be running the Saxon processor while when running FOP you're likely running what ships with it by default - Xalan - which does not understand XSLT 2.0. If you want to use XSLT 2.0 and want to use the FOP command-line script as your launcher then you'll need to change that script to put Saxon on the classpath instead of Xalan. Sean From: Jos van Roosmalen [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 09, 2008 8:34 AM To: fop-dev@xmlgraphics.apache.org Subject: [FOP0.95]Group-by not functioning Hello, I have a problem with FOP. Consider the stripped down minimal Input XML and XSL below. If I run this group.xsl on input.xml using XMLSpy 2005 I get the expected output: ?xml version=1.0 encoding=UTF-8? Group found: group1Key Group found: group2Key However if I run it using FOP 0.95 with: fop -xml input.xml -xsl group.xsl -foout test.fo It is complaining about the current-grouping-index(): SystemId Unknown; Line #6; Column #64; function token not found. If I remove that current-grouping-index(), and only print Group Found: xsl:for-each-group select=item group-by=[EMAIL PROTECTED]'48'] Group found /xsl:for-each-group I expect 2 times Group found but I end with an *empty* XML File: ?xml version=1.0 encoding=UTF-8? Questions: 1. Why is current-grouping-index() not working? 2. Why is even group-by not working? 3. How to get this working? Thanks you, Jos ?xml version=1.0 encoding=ISO-8859-1? !-- group.xsl -- xsl:stylesheet version=2.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:template match=items xsl:for-each-group select=item group-by=[EMAIL PROTECTED]'48'] Group found: xsl:value-of select=current-grouping-key()/ /xsl:for-each-group /xsl:template /xsl:stylesheet !-- input.xml -- items itemcolumn index=48 name=mnemogroup1Key/column/item itemcolumn index=48 name=mnemogroup1Key/column/item itemcolumn index=48 name=mnemogroup2Key/column/item /items -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
