Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 46612 invoked by uid 500); 17 May 2001 13:59:18 -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 46541 invoked from network); 17 May 2001 13:59:04 -0000 From: "Per Kreipke" To: Subject: [C1] JAXP and Xalan 1.3.1 Date: Thu, 17 May 2001 10:04:18 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Has anyone else tried to get Cocoon 1 to work with a JAXP parsers and transformers? I know that C2 will work that way but I thought it might be easy to get C1 to work with it too. Specifically, I needed Xalan 1.3.1 for some other dependencies and I found that it's now missing the liasons necessary to work with C1. So, instead I wrote my own JAXPParser and JAXPTransformer classes to try to plug the new Xalan in. I was partially successful: they invoke, but the transformer won't pass any of my existing XSP or XSL files as valid. Anyone else try this? Per. --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: