DO NOT REPLY [Bug 41500] ClassCastException after generating FO with an XSLT 1.0 for a PDF output
https://issues.apache.org/bugzilla/show_bug.cgi?id=41500 --- Comment #7 from Andreas L. Delmelle [EMAIL PROTECTED] 2008-04-27 01:46:16 PST --- (In reply to comment #6) FWIW, the following implementation of BlockContainerLayoutManager.wrapPositionElements() seems to fix the issue: Correction: BlockStackingLM.wrapPositionElements()... -- 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 41500] ClassCastException after generating FO with an XSLT 1.0 for a PDF output
https://issues.apache.org/bugzilla/show_bug.cgi?id=41500
--- Comment #6 from Andreas L. Delmelle [EMAIL PROTECTED] 2008-04-27
01:42:48 PST ---
FWIW, the following implementation of
BlockContainerLayoutManager.wrapPositionElements() seems to fix the issue:
---
protected void wrapPositionElements(List sourceList, List targetList,
boolean force) {
ListIterator listIter = sourceList.listIterator();
Object tempElement;
while (listIter.hasNext()) {
tempElement = listIter.next();
if (tempElement instanceof ListElement) {
wrapPositionElement(
(ListElement) tempElement,
targetList,
force);
} else if (tempElement instanceof List) {
wrapPositionElements(
(List) tempElement,
targetList,
force);
}
}
}
---
Haven't committed it, since I still need to do some more thorough checking, and
I'm not sure if this is the best way to avoid this error.
The problem is that the original implementation assumes that all the elements
of the list will be instances of ListElement, where the WrapperLayoutManager
generates an InlineKnuthSequence. This quick and dirty fix simply takes this
possibility into account and changes the behavior in that case.
--
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 41500] ClassCastException after generating FO with an XSLT 1.0 for a PDF output
https://issues.apache.org/bugzilla/show_bug.cgi?id=41500 --- Comment #5 from Lars Marius Garshol [EMAIL PROTECTED] 2008-04-10 05:07:18 PST --- For the record: this bug still exists in FOP 0.94 and 0.95beta. I just ran into it, and only discovered this bug after extensive searching. It would be nice if this bug was fixed. It did not exist in older FOP versions. I was able to work around the problem thanks to the information here, though. -- 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 41500] - ClassCastException after generating FO with an XSLT 1.0 for a PDF output
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=41500. 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=41500 --- Additional Comments From [EMAIL PROTECTED] 2007-01-31 10:48 --- Created an attachment (id=19491) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=19491action=view) FO source do generate the error (transforming to PDF) -- 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 41500] - ClassCastException after generating FO with an XSLT 1.0 for a PDF output
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=41500. 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=41500 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2007-01-31 12:16 --- The problem appears as fo:wrapper is used as a direct child of fo:block-container with block-level content. As documented in http://xmlgraphics.apache.org/fop/compliance.html#fo-object-wrapper fo:wrapper is currently only working properly around inline-level content. The work-around at the moment is to use fo:block instead of fo:wrapper. Let's keep this bug open until the implementation is fully finished for fo:wrapper. Thanks for the test 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.
DO NOT REPLY [Bug 41500] - ClassCastException after generating FO with an XSLT 1.0 for a PDF output
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=41500. 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=41500 --- Additional Comments From [EMAIL PROTECTED] 2007-01-30 15:33 --- Transformation has been made using SAXON 7.9.1 -- 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 41500] - ClassCastException after generating FO with an XSLT 1.0 for a PDF output
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=41500. 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=41500 --- Additional Comments From [EMAIL PROTECTED] 2007-01-30 15:55 --- Any chance of attaching an FO file demonstrating the problem? Not XML + XSLT just plain FO please. -- 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.
