the output of the stylesheet lokks like that:
<?xml version="1.0" encoding="UTF-8"?>
<out>
<checkEnvironmentExtension>
<EnvironmentCheck version="$Revision: 1.19 $">
<environment>
<item key="version.DOM.draftlevel">2.0fd</item>
<item key="java.class.path">/usr/lib/j2sdk1.4.1_02/lib/tools.jar:/home/vam/ apps/tomcat/bin/bootstrap.jar</item>
<item key="version.JAXP">1.1</item>
<item key="java.ext.dirs">/usr/lib/j2sdk1.4.1_02/jre/lib/ext</item>
<foundJar desc="apis.jar-apparent.version" name="xml">xml-apis.jar present-unknown-version</foundJar>
<foundJar desc="apis.jar-path" name="xml">/home/vam/apps/tomcat/common/endorsed/xml-apis.jar</ foundJar>
<item key="version.xerces2">Xerces-J 2.4.0</item>
<item key="version.xerces1">not-present</item>
<item key="version.xalan2_2">Xalan Java 2.5.0</item>
<item key="version.xalan1">not-present</item>
<item key="version.ant">Apache Ant version 1.5.1 compiled on October 2 2002</item>
<item key="java.version">1.4.1_02</item>
<item key="version.DOM">2.0</item>
<item key="version.crimson">present-unknown-version</item>
<item key="sun.boot.class.path">
/home/vam/apps/tomcat/common/endorsed/xml-apis.jar:/home/vam/apps/ tomcat/common/endorsed/xsltc-20030211.jar:/home/vam/apps/tomcat/common/ endorsed/xalan-2.5.0.jar:/home/vam/apps/tomcat/common/endorsed/ xercesImpl-2.4.0.jar:/usr/lib/j2sdk1.4.1_02/jre/lib/rt.jar:/usr/lib/ j2sdk1.4.1_02/jre/lib/i18n.jar:/usr/lib/j2sdk1.4.1_02/jre/lib/ sunrsasign.jar:/usr/lib/j2sdk1.4.1_02/jre/lib/jsse.jar:/usr/lib/ j2sdk1.4.1_02/jre/lib/jce.jar:/usr/lib/j2sdk1.4.1_02/jre/lib/ charsets.jar:/usr/lib/j2sdk1.4.1_02/jre/classes</item>
<item key="version.SAX">2.0</item>
<item key="version.xalan2x">Xalan Java 2.5.0</item>
</environment>
<status result="OK" />
</EnvironmentCheck>
</checkEnvironmentExtension>
</out>
Do you see any conflicts or potential problems?
Thank you!
--mv
On 20.01.2004 00:54, Joerg Heinicke wrote:
On 19.01.2004 20:26, Markus Vaterlaus wrote:
Hello all,
today I encountered a strange behaviour in the XPath Directory Generator. I was using it on a directory with about 600 files. If I was specifying the attribute value for the parameter xpath as root ("/", see below), the generated output could only be processed by cocoon in a transformer generating an html page.
...
<map:generate type="xpathdirectory" src="content">
<map:parameter name="xpath" value="/"/>
<map:parameter name="xmlFiles" value="\.x.*$"/>
</map:generate>
...
Using the same generator with an other matcher to generate a PDF did not work: An error message was shown, stating that "fo:flow needs block level children". However, using content view, manually saving the resulting file and transforming it worked. After quite a while I changed the value of xpath from "/" to "/therootelement" and everything worked fine. Is there a bug in the xpath directory generator or am I doing something wrong?
Such behaviour often points to problem with the XML libraries. What does the environment check say? Try the stylesheet at http://xml.apache.org/xalan-j/faq.html#environmentcheck.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
