RE: Cocoon 1.8.2 and FOP 0.20.4
Do you know if new Cocoon 2.0 supports the new FOP ? Even though I think cocoon and APIs such as FOP are great the general trend that I seem to finding is that the software tends not to be backward compatable which sometimes make it difficult in a corporate environment. Thanks for your assistance! -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 4:57 PM To: [EMAIL PROTECTED] Subject: Re: Cocoon 1.8.2 and FOP 0.20.4 George Pieri wrote: Should I be able to change 1) the fop_0_15_0.jar to the new fop.jar FOP's API evolved quite significantly between 0.15 and 0.20.4, with major changes between 0.20.1 and 0.20.2. I don't expect the new jar to work with an old Cocoon wrapper. J.Pietschmann - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cocoon 1.8.2 and FOP 0.20.4
Has anyone gotten FOP 0.20.4 to work with Cocoon 1.8.2 Should I be able to change 1) the fop_0_15_0.jar to the new fop.jar 2) modify the cocoon properties file formatter.type.text/xslfo = org.apache.cocoon.formatter.FO2PDFFormatter and then use the new fo ??? Thanks in advance! - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CDATA output / Server Upgrage
In alot of our xsl stylesheets we wrap xml and javascrip within !CDATA[ ]] tags so that it is not parsed. This has worked well for us with the output being delivered successfully. Using the new version of our web server, Weblogic 7.0, this appears no longer to work and our CDATA sections get interperted and changed to lt; x gt; tags !?! What could be affecting this. Any ideas ? e.g. --- xsl code maintag/maintag ![CDATA[maintag/maintag]] - output maintag/maintag lt;maintaggt;lt;/maintaggt; -- output in previous version of web server maintag/maintag maintag/maintag - 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]
Output Data as XML output
I have XML that I would like to generate XML from using my XSL stylesheet. I've tried using the cocoon format command ?cocoon-format type=text/xhtml? and ?cocoon-format type=text/xml? with NO luck it appears that my output is still coming back in HTML format !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0//EN http://www.w3.org/TR/REC-html40/strict.dtd; and my processing instruction does NOT appear in the output. The xsl:output command does not appear to work as well. Do I have any options available for Cocoon 1.8.2 ? Do I have the cocoon-format command in the wrong syntax ? Thanks in advance - 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]
Can Coocoon not parse elements
Is there a way besides wrapping each column with CDATA to tell cocoon or the xml parser NOT to parse the ELEMENTS defined in the XML ? All our data comes from the database and some of the columns at times may have the special characters (e.g. ) so in order to resolve this issue we wrap the data within the !CDATA[ ]] tag. This however makes the XML string MUCH larger than it needs to be because wrapping every column multipled by the number of rows produces alot of extra text. My thought was to build a DTD for the data coming back from the database telling the parser NOT to parse the content by defining the ELEMENT as a CDATA type or some type that will allow these characters. Unfortunately CDATA cannot be used for ELEMENTs. Question --- !DOCTYPE DATA [ !ELEMENT DATA ANY --- Produces error because of ] DATA GRENADA CW /DATA !DOCTYPE DATA [ !ELEMENT DATA ] DATA GRENADA CW /DATA - 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]
