Re: Validating an XSL-FO

[Stijn Van Vreckem]

Kurt,

I've posted a work around to your problem a few days ago. 
You must change the fop jar from cocoon version 
0.20.3rc with the latest version 0.20.3.

Stijn

On Fri, 5 Apr 2002, Hahn Kurt (CHA) wrote:

 I'm trying to produce PDF-documents, and I'm really desperate. For a while,
 I tried to apply some minor changes to a previously working XSL, and all I
 get since then is the Acrobat message The file is damaged and could not be
 repaired. However, if I choose xml as ouput instead, everything looks fine
 to me, I get a well-formed document. Is there a way I can validate such a
 document? I mean something similar to a compiler, that tells me at least
 WHERE in the document the error occurred?
 
 Thanks
 
 -
 Please check that your question has not already been answered in the
 FAQ before posting. http://xml.apache.org/cocoon/faqs.html
 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-- 

Stijn Van Vreckem





-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: fo2pdf serializer

[Stijn Van Vreckem]

I had a similar problem, my stylesheet was running from command line and 
produced the pdf. 
Within cocoon it gave some errors and produced no output. 

I changed the fop jar from cocoon (version 0.20.3rc with the latest 
version 0.20.3 ) and everything was running again ! 
  


On Tue, 2 Apr 2002, cyril vidal wrote:

 Good evening,
 
 I've got problems with transforming an xml document (CinemaFO.xml) into a pdf one 
(CinemaFO.pdf) via an xslt transformation (CinemaFO.xsl).
 I'm sure CinemaFO.xml and Cinema.xsl are valid because I've tested them by command 
line with fop 0.20.3
 
 To test my samples with Cocoon2, I've created a new clean environment, also a new 
directory under $CATALINA_HOME/webapps/ , e.g. essai. 
 Under essai, I've created  the following repertory structure:  /static (including 
the file CinemaFO.xml and index.html) and transforms(including the file 
CinemaFO.xsl), and I've also copied over both $COCOON_HOME/cocoon.xconf and the 
$COCOON_HOME/WEB-INF directory.
 
 The structure of my sitemap.xmap file (in directory essai) is following:
 
 map:pipelines
   map:pipeline
  map:match pattern=index.html
 map:read src=static/index.html mime-type=text/html/
  /map:match
   /map:pipeline
 
   map:pipeline
 map:match pattern=CinemaFO.xml
   map:generate src=static/CinemaFO.xml/
   map:transform src=transforms/CinemaFO.xsl/
map:serialize type=fo2pdf/
 /map:match
   /map:pipeline
 
 Theres is no problem with serving static document index.html.
 But when I try to perform the xslfo transformation by requesting the 
URL:http://localhost:8080/essai/CinemaFO.xml, I've got any message error (It means 
the server finds the files) but the browser (IE6) stays completely white. With 
Netscape 6, the browser opens Acrobat reader, but there's a message error, that 
indicates that an error occured at the opening of the pdf document.
 
 What do you think is wrong?
 Thanks a lot for your answers,
 Cyril.
 
 

-- 

Stijn Van Vreckem





-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]