DO NOT REPLY [Bug 41443] [PATCH] FOP can't handle mixed-case hyphenation exceptions
https://issues.apache.org/bugzilla/show_bug.cgi?id=41443 Glenn Adams gad...@apache.org changed: What|Removed |Added Priority|P3 |P2 --- Comment #4 from Glenn Adams gad...@apache.org 2012-04-11 03:22:04 UTC --- increase priority for bugs with a patch -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 41443] [PATCH] FOP can't handle mixed-case hyphenation exceptions
https://issues.apache.org/bugzilla/show_bug.cgi?id=41443 --- Comment #3 from Glenn Adams gl...@skynav.com 2012-04-07 01:42:01 UTC --- resetting P2 open bugs to P3 pending further review -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 41443] [PATCH] FOP can't handle mixed-case hyphenation exceptions
https://issues.apache.org/bugzilla/show_bug.cgi?id=41443 Glenn Adams gl...@skynav.com changed: What|Removed |Added Priority|P2 |P3 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681 Glenn Adams gl...@skynav.com changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #9 from Glenn Adams gl...@skynav.com 2012-04-01 06:18:40 UTC --- batch transition to closed; if someone wishes to restore one of these to resolved in order to perform a verification step, then feel free to do so -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 37505] SEVERE FOP Exceptions should be thrown!
https://issues.apache.org/bugzilla/show_bug.cgi?id=37505 Glenn Adams gl...@skynav.com changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from Glenn Adams gl...@skynav.com 2012-04-01 06:53:00 UTC --- batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49727] Upgrade exceptions from fop 0.95 to fop 1.0 (generate tiff output)
https://issues.apache.org/bugzilla/show_bug.cgi?id=49727 Glenn Adams gl...@skynav.com changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #2 from Glenn Adams gl...@skynav.com 2012-04-01 13:42:29 UTC --- batch transition to closed for remaining resolved bugs -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681
--- Comment #8 from Marc Lang marc.l...@ggc.scot.nhs.uk 2011-10-14 16:21:31
UTC ---
I am getting this error using the below ANT task.
?xml version=1.0 encoding=UTF-8?
project name=FOPAnt default=generate-pdf-from-transform basedir=.
property name=fop.home
value=D:\Dev\Java\libraries\fop-1.0-bin\fop-1.0/
taskdef name=fop classname=org.apache.fop.tools.anttasks.Fop
classpath
fileset dir=${fop.home}/lib
include name=*.jar/
/fileset
fileset dir=${fop.home}/build
include name=*.jar/
/fileset
/classpath
/taskdef
target name=generate-pdf-from-transform description=Generates a single PDF
file from an XSLT stylesheet
fop format=image/tiff force=true
userconfig=D:\Dev\Java\FopConverter\workspace\FopConverterService\fop.xconf
xmlfile=D:\Dev\Java\FopConverter\workspace\TestFiles\EDIS_SCIDischarge.xml
xsltfile=D:\Dev\Java\FopConverter\workspace\Stylesheets\EDIS.fo
outfile=D:\Dev\Java\FopConverter\workspace\FopConverterService\something.tif
/
/target
/project
As you can see, the contents of D:\Dev\Java\libraries\fop-1.0-bin\fop-1.0\build
are included in the CLASSPATH, which includes jai_imageio.jar
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681 Marc Lang marc.l...@ggc.scot.nhs.uk changed: What|Removed |Added CC||marc.l...@ggc.scot.nhs.uk -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681 Murthy murthy.m...@caprusit.com changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution||FIXED --- Comment #7 from Murthy murthy.m...@caprusit.com 2010-09-05 02:31:43 EDT --- (In reply to comment #6) Should have thought about it earlier. We're talking about TIFF export, so another work-around: Install JAI ImageIO Tools to give ImageIO a TIFF codec which it hasn't by default. http://jai-imageio.dev.java.net/ So, I guess that's an important clue. Could it be that you had JAI ImageIO Tools installed but didn't add that when upgrading to FOP 1.0? Otherwise, I still can't explain that the error should have appeared when switching to FOP 1.0. Hi Maerki, Yes you are right, JAI ImageIO tools were missing from my classpath which results in error. After placing the JAI ImageIO tool, able to generate the TIFF successfully. Thanks for all your help. Thanks Murthy -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681 Jeremias Maerki jerem...@apache.org changed: What|Removed |Added CC||ruud.verd...@pinkroccade.nl --- Comment #3 from Jeremias Maerki jerem...@apache.org 2010-09-02 02:59:19 EDT --- *** Bug 49727 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49727] Upgrade exceptions from fop 0.95 to fop 1.0 (generate tiff output)
https://issues.apache.org/bugzilla/show_bug.cgi?id=49727 Jeremias Maerki jerem...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE OS/Version||All --- Comment #1 from Jeremias Maerki jerem...@apache.org 2010-09-02 02:59:18 EDT --- *** This bug has been marked as a duplicate of bug 49681 *** -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681
Jeremias Maerki jerem...@apache.org changed:
What|Removed |Added
Version|0.95|1.0
--- Comment #4 from Jeremias Maerki jerem...@apache.org 2010-09-02 03:10:21
EDT ---
The actual exception:
case DataBuffer.TYPE_INT:
case DataBuffer.TYPE_FLOAT:
if(sampleSize[0] != 32) {
throw new Error(TIFFImageEncoder4);
}
Ugly as hell but this has been so since TIFFImageEncoder has been introduced
into Batik. Anyway, the error probably happens because INT is used as sample
carrier but I assume the sample size is only 24 bits.
One change that happened from 0.95 to 1.0 was the introduction of the new
intermediate format so that TIFF output is now handled by TIFFDocumentHandler
instead of TIFFRenderer by default, but both classes use the same ImageWriter
API from XML Graphics Commons. The default color type (RGBA) has remained the
same. So I'm not sure where this comes from. I'll have to try to reproduce.
A possibility in the meantime is to try different color format settings:
http://xmlgraphics.apache.org/fop/1.0/output.html#bitmap-configuration
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681 Jeremias Maerki jerem...@apache.org changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #5 from Jeremias Maerki jerem...@apache.org 2010-09-02 03:21:27 EDT --- Ok, on my side, the ImageIO implementation for ImageWriter is used which doesn't show this problem. If I disable the ImageIO implementation the internal codec becomes active and fails on the default configuration settings with said exception. Now, the question is why the ImageIO implementation isn't used. Maybe it has to do with Bug 49696 but I don't really think so. So my next question: What JVM are running this on so you get this result? That might help me figure out why the internal codecs are selected over the ImageIO implementations. In this light, another work-around presents itself: In xmlgraphics-commons.jar you can edit META-INF/services/org.apache.xmlgraphics.image.writer.ImageWriter and remove the following entries: org.apache.xmlgraphics.image.writer.internal.PNGImageWriter org.apache.xmlgraphics.image.writer.internal.TIFFImageWriter org.apache.xmlgraphics.image.writer.internal.JPEGImageWriter -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681 --- Comment #6 from Jeremias Maerki jerem...@apache.org 2010-09-02 03:36:12 EDT --- Should have thought about it earlier. We're talking about TIFF export, so another work-around: Install JAI ImageIO Tools to give ImageIO a TIFF codec which it hasn't by default. http://jai-imageio.dev.java.net/ So, I guess that's an important clue. Could it be that you had JAI ImageIO Tools installed but didn't add that when upgrading to FOP 1.0? Otherwise, I still can't explain that the error should have appeared when switching to FOP 1.0. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49727] Upgrade exceptions from fop 0.95 to fop 1.0 (generate tiff output)
https://issues.apache.org/bugzilla/show_bug.cgi?id=49727 Ruud ruud.verd...@pinkroccade.nl changed: What|Removed |Added OS/Version||Windows 7 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49727] New: Upgrade exceptions from fop 0.95 to fop 1.0 (generate tiff output)
https://issues.apache.org/bugzilla/show_bug.cgi?id=49727 Summary: Upgrade exceptions from fop 0.95 to fop 1.0 (generate tiff output) Product: Fop Version: 1.0 Platform: PC Status: NEW Severity: blocker Priority: P2 Component: images AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: ruud.verd...@pinkroccade.nl We have the same problem like Bug 49681. The second errornumber is: org.apache.xmlgraphics.image.codec.tiff.TIFFImageEncoder.encodeMultiple(TIFFImageEncoder.java:165) (Bug 49681 reported org.apache.xmlgraphics.image.codec.tiff.TIFFImageEncoder.finishMultiple(TIFFImageEncoder.java:186) ) -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681 Pascal Sancho pascal.san...@takoma.fr changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Pascal Sancho pascal.san...@takoma.fr 2010-08-02 03:08:05 EDT --- no exception log is attached, please give further information. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681 Murthy murthy.m...@caprusit.com changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #2 from Murthy murthy.m...@caprusit.com 2010-08-02 04:44:51 EDT --- I'm sorry that the attachment is not uploaded, sorry for the inconvenience caused. Below is the exception == java.lang.Error: TIFFImageEncoder4 at org.apache.xmlgraphics.image.codec.tiff.TIFFImageEncoder.encode(TIFFImageEncoder.java:245) at org.apache.xmlgraphics.image.codec.tiff.TIFFImageEncoder.finishMultiple(TIFFImageEncoder.java:186) at org.apache.xmlgraphics.image.writer.internal.TIFFImageWriter$TIFFMultiImageWriter.close(TIFFImageWriter.java:206) at org.apache.fop.render.bitmap.AbstractBitmapDocumentHandler.endDocument(AbstractBitmapDocumentHandler.java:174) at org.apache.fop.render.intermediate.IFRenderer.stopRenderer(IFRenderer.java:285) at org.apache.fop.area.RenderPagesModel.endDocument(RenderPagesModel.java:256) at org.apache.fop.area.AreaTreeHandler.endDocument(AreaTreeHandler.java:309) at org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:164) at net.sf.saxon.event.ContentHandlerProxy.close(ContentHandlerProxy.java:274) at net.sf.saxon.event.ProxyReceiver.close(ProxyReceiver.java:90) at net.sf.saxon.event.ReceivingContentHandler.endDocument(ReceivingContentHandler.java:218) at org.apache.xerces.parsers.AbstractSAXParser.endDocument(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl.endEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.endEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.skipSpaces(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:371) at net.sf.saxon.event.Sender.send(Sender.java:185) at net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:29) Note: xml-apis-ext-1.3.04.jar it is also part of core Jars Thanks MVVR Murthy -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49681] New: Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681 Summary: Upgrade Exceptions from fop 0.95 to 1.o Product: Fop Version: 0.95 Platform: PC OS/Version: Windows Vista Status: NEW Severity: normal Priority: P2 Component: images AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: murthy.m...@caprusit.com i tried to upgrade from 0.95 to 1.0 version, and getting the exception attached when generating the TIFF image. These are my changes 0.95 jars 1.0 upgrade changes = fop0.95.jar - fop1.0.jar xercesImpl-2.6.2.jar - xercesImpl-2.7.1.jar xmlgraphics-commons-1.3.1.jar - xmlgraphics-commons-1.4.jar other Jars using = xalan-2.7.0.jar batik-all-1.7.jar avalon-framework-4.2.0.jar barcode4j-fop-ext-complete.jar please help me out in this problem Thanks Murthy -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 49681] Upgrade Exceptions from fop 0.95 to 1.o
https://issues.apache.org/bugzilla/show_bug.cgi?id=49681 Murthy murthy.m...@caprusit.com changed: What|Removed |Added Severity|normal |critical -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: Assert vs Exceptions [was: svn commit: r731248 - in /xmlgraphics/fop/trunk: ./ src/documentation/content/xdocs/trunk/ src/foschema/ src/java/org/apache/fop/fonts/ src/java/org/apache/fop/fonts/aut
Jeremias Maerki wrote:
On 07.01.2009 12:36:34 Vincent Hennebert wrote:
Jeremias Maerki wrote:
Hi Vincent
On 07.01.2009 11:47:16 Vincent Hennebert wrote:
Hi Jeremias,
Author: jeremias
Date: Sun Jan 4 04:59:29 2009
New Revision: 731248
snip/
+/**
+ * Sets the requested encoding mode for this font.
+ * @param mode the new encoding mode
+ */
+public void setEncodingMode(EncodingMode mode) {
+if (mode == null) {
+throw new NullPointerException(mode must not be null);
+}
+this.encodingMode = mode;
+}
snip/
if (type1) {
+if (encodingMode == EncodingMode.CID) {
+throw new IllegalArgumentException(
+CID encoding mode not supported for Type 1 fonts);
+}
I’d rather use assert statements instead. Anything wrong with that?
Nothing, it's a matter of taste. For these cases here, I prefer
exceptions.
No big deal of course, but let me just explain my view of assert vs
exception:
- if the error is due to an illegal use of the library, I use an assert
and expect the developer to test his program with assertions enabled,
debug it and then put it in production with assertions disabled. That
saves some checking overhead.
- if the error is due to some external cause (missing resource, invalid
URL, etc.) then an exception is to be used.
I don’t know the context, but in this case it seemed to correspond to
the first situation, hence my question.
Vincent
I understand your reasoning, but looking around on the net, I find that
best practice seems to be to use explicit checks for parameters of
public methods and asserts only for private methods and code consistency
checks. That basically matches my understanding of the facility and how
I try to use it.
http://docs.sun.com/app/docs/doc/806-7930/6jgp65iks?a=view#assert-13
http://www.jfasttrack.com/whitePapers/assertions.html
http://goliath.ecnext.com/coms2/gi_0199-1331586/Using-assertions-in-Java-building.html
Thanks for the links. Indeed that makes sense to use exceptions in
public methods; but then they need to appear in the javadoc I think,
even if they are unchecked exceptions.
I’ll apply that convention from now on. But to be honest, I’m not too
keen on constantly checking for e.g. null arguments. I guess it’s all
a matter of how ‘obvious’ this is that the argument must not be null...
Vincent
DO NOT REPLY [Bug 37505] SEVERE FOP Exceptions should be thrown!
https://issues.apache.org/bugzilla/show_bug.cgi?id=37505 Jeremias Maerki jerem...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #2 from Jeremias Maerki jerem...@apache.org 2009-01-02 07:17:55 PST --- With the event facility [1] in FOP Trunk you can now intercept such errors and throw an exception if you want. Not everyone wants to stop processing early if an image is missing or faulty. The event ID of the error in your particular case would be org.apache.fop.svg.SVGEventProducer.svgNotBuilt. Your requirement was one of the reason for implementing the event facility. HTH [1] http://xmlgraphics.apache.org/fop/trunk/events.html -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 37505] SEVERE FOP Exceptions should be thrown!
https://issues.apache.org/bugzilla/show_bug.cgi?id=37505 --- Comment #1 from M.H. [EMAIL PROTECTED] 2008-10-01 08:53:11 PST --- *push* This still occurs with FOP 0.95. Errors like -- ... The URI file:/c:/temp/reports/C_V10276_PropRegion_Overview_S.svg on element image can't be opened because: ... -- should throw an exception to the FOP caller. Silently logging is not very helpful. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 41443] New: - [PATCH] FOP can't handle mixed-case hyphenation exceptions
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41443. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41443 Summary: [PATCH] FOP can't handle mixed-case hyphenation exceptions Product: Fop Version: 0.93 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: [EMAIL PROTECTED] FOP can't handle mixed-case words (for example German nouns) as hyphenation exceptions, for example Dateiname (file name) which is hyphenated as Datein-ame (Datei-name would be correct). The words in the stoplist are mixed-case. However, when FOP checks if there's an hyphenation exception for a certain word (that is, it is in the stop list), all the characters of the word have already been converted to lowercase. Therefore mixed-case words in the stoplist cannot be found. With the attached patch applied, FOP enters the exception words in lowercase into the stop list. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 41443] - [PATCH] FOP can't handle mixed-case hyphenation exceptions
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41443. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41443 --- Additional Comments From [EMAIL PROTECTED] 2007-01-23 10:00 --- Created an attachment (id=19443) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=19443action=view) Patch to convert exceptions to lower-case -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: svn commit: r397562 [2/6] - in /xmlgraphics/fop/trunk/src/sandbox: META-INF/services/ org/apache/fop/render/afp/ org/apache/fop/render/afp/apps/ org/apache/fop/render/afp/exceptions/ org/apache/fo
[EMAIL PROTECTED] wrote: Added: .../fop/render/afp/exceptions/NestedRuntimeException.java ^^ Ow. Don't we have that already somewhere else in the code? J.Pietschmann
DO NOT REPLY [Bug 37505] New: - SEVERE FOP Exceptions should be thrown!
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=37505. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=37505 Summary: SEVERE FOP Exceptions should be thrown! Product: Fop Version: 0.20.5 Platform: Other OS/Version: Windows 2000 Status: NEW Severity: critical Priority: P2 Component: svg AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: [EMAIL PROTECTED] I trace a bug because I saw the following exception in my log file. After inspecting my code, I noticed that this is just a log entry probably written by FOP/Batik ... the exception itself wasn't thrown further to my calling application. At least for the new FOP 1.0 version, such exceptions shouldn't be swalled by FOP - a SEVERE problem should always result in an Exception for the calling application. 2005-11-15 10:14:35.277 SEVERE Thread-227: svg graphic could not be built: file:/c:/temp/TJ9VV4pz1+FP0cz0bG6gDtdoar7QLGq0bTMTGOQ5bd4=/Perf.svg:28 The attribute 'transform' of the element path is invalid org.apache.batik.bridge.BridgeException: file:/c:/temp/TJ9VV4pz1+FP0cz0bG6gDtdoar7QLGq0bTMTGOQ5bd4=/Perf.svg:28 The attribute 'transform' of the element path is invalid at org.apache.batik.bridge.SVGUtilities.convertTransform(SVGUtilities.java:852) at org.apache.batik.bridge.AbstractGraphicsNodeBridge.createGraphicsNode (AbstractGraphicsNodeBridge.java:92) at org.apache.batik.bridge.SVGShapeElementBridge.createGraphicsNode (SVGShapeElementBridge.java:50) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:182) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:148) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:188) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:148) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:188) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:148) at org.apache.batik.bridge.GVTBuilder.build(GVTBuilder.java:120) at org.apache.batik.bridge.SVGImageElementBridge.createSVGImageNode (SVGImageElementBridge.java:328) at org.apache.batik.bridge.SVGImageElementBridge.createGraphicsNode (SVGImageElementBridge.java:118) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:182) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:148) at org.apache.batik.bridge.GVTBuilder.build(GVTBuilder.java:76) at org.apache.fop.render.pdf.PDFRenderer.renderSVGDocument(PDFRenderer.java:590) at org.apache.fop.render.pdf.PDFRenderer.renderSVGArea(PDFRenderer.java:549) at org.apache.fop.svg.SVGArea.render (SVGArea.java:98) at org.apache.fop.render.pdf.PDFRenderer.renderForeignObjectArea (PDFRenderer.java:533) at org.apache.fop.layout.inline.ForeignObjectArea.render(ForeignObjectArea.java:89) at org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRenderer.java:516) at org.apache.fop.layout.LineArea.render (LineArea.java:519) at org.apache.fop.render.AbstractRenderer.renderBlockArea (AbstractRenderer.java:485) at org.apache.fop.layout.BlockArea.render(BlockArea.java:117) at org.apache.fop.render.AbstractRenderer.renderBlockArea (AbstractRenderer.java:485) at org.apache.fop.layout.BlockArea.render(BlockArea.java:117) at org.apache.fop.render.AbstractRenderer.renderAreaContainer (AbstractRenderer.java:451) at org.apache.fop.layout.AreaContainer.render(AreaContainer.java:88) at org.apache.fop.render.AbstractRenderer.renderAreaContainer (AbstractRenderer.java:451
Re: Exceptions
Today, 15 November 2005, revision 344223 only gives an exception on the first test file. Simon On Thu, Sep 01, 2005 at 02:45:30PM +0200, Finn Bock wrote: Hi Running the NIST test suite I get 2 table related exceptions and 1 KnuthElement related exception: java.lang.NullPointerException org.apache.fop.layoutmgr.table.GridUnit.resolveBorder(GridUnit.java:246) org.apache.fop.layoutmgr.table.GridUnit.resolveBorder(GridUnit.java:230) org.apache.fop.layoutmgr.table.TableRowIterator.resolveStartEndBorders(TableRowIterator.java:480) org.apache.fop.layoutmgr.table.TableRowIterator.buildGridRow(TableRowIterator.java:419) org.apache.fop.layoutmgr.table.TableRowIterator.prefetchNext(TableRowIterator.java:294) ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=test-page-master margin-right=1.0in margin-bottom=1.0in margin-top=0.2in margin-left=1.0in page-width=8.5in page-height=11in fo:region-body margin-bottom=1.0in margin-right=1.0in margin-top=0.2in margin-left=1.0in/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=test-page-master fo:flow flow-name=xsl-region-body fo:block space-after.optimum=0.4in space-after.maximum=0.4in This test evaluates the border-before-color property on a table-body FO. The border-before-color property (see red border) for the next table-body FO was set to red. /fo:block fo:table border-collapse=collapse-with-precedence fo:table-body border-before-style=solid border-before-color=red fo:table-row fo:table-cell fo:block The border above should be red. /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:flow /fo:page-sequence /fo:root -- Simon Pepping home page: http://www.leverkruid.nl
Re: Exceptions
No surprise, actually. The tables all use the collapsing border model. But tell me, have they updated the NIST test suite for XSL Rec 1.0? I remember that at a stand-still in working-draft stage (master-name instead of master-reference). On 01.09.2005 14:45:30 Finn Bock wrote: Hi Running the NIST test suite I get 2 table related exceptions and 1 KnuthElement related exception: java.lang.NullPointerException org.apache.fop.layoutmgr.table.GridUnit.resolveBorder(GridUnit.java:246) org.apache.fop.layoutmgr.table.GridUnit.resolveBorder(GridUnit.java:230) org.apache.fop.layoutmgr.table.TableRowIterator.resolveStartEndBorders(TableRowIterator.java:480) org.apache.fop.layoutmgr.table.TableRowIterator.buildGridRow(TableRowIterator.java:419) org.apache.fop.layoutmgr.table.TableRowIterator.prefetchNext(TableRowIterator.java:294) ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=test-page-master margin-right=1.0in margin-bottom=1.0in margin-top=0.2in margin-left=1.0in page-width=8.5in page-height=11in fo:region-body margin-bottom=1.0in margin-right=1.0in margin-top=0.2in margin-left=1.0in/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=test-page-master fo:flow flow-name=xsl-region-body fo:block space-after.optimum=0.4in space-after.maximum=0.4in This test evaluates the border-before-color property on a table-body FO. The border-before-color property (see red border) for the next table-body FO was set to red. /fo:block fo:table border-collapse=collapse-with-precedence fo:table-body border-before-style=solid border-before-color=red fo:table-row fo:table-cell fo:block The border above should be red. /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:flow /fo:page-sequence /fo:root java.lang.NullPointerException org.apache.fop.layoutmgr.table.TableContentLayoutManager$RowPainter.addAreasForCell(TableContentLayoutManager.java:885) org.apache.fop.layoutmgr.table.TableContentLayoutManager$RowPainter.addAreasAndFlushRow(TableContentLayoutManager.java:864) org.apache.fop.layoutmgr.table.TableContentLayoutManager.addAreas(TableContentLayoutManager.java:642) org.apache.fop.layoutmgr.table.TableLayoutManager.addAreas(TableLayoutManager.java:296) ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=test-page-master margin-right=1.0in margin-bottom=1.0in margin-top=0.2in margin-left=1.0in page-width=8.5in page-height=11in fo:region-body margin-bottom=1.0in margin-right=1.0in margin-top=0.2in margin-left=1.0in/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=test-page-master fo:flow flow-name=xsl-region-body fo:table fo:table-column column-width=1.0in/ fo:table-column column-width=1.0in/ fo:table-body fo:table-row fo:table-cell background-color=red fo:blockThis cell spans one row/fo:block /fo:table-cell /fo:table-row fo:table-row fo:table-cell number-rows-spanned=2 background-color=aqua fo:blockThis cells spans two rows/fo:block /fo:table-cell /fo:table-row fo:table-row fo:table-cell background-color=aqua fo:block/ /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:flow /fo:page-sequence /fo:root java.lang.ClassCastException org.apache.fop.layoutmgr.inline.ContentLayoutManager.getNextKnuthElements(ContentLayoutManager.java:282) org.apache.fop.layoutmgr.inline.LeaderLayoutManager.getLeaderInlineArea(LeaderLayoutManager.java:150) org.apache.fop.layoutmgr.inline.LeaderLayoutManager.get(LeaderLayoutManager.java:77) org.apache.fop.layoutmgr.inline.LeaderLayoutManager.getNextKnuthElements(LeaderLayoutManager.java:255) ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=test-page-master margin-right=1.0in margin-bottom=1.0in margin-top=0.2in margin-left=1.0in page-width=8.5in page-height=11in fo:region-body margin-bottom=1.0in margin-right=1.0in margin-top=0.2in margin-left=1.0in/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=test-page-master fo:flow flow-name=xsl-region-body fo:block space-after.optimum=0.4in space-after.maximum=0.4inThe leader-pattern property of the leader FO below was set to use-content(set to *)./fo:block fo:block text-align=startEntry 1fo:leader leader-pattern=use-content leader-length.optimum=1.0in leader-length.maximum=1.0in*/fo:leaderPage 1/fo:block /fo:flow /fo:page-sequence /fo:root Jeremias Maerki
Re: Exceptions
[Jeremias] No surprise, actually. The tables all use the collapsing border model. But tell me, have they updated the NIST test suite for XSL Rec 1.0? I remember that at a stand-still in working-draft stage (master-name instead of master-reference). Years back, when we last talked about the NIST suite, the author of the suite gave a link to a new version of the suite. Last I checked, it was the old version that was available on their webpage. regards, finn
