Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 60142 invoked by uid 500); 10 Dec 2001 15:52:55 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 60119 invoked from network); 10 Dec 2001 15:52:54 -0000 Reply-To: From: "Matthias Fischer" To: Subject: RE: XSLT transformations with Cocoon (added clearer formulation) Date: Mon, 10 Dec 2001 16:52:20 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-UIDL: Eh@"!>!n"!G%,!!*B*"! X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <4.3.1.1.20011210095739.00b76520@mail.dti.net> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N That was real quick, David. Thanks. I'll clarify: 1. In Tomcat [4] we have set the destination type to , as you have suggested. The following problems have arisen: - Internet Explorer gets into Cocoon's way and wants to open the xml file when I click onto it to start the transformation. We haven't found a way to stop IE doing that. - Alternatively, we have set Tomcat to , producing an html output with the option of (a) viewing the source code, (b) copy it to the clipboard, (c) paste it into an empty xml file using some XML editor, (d) saving the xml file in the xml editor. This (a)..(d) does not seem satisfactory at all. We need the xml output as an xml file, to further process it. Therefore, we'd prefer to - set the destination type to - click on the xml file or any other destination file from inside the browser TO START THE TRANSFORMATION - have our xml editor open the xml file produced by the transformation or, alternatively, view the xml sourcecode directly in the browser or, alternatively, have an xml file dropped unviewed somewhere in a specified destination folder. Is this possible, and if it is, how? 2. The other question I tried to get over before was this: When we embarked in FOP transformation we didn't expect so many problems linked to the processor. However, we got lots of problems with non-existing or even wrong documentation, non-working functions or functions working under some very specific conditions. Is the state of realization of XML2XML with Cocoon [2] satisfactory under this aspect? Or would anybody advise me to use rather a different processor? Thanks for your answer(s) in advance, Matthias -----Original Message----- From: David Rosenstrauch [mailto:darose@dti.net] Sent: Monday, December 10, 2001 4:00 PM To: cocoon-users@xml.apache.org Subject: Re: XSLT transformations with Cocoon I'm not sure I understand your question, so I'll try to answer as best I can: * Is it possible to use cocoon to do an XSLT transformation with the output being XML? Yes. [...] DR --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: