search

hydralix / docbkx-tools

Automatically exported from code.google.com/p/docbkx-tools
0 stars 0 forks source link

fo:flow is missing child elements #47

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. mvn install

What is the expected output? What do you see instead?
Expected: Finished HTML and PDF files.
Instead: Error building:

[INFO] Failed to transform to PDF

Embedded error: org.apache.fop.fo.ValidationException: null:1:45993: 
Error(1/45993): fo:flow is 
missing child elements. 
Required Content Model: marker* (%block;)+

What version of the product are you using? On what operating system?
2.0.9 and 2.0.10-SNAPSHOT, linux

Please provide any additional information below.
This project had been building fine with docbkx-maven-plugin 2.0.8 for a long 
time, but 
recently we've started seeing this error:

[INFO] Trace
java.lang.ClassCastException: java.lang.String
        at com.agilejava.docbkx.maven.ExpressionUtils.splitToTree(ExpressionUtils.java:40)
        at com.agilejava.docbkx.maven.ExpressionUtils.splitToTree(ExpressionUtils.java:43)
        at com.agilejava.docbkx.maven.ExpressionUtils.createTree(ExpressionUtils.java:31)
        at 
com.agilejava.docbkx.maven.AbstractTransformerMojo$1.<init>(AbstractTransformerM
ojo.java:
151)
        at 
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:1
48)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:483)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecutor.java:
678)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Def
aultLifecycleEx
ecutor.java:540)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycle
Executor.java:5
19)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecy
cleExecutor.java:371)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecu
tor.java:332)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.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:362)
        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a: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)

...and found the fix described in issue 20:
  http://code.google.com/p/docbkx-tools/issues/detail?id=20

I tried updating to 2.0.9 and get the failure mentioned above.  2.0.10-SNAPSHOT 
shows the 
same behavior.

I've tried disabling our custom fo, and it doesn't seem to help.

Attached is the project.

Original issue reported on code.google.com by rangerr...@gmail.com on 24 Feb 2010 at 7:18

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi,

I think I found, I tried validating the document using "XML Mind XML Editor" 
and I saw it was not conforming to docbook 5 schema.
I modified the source to use docbook 4.4 and it does generate well (it is still 
not valid against 4.4 but it works)

Here is what I modified:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
]>
<book xmlns:xlink="http://www.w3.org/1999/xlink"
      xmlns:xi="http://www.w3.org/2001/XInclude">

Can you tell me if this solution works for you?

Regards,
Mimil

Original comment by MimilO...@gmail.com on 14 Aug 2010 at 9:57

GoogleCodeExporter commented 8 years ago 
Closing, the issue seems to be related to an invalid docbook file.

Original comment by MimilO...@gmail.com on 19 Aug 2010 at 9:13