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=41448>.
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=41448


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From [EMAIL PROTECTED]  2007-01-25 01:50 -------
The FO generated by docbook contains fo:wrapper elements as direct children of 
fo:flow, e.g.

<fo:wrapper id="id91268">
        <!--index term-->
</fo:wrapper>

In 0.93 this is the cause of the ClassCastException. The ClassCastException 
has been fixed in SVN. But the id attribute has no affect on an fo:wrapper in 
FOP currently. I guess docbook generates this as a placeholder for PDF 
destinations. If you don't care about PDF destinations and just want to 
overcome the ClassCastException then get an SVN client, download the code and 
compile it yourself. If you don't fancy doing that then you may want to tell 
the docbook folks about this problem. Maybe when fop1.extensions is set they 
could skip generating such fo:wrapper elements for PDF Destinations, since PDF 
Destinations aren't supported in FOP anyway.

I'm closing this bug as the ClassCastException is fixed.

-- 
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.

Reply via email to