Maven Doxia

Problem with Tables, Doxia, APT Maven site and PDF/RTF generation

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1.1
  • Fix Version/s: 1.1.1
  • Component/s: Book, Module - FO, Module - Itext
  • Labels:
    None
  • Environment:
    OSX 10.5.7, Maven 2.1.0, Java 5
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

When running the attached project I get:

~/Documents/java/apache-maven-2.1.0/bin/mvn clean; ~/Documents/java/apache-maven-2.1.0/bin/mvn site
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building doxia-site-test
[INFO] task-segment: [clean]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory .../doxia-site-test/target
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Fri Jun 05 10:54:46 CEST 2009
[INFO] Final Memory: 3M/7M
[INFO] ------------------------------------------------------------------------
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building doxia-site-test
[INFO] task-segment: [site]
[INFO] ------------------------------------------------------------------------
[INFO] [doxia:render-books {execution: default}]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] com.lowagie.text.Table
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.ClassCastException: com.lowagie.text.Table
at com.lowagie.text.xml.SAXiTextHandler.handleEndingTags(Unknown Source)
at com.lowagie.text.xml.SAXiTextHandler.endElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.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 org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at com.lowagie.text.xml.XmlParser.go(Unknown Source)
at com.lowagie.text.xml.XmlParser.parse(Unknown Source)
at com.lowagie.text.xml.XmlToXXX.parse(Unknown Source)
at org.apache.maven.doxia.module.itext.ITextUtil.writePdf(ITextUtil.java:118)
at org.apache.maven.doxia.book.services.renderer.PdfBookRenderer.renderXML(PdfBookRenderer.java:50)
at org.apache.maven.doxia.book.services.renderer.AbstractITextBookRenderer.renderBook(AbstractITextBookRenderer.java:163)
at org.apache.maven.doxia.book.DefaultBookDoxia.renderBook(DefaultBookDoxia.java:142)
at org.apache.maven.doxia.plugin.DoxiaRenderBooksMojo.execute(DoxiaRenderBooksMojo.java:265)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Jun 05 10:54:51 CEST 2009
[INFO] Final Memory: 8M/15M
[INFO] ------------------------------------------------------------------------
bash-3.2$ pwd
.../doxia-site-test

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Siveton added a comment -

This problem occurs with the anchor in the table caption.
The fo and itext sink should take care of this.

Show
Vincent Siveton added a comment - This problem occurs with the anchor in the table caption. The fo and itext sink should take care of this.
Hide
Permalink
Nathan Sowatskey added a comment -

Hi

Thanks for looking at this. Does this mean that the anchor markers around the table title cannot be supported?

Or does it mean that they should be supported and that a fix will be available as a consequence of planned work?

Or ...?

Sorry, I am just not sure what I should do next:

  • Remove the anchors
  • Await a fix
  • Look for a fix that exists

Regards

Nathan

Show
Nathan Sowatskey added a comment - Hi Thanks for looking at this. Does this mean that the anchor markers around the table title cannot be supported? Or does it mean that they should be supported and that a fix will be available as a consequence of planned work? Or ...? Sorry, I am just not sure what I should do next:
  • Remove the anchors
  • Await a fix
  • Look for a fix that exists
Regards Nathan
Hide
Permalink
Vincent Siveton added a comment -

I fixed the itext sink in r782017, snapshot deployed, please retry.
We need to fix the fo sink.

Show
Vincent Siveton added a comment - I fixed the itext sink in r782017, snapshot deployed, please retry. We need to fix the fo sink.
Hide
Permalink
Nathan Sowatskey added a comment -

Fiixed! Thanks

Show
Nathan Sowatskey added a comment - Fiixed! Thanks
Hide
Permalink
Vincent Siveton added a comment -

fixed the fo sink in r782221

Show
Vincent Siveton added a comment - fixed the fo sink in r782221

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.