[From nobody Fri Aug 6 17:08:07 2004 Return-Path: <MerrilG@ibsplc.com> Received: from alias2.acm.org ([199.222.69.92]) by wanamaker.mail.atl.earthlink.net (Earthlink Mail Service) with ESMTP id 187Z2r2ZF3Nl3oJ0 for <servlets@mindspring.com>; Sat, 2 Nov 2002 09:14:10 -0500 (EST) Received: from gw018 ([203.129.250.164]) by alias2.acm.org (ACM Email Forwarding Service) with SMTP id CRY73883 for <jhunter@ACM.org>; Sat, 02 Nov 2002 09:14:11 -0500 Subject: Help: XSLT To: jhunter@ACM.org X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: <OFC99ED02C.057DDB51-ON65256C65.004D2BE4@ibsplc.com> From: MerrilG@ibsplc.com Date: Sat, 2 Nov 2002 19:49:38 +0530 X-MIMETrack: Serialize by Router on Green/IBS(Release 5.0.5 |September 22, 2000) at 11/02/2002 07:49:39 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Mozilla-Status2: 00000000 Dear Jason, I read your article on JDOM in Oramag last month and saw that the next part would be on XSLT and Xpath in JDOM. I would be grateful if you could solve a problem that I am facing in XML-XSL.. I am developing a system by extending the Struts framework for XML-XSL. I modified the code for our purpose from stxx (that is using JDOM) as you would know is an m2x extension on Struts. The majority of the user community of this application will be using IE5.5 or above. So in this case I decided that I could go for the XSLT at the browser. In most of the pages there is an <xsl:import .. > tag which I use to import other pages just as the <jsp:include...> An example would be <xsl:import href="../ACCHeader.jsp?menu=T"/> This jsp would emit diffreent html depending on the logged on users and this header was part of the older version of our application that was using the traditional struts framewrok with JSP's and custom tags. The above mentioned import facility of xsl works when the XSLT is at the browser level. But 8-10 pages are hosted in the internet where we cannot specify the browser. People may use Netscape. For such users I do the XSLT at the server. Everything works fine except for the import tag. XSLT engine at the server thinks that the file is in the server's local directory. That is if I am using tomcat, the JVM's root directory would be tomcat's bin directory. So the XSLT searches for the particular file used in the import tag from the server's hard disk. Hence I always get the message in tomcat's console, that the file doesnot exist. I can hardcode the server address and url of the page, but that would not be right. How can we make the XSLT engine at the server to use the url of the incoming request while parsing the xsl:import tag. regards Merrill George Disclaimer: "The information in this e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. It should not be used by anyone who is not the original intended recipient. If you have erroneously received this message, please delete it immediately and notify the sender. The recipient acknowledges that IBS or IBS Group like any other large global corporation, are unable to exercise total control or ensure or guarantee the integrity of contents of the information contained in individual e-mail transmissions and the recipient acknowledges that any views expressed in this message may be those of the individual sender and no binding nature of the message shall be implied or assumed unless the sender does so expressly with due authority of IBS Group. Before opening any attachments please check them for viruses and defects." ]