Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 27382 invoked from network); 16 Dec 2009 00:33:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Dec 2009 00:33:16 -0000 Received: (qmail 92184 invoked by uid 500); 16 Dec 2009 00:33:16 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 92110 invoked by uid 500); 16 Dec 2009 00:33:15 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 92100 invoked by uid 99); 16 Dec 2009 00:33:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 00:33:15 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 00:33:13 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NKhoy-0003ai-T3 for users@camel.apache.org; Tue, 15 Dec 2009 16:32:52 -0800 Message-ID: <26803542.post@talk.nabble.com> Date: Tue, 15 Dec 2009 16:32:52 -0800 (PST) From: murugess To: users@camel.apache.org Subject: Issue with includes/imports in XSL file MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: msanjay@gmail.com We are using camel-xslt component to do the transformation and it looks like all the includes in the XSL are failing with following error message: SystemId Unknown; Line #3; Column #54; Had IO Exception with stylesheet file: SystemId Unknown; Line #4; Column #49; Had IO Exception with stylesheet file: All the XSLs reside in the same directory. So, relative path should work. I guess SystemId is not set on the source passed to the XSLT implementation library due to which it is not able to know the current path of XSL and ends up looking in the root directory for the imported XSL. We are using the spring-camel version 1.6 for our project. I wonder whether xsl include is failing for everyone or are we making some blunder. Please let me know if xsl includes work for any of you. FYI, here is how I am adding the includes in the XSL: -- View this message in context: http://old.nabble.com/Issue-with-includes-imports-in-XSL-file-tp26803542p26803542.html Sent from the Camel - Users mailing list archive at Nabble.com.