xslt-process-users Mailing List for XSLT-process - Emacs XSLT process/debug (Page 25)
Brought to you by:
ovidiu
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(9) |
Jun
(20) |
Jul
(9) |
Aug
(16) |
Sep
(2) |
Oct
|
Nov
(8) |
Dec
(6) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(5) |
Feb
(8) |
Mar
(2) |
Apr
(22) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(3) |
Dec
|
2003 |
Jan
(6) |
Feb
(3) |
Mar
(3) |
Apr
(4) |
May
(12) |
Jun
(16) |
Jul
(2) |
Aug
(1) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
2004 |
Jan
(5) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(1) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(5) |
2005 |
Jan
|
Feb
|
Mar
(3) |
Apr
(1) |
May
(2) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
2006 |
Jan
(2) |
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(6) |
Jun
(3) |
Jul
(8) |
Aug
(8) |
Sep
(3) |
Oct
(23) |
Nov
(55) |
Dec
(45) |
2007 |
Jan
(8) |
Feb
(11) |
Mar
(6) |
Apr
(11) |
May
(3) |
Jun
(9) |
Jul
(12) |
Aug
(29) |
Sep
(22) |
Oct
(12) |
Nov
(12) |
Dec
(10) |
2008 |
Jan
(7) |
Feb
(6) |
Mar
(34) |
Apr
(22) |
May
(12) |
Jun
(15) |
Jul
(21) |
Aug
(4) |
Sep
(14) |
Oct
(11) |
Nov
(23) |
Dec
(34) |
2009 |
Jan
(9) |
Feb
(8) |
Mar
(9) |
Apr
(16) |
May
(29) |
Jun
(28) |
Jul
(31) |
Aug
(6) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(11) |
2010 |
Jan
(7) |
Feb
(5) |
Mar
(5) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
(6) |
2012 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(1) |
2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2015 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
(1) |
Oct
(2) |
Nov
(4) |
Dec
(5) |
2016 |
Jan
(5) |
Feb
(6) |
Mar
(8) |
Apr
(6) |
May
(5) |
Jun
(2) |
Jul
(5) |
Aug
(6) |
Sep
(12) |
Oct
(7) |
Nov
(8) |
Dec
(2) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(3) |
Oct
(3) |
Nov
(1) |
Dec
(4) |
2018 |
Jan
(6) |
Feb
(6) |
Mar
(18) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2019 |
Jan
|
Feb
|
Mar
(6) |
Apr
(4) |
May
(3) |
Jun
(4) |
Jul
(8) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(1) |
2021 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(4) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
2022 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2023 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
2024 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Ovidiu P. <ov...@xe...> - 2001-06-01 23:43:20
|
Hi Carsten, I've added support for viewing the results of XSLT processing in a browser. Please check it out from the repository. The support right now is rather primitive, the code assumes the output is always HTML. I'll fix this hopefully today. Please let me know how it works for you. Regards, -- Ovidiu Predescu <ov...@cu...> http://orion.nsr.hp.com/ (inside HP's firewall only) http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff) |
From: Frank T. <fra...@in...> - 2001-06-01 09:13:27
|
Hi, ok, it tried it with the "xslt-process-1.2.2.tgz" from your homepage. The same error occurred again with this version. btw, to run the bsh i have to switch from javaw to java with "java-run-set-vm-w" . Cheers Frank > You may want to install 1.2.2, I think this problem was fixed in this > release. Please let me know if you still see it. > > Thanks, > Ovidiu |
From: Ovidiu P. <ov...@xe...> - 2001-06-01 06:48:57
|
I've fixed the problems with GNU Emacs, you may want to do a cvs update and check if it works for you. Greetings, Ovidiu On Tue, 29 May 2001 19:04:34 -0400, Carsten Heinrigs <ca...@oc...> wrote: > Thanks a lot and please keep me updated. > > carst > -- > Carsten Heinrigs > Ocean-7 Development > Tel: 212-533-8460 > > |
From: Carsten H. <ca...@oc...> - 2001-06-01 03:55:07
|
All right!!! Works great so far. carst -- Carsten Heinrigs Ocean-7 Development Tel: 212-533-8460 |
From: Carsten H. <ca...@oc...> - 2001-06-01 03:39:52
|
Thanks a lot and please keep me updated. carst -- Carsten Heinrigs Ocean-7 Development Tel: 212-533-8460 |
From: Ovidiu P. <ov...@xe...> - 2001-06-01 01:20:49
|
You may want to install 1.2.2, I think this problem was fixed in this release. Please let me know if you still see it. Thanks, Ovidiu On Wed, 23 May 2001 12:42:20 +0200, "Frank Taffelt" <fra...@in...> wrote: > Hi > > i tried using xslt-process(1.2.1) under NT with XEmacs (21.1.9). > > when i tried to invoke xslt, i got TokenMgr Error's from bsh . > > i think the error comes from this part: > > xslt.Xalan1.invoke("c:\TEMP\hello-page.xml", "C:\TEMP/xsltoutKEAh-4"); > > it should be > xslt.Xalan1.invoke("c:\\TEMP\\hello-page.xml", "C:\\TEMP\\xsltoutKEAh-4"); > > is this correct or did i something miss ? > > Cheers > Frank > > > > |
From: Matthew C. <mat...@i2...> - 2001-05-14 03:35:49
|
Hi, I started using your xslt-process, and it works great. Thanks for making it available. Unfortunately, most of the xml files I process never have a xsl-stylesheet directive, so adding one when I needed to process it was becoming a pain. Thus I hacked together a little something based on your code in order to read in a xsl (or xml) file from the minibuffer. The prompting works such that a reasonable default is chosen by examining the filenames of visible xml buffers. Thus, if I have both a xml and a xsl file open, and I run xslt-process-invoke in either of them, I only get prompted for a single file, and the prompt has a default value of the other buffer. I also hacked up Xalan1.java to use both values always, and never look for the stylesheet directive, but seeing as how this is probably not what you want, feel free to ignore those changes! Hope this helps, Matt mat...@i2... (defun xslt-process-is-xml-buffer (buffer) "Determines if a buffer is xml" (save-excursion (set-buffer buffer) (string= mode-name "XML"))) (defun xslt-process-get-xml-buffers () "Get a list of the xml buffers open in the current session." (mapcan (lambda (buffer) (if (xslt-process-is-xml-buffer buffer) (list buffer))) (buffer-list))) (defun xslt-process-get-visible-xml-buffers () "Returns a list of visible xml buffers." (delq nil (mapcar (lambda (buffer) (if (get-buffer-window buffer 'visible) buffer)) (xslt-process-get-xml-buffers)))) (defun xslt-process-read-file (prompt) "Reads a filename, using a any other visible xml buffer as a default" (let* ((buffer (car (delete (current-buffer) (xslt-process-get-visible-xml-buffers)))) (default-filename (buffer-file-name buffer))) (read-file-name (concat prompt " (" default-filename "): ") "" default-filename))) (defun xslt-process-read-files-to-process () "Returns list of (xmlfile xslfile) for invoke to operate on" (let* ((currentfile (buffer-file-name)) (isXmlFile (if currentfile (string-match "\.xml$" currentfile))) (isXslFile (if currentfile (string-match "\.xsl$" currentfile)))) (list (if (or isXslFile (not (or isXmlFile isXslFile))) (xslt-process-read-file "XML file to process") (expand-file-name currentfile)) (if (or isXmlFile (not (or isXmlFile isXslFile))) (xslt-process-read-file "Stylesheet to use") (expand-file-name currentfile))))) (defun xslt-process-invoke (&optional xmlFile xslFile) "This is the main function which invokes the XSLT processor of your choice on the current buffer." (interactive (xslt-process-read-files-to-process)) (let* ((temp-directory (or (if (fboundp 'temp-directory) (temp-directory)) (if (boundp 'temporary-file-directory) temporary-file-directory))) (classpath (if (boundp 'jde-global-classpath) jde-global-classpath nil)) (classpath-env (if (getenv "CLASSPATH") (split-string (getenv "CLASSPATH") jde-classpath-separator) nil)) (out-buffer (get-buffer-create "*xslt output*")) (msg-buffer (get-buffer-create "*xslt messages*")) (xslt-jar (concat (xslt-process-find-xslt-directory) "java/xslt.jar")) (tmpfile (make-temp-name (concat temp-directory "/xsltout"))) ; Set the name of the XSLT processor. This is either specified ; in the local variables of the file or is the default one. (xslt-processor (progn ; Force evaluation of local variables (hack-local-variables t) (or (if (and (local-variable-p 'processor (current-buffer)) (boundp 'processor)) (if (stringp processor) processor (symbol-name processor))) (symbol-name (car xslt-process-default-processor)))))) (save-excursion ; Reset any local variables in the source buffer so the next ; time we execute we correctly pick up the default processor ; even if the user decides to remove the local variable (makunbound 'processor) ; Prepare to invoke the Java method to process the XML document (setq jde-global-classpath (mapcar 'expand-file-name (union (append jde-global-classpath (list xslt-jar)) (union xslt-process-additional-classpath classpath-env)))) ; Append the additional arguments to the arguments passed to bsh (setq bsh-vm-args (union xslt-process-jvm-arguments bsh-vm-args)) ; Setup additional arguments to the processor (setq func (get (intern-soft xslt-processor) 'additional-params)) (if (not (null func)) (funcall func)) ; Prepare the buffers (save-some-buffers) (set-buffer msg-buffer) (erase-buffer) (set-buffer out-buffer) (erase-buffer) ; Invoke the processor, displaying the result in a buffer and ; any error messages in an additional buffer (condition-case nil (progn (setq messages (bsh-eval (concat "xslt." xslt-processor ".invoke(\"" xmlFile "\", \"" xslFile "\", \"" tmpfile "\");"))) (setq jde-global-classpath classpath) (if (file-exists-p tmpfile) (progn (set-buffer out-buffer) (insert-file-contents tmpfile) (delete-file tmpfile) (display-buffer out-buffer) (if (not (string= messages "")) (xslt-process-display-messages messages msg-buffer out-buffer)) (message "Done invoking %s." xslt-processor)) (message (concat "Cannot process " (file-name-nondirectory xmlFile) ".")) (xslt-process-display-messages messages msg-buffer out-buffer))) (error (progn (message (concat "Could not process file, most probably " xslt-processor " could not be found!")) (message (concat "Failed to process: " xmlFile " with: " xslFile)) (setq jde-global-classpath classpath))))))) package xslt; import org.apache.xalan.xslt.XSLTProcessorFactory; import org.apache.xalan.xslt.XSLTProcessor; import org.apache.xalan.xslt.XSLTInputSource; import org.w3c.dom.Node; import org.w3c.dom.NamedNodeMap; import org.apache.xalan.xslt.XSLTResultTarget; import org.w3c.dom.ProcessingInstruction; import java.util.Hashtable; import java.util.StringTokenizer; import java.net.URL; import java.io.File; import java.io.InputStream; import java.io.FileOutputStream; import java.io.FileInputStream; public class Xalan1 { public static void invoke(String xmlFilename, String xslFilename, String outFilename) { try { File xmlFile = new File(xmlFilename); File xslFile = new File(xslFilename); if ( !xmlFile.exists() ) { System.out.println("Cannot find xml file: " + xmlFilename); return; } if ( !xslFile.exists() ) { System.out.println("Cannot find xsl file: " + xslFilename); return; } XSLTProcessor processor = XSLTProcessorFactory.getProcessor(); XSLTInputSource xmlDoc = new XSLTInputSource(new FileInputStream(xmlFile)); XSLTInputSource xslDoc = new XSLTInputSource(new FileInputStream(xslFile)); FileOutputStream out = new FileOutputStream(outFilename); // Finally process the XML document through the XSLT processor processor.process(xmlDoc, xslDoc, new XSLTResultTarget(out)); out.close(); } catch(Exception e) { System.out.println("Cannot process: " + e); } } } |
From: Ovidiu P. <ov...@xe...> - 2001-05-13 12:33:35
|
This is a great idea, thanks you for coming up with it! I currently work on the next major release for the code, which has dramatical changes in the source code. I've registered the project at Sourceforge.net, http://sourceforge.net/projects/xslt-process/. Please check out the new source code in the CVS repository (sorry, there is no .tar.gz package for the new code yet). For this new release I was planning to add such a functionality, by giving the option of registering XSLT files. Your approach seems a lot better though because it allows one to run the XSLT processor while editing an XML buffer. So to merge the two approaches, I am thinking of the following: - while visiting an XML or XSLT file, you can use the "XSLT" -> "Register XSLT stylesheet" menu item to register an XSLT file, with the default XSLT file chosen from existing buffers. The registered XSLT stylesheets can then be saved in the options file .emacs persistently. - after you registered the XSLT file, you visit an XML file. If the file has no xml-stylesheet PI, you can associate an XSLT stylesheet to be used using the menu "XSLT" -> "Apply XSLT stylesheet" -> "<stylesheet name>". You need to do the association only once, the association is remembered by Emacs for further invocations. If you want to associate a different XSLT file, you simply select it from the menu. - if the above steps did not happen prior to invoking the processor on an XML file, emacs asks you for the XSLT file to be used and associates it with the XML file. Further invocations of the XSLT processor use the same XSLT file. - when you visit an XSLT buffer and you invoke the XSLT processor, you're asked for an XML buffer on which the XSLT stylesheet should be applied, exactly as in your approach. Does this make sense? What do you think? Regards, Ovidiu On Fri, 11 May 2001 13:16:11 -0500, Matthew Conway <mat...@i2...> wrote: > > Hi, > > I started using your xslt-process, and it works great. Thanks for > making it available. Unfortunately, most of the xml files I process > never have a xsl-stylesheet directive, so adding one when I needed to > process it was becoming a pain. Thus I hacked together a little > something based on your code in order to read in a xsl (or xml) file > from the minibuffer. The prompting works such that a reasonable > default is chosen by examining the filenames of visible xml buffers. > Thus, if I have both a xml and a xsl file open, and I run > xslt-process-invoke in either of them, I only get prompted for a > single file, and the prompt has a default value of the other buffer. > I also hacked up Xalan1.java to use both values always, and never look > for the stylesheet directive, but seeing as how this is probably not > what you want, feel free to ignore those changes! Hope this helps, > > Matt > mat...@i2... > > > (defun xslt-process-is-xml-buffer (buffer) > "Determines if a buffer is xml" > (save-excursion > (set-buffer buffer) > (string= mode-name "XML"))) > > (defun xslt-process-get-xml-buffers () > "Get a list of the xml buffers open in the > current session." > (mapcan (lambda (buffer) > (if (xslt-process-is-xml-buffer buffer) > (list buffer))) > (buffer-list))) > > (defun xslt-process-get-visible-xml-buffers () > "Returns a list of visible xml buffers." > (delq > nil > (mapcar > (lambda (buffer) > (if (get-buffer-window buffer 'visible) buffer)) > (xslt-process-get-xml-buffers)))) > > (defun xslt-process-read-file (prompt) > "Reads a filename, using a any other visible xml buffer as a default" > (let* ((buffer (car > (delete (current-buffer) (xslt-process-get-visible- > xml-buffers)))) > (default-filename (buffer-file-name buffer))) > (read-file-name (concat prompt " (" default-filename "): ") "" default-filename))) > > (defun xslt-process-read-files-to-process () > "Returns list of (xmlfile xslfile) for invoke to operate on" > (let* ((currentfile (buffer-file-name)) > (isXmlFile (if currentfile (string-match "\.xml$" currentfile))) > (isXslFile (if currentfile (string-match "\.xsl$" currentfile)))) > > (list (if (or isXslFile (not (or isXmlFile isXslFile))) > (xslt-process-read-file "XML file to process") > (expand-file-name currentfile)) > (if (or isXmlFile (not (or isXmlFile isXslFile))) > (xslt-process-read-file "Stylesheet to use") > (expand-file-name currentfile))))) > > (defun xslt-process-invoke (&optional xmlFile xslFile) > "This is the main function which invokes the XSLT processor of your > choice on the current buffer." > (interactive (xslt-process-read-files-to-process)) > (let* ((temp-directory > (or (if (fboundp 'temp-directory) (temp-directory)) > (if (boundp 'temporary-file-directory) temporary-file-directory)) > ) > (classpath > (if (boundp 'jde-global-classpath) > jde-global-classpath > nil)) > (classpath-env (if (getenv "CLASSPATH") > (split-string (getenv "CLASSPATH") > jde-classpath-separator) > nil)) > (out-buffer (get-buffer-create "*xslt output*")) > (msg-buffer (get-buffer-create "*xslt messages*")) > (xslt-jar (concat > (xslt-process-find-xslt-directory) "java/xslt.jar")) > (tmpfile (make-temp-name (concat temp-directory "/xsltout"))) > ; Set the name of the XSLT processor. This is either specified > ; in the local variables of the file or is the default one. > (xslt-processor > (progn > ; Force evaluation of local variables > (hack-local-variables t) > (or > (if (and > (local-variable-p 'processor (current-buffer)) > (boundp 'processor)) > (if (stringp processor) > processor > (symbol-name processor))) > (symbol-name (car xslt-process-default-processor)))))) > (save-excursion > ; Reset any local variables in the source buffer so the next > ; time we execute we correctly pick up the default processor > ; even if the user decides to remove the local variable > (makunbound 'processor) > ; Prepare to invoke the Java method to process the XML document > (setq jde-global-classpath > (mapcar 'expand-file-name > (union (append jde-global-classpath (list xslt-jar)) > (union xslt-process-additional-classpath > classpath-env)))) > ; Append the additional arguments to the arguments passed to bsh > (setq bsh-vm-args (union xslt-process-jvm-arguments bsh-vm-args)) > ; Setup additional arguments to the processor > (setq func (get (intern-soft xslt-processor) 'additional-params)) > (if (not (null func)) (funcall func)) > ; Prepare the buffers > (save-some-buffers) > (set-buffer msg-buffer) > (erase-buffer) > (set-buffer out-buffer) > (erase-buffer) > ; Invoke the processor, displaying the result in a buffer and > ; any error messages in an additional buffer > (condition-case nil > (progn > (setq messages (bsh-eval > (concat "xslt." xslt-processor ".invoke(\"" > xmlFile "\", \"" xslFile > "\", \"" tmpfile "\");"))) > (setq jde-global-classpath classpath) > (if (file-exists-p tmpfile) > (progn > (set-buffer out-buffer) > (insert-file-contents tmpfile) > (delete-file tmpfile) > (display-buffer out-buffer) > (if (not (string= messages "")) > (xslt-process-display-messages messages > msg-buffer out-buffer)) > (message "Done invoking %s." xslt-processor)) > (message (concat "Cannot process " > (file-name-nondirectory xmlFile) ".")) > (xslt-process-display-messages messages msg-buffer out-buffer))) > (error (progn > (message > (concat "Could not process file, most probably " > xslt-processor > " could not be found!")) > (message (concat "Failed to process: " xmlFile " with: " xslFile)) > (setq jde-global-classpath classpath))))))) > > > package xslt; > > import org.apache.xalan.xslt.XSLTProcessorFactory; > import org.apache.xalan.xslt.XSLTProcessor; > import org.apache.xalan.xslt.XSLTInputSource; > import org.w3c.dom.Node; > import org.w3c.dom.NamedNodeMap; > import org.apache.xalan.xslt.XSLTResultTarget; > import org.w3c.dom.ProcessingInstruction; > import java.util.Hashtable; > import java.util.StringTokenizer; > import java.net.URL; > import java.io.File; > import java.io.InputStream; > import java.io.FileOutputStream; > import java.io.FileInputStream; > > public class Xalan1 > { > public static void invoke(String xmlFilename, String xslFilename, String outFilename) > { > try > { > File xmlFile = new File(xmlFilename); > File xslFile = new File(xslFilename); > if ( !xmlFile.exists() ) > { > System.out.println("Cannot find xml file: " + xmlFilename); > return; > } > > if ( !xslFile.exists() ) > { > System.out.println("Cannot find xsl file: " + xslFilename); > return; > } > > XSLTProcessor processor = XSLTProcessorFactory.getProcessor(); > XSLTInputSource xmlDoc = new XSLTInputSource(new FileInputStream(xmlFile)); > XSLTInputSource xslDoc = new XSLTInputSource(new FileInputStream(xslFile)); > FileOutputStream out = new FileOutputStream(outFilename); > > // Finally process the XML document through the XSLT processor > processor.process(xmlDoc, xslDoc, new XSLTResultTarget(out)); > out.close(); > } > catch(Exception e) { > System.out.println("Cannot process: " + e); > } > } > > } > > |
From: Jeremy C. <jc...@bh...> - 2001-05-10 11:43:21
|
Thank you for the reply. I have added a pointer to my cocoon.properties file (the same one I use during web development) and recieve the same error, Could not process file, most probably Cocoon1 could not be found! ... You asked for the bsh message window, and after looking at it, I am not sure that it is getting to that point. Here it is: * bsh * cd c:/DEVELOP/jboss_jetty/jetty/webapps/knopro5/ javaw -classpath c:/DEVELOP/emacs/site/jde/java/bsh-commands;c:/DEVELOP/emacs/site/jde/java/l ib/jde.jar;c:/DEVELOP/emacs/site/jde/java/lib/bsh.jar;c:/develop/emacs/site/ java/xslt.jar;c:/DEVELOP/jboss_jetty/jetty/webapps/knopro5;c:/DEVELOP/jboss_ jetty/jetty/lib/cocoon.jar;c:/DEVELOP/jboss_jetty/jetty/lib/xalan_1_2_D02.ja r;c:/DEVELOP/jboss_jetty/jetty/lib/xerces_1_2.jar;c:/DEVELOP/jboss_jetty/jet ty/lib/servlet_2_2.jar;c:/DEVELOP/emacs/site/xslt/xslt.jar;c:/DEVELOP/jde-2. 2.6/java/lib/jde.jar;c:/DEVELOP/jde-2.2.6/java/lib/bsh.jar;c:/DEVELOP/jboss_ jetty/jetty/lib/bsf.jar;c:/DEVELOP/jboss_jetty/jetty/lib/bsfengines.jar;c:/D EVELOP/jboss_jetty/jetty/lib/fesi.jar;c:/DEVELOP/jboss_jetty/jetty/lib/fop_0 _15_0.jar;c:/DEVELOP/jboss_jetty/jetty/lib/sax-bugfix.jar;c:/DEVELOP/jboss_j etty/jetty/lib/stylebook-1.0-b2.jar;c:/DEVELOP/jboss_jetty/jetty/lib/turbine -pool.jar;c:/DEVELOP/jboss_jetty/jetty/lib/w3c.jar;c:/DEVELOP/jboss_jetty/je tty/lib/xml.jar;c:/DEVELOP/jboss_jetty/jetty/lib/xt.jar;c:/DEVELOP/jdk/lib/t ools.jar bsh.Interpreter BeanShell 1.0 beta - by Pat Niemeyer (pa...@pa...) bsh % Here are a few more screens that might be revelant. *Messages* Loading xslt-process... Loading xslt-process...done Fontifying category_select.xml... Fontifying category_select.xml... (regexps......................) Loading xslt-process...done Updating speedbar to: c:/DEVELOP/jboss_jetty/jetty/webapps/knopro5/... Updating speedbar to: c:/DEVELOP/jboss_jetty/jetty/webapps/knopro5/...done Starting the BeanShell. Please wait... (No files need saving) Could not process file, most probably Cocoon1 could not be found! *xslt output* and *xslt messages* are both blank. Here is my classpath (don't laugh at the size, I added everything I could think of to make this work, I was then going to start removing items until things broke :) SET CLASSPATH=.;C:\DEVELOP\jboss_jetty\jetty\lib\cocoon.jar;C:\DEVELOP\jboss_jet ty\jetty\lib\xalan_1_2_D02.jar;C:\DEVELOP\jboss_jetty\jetty\lib\xerces_1_2.j ar;C:\DEVELOP\jboss_jetty\jetty\lib\servlet_2_2.jar;C:\DEVELOP\emacs\site\xs lt\xslt.jar;C:\DEVELOP\jde-2.2.6\java\lib\jde.jar;C:\DEVELOP\jde-2.2.6\java\ lib\bsh.jar;C:\DEVELOP\jboss_jetty\jetty\lib\bsf.jar;C:\DEVELOP\jboss_jetty\ jetty\lib\bsfengines.jar;C:\DEVELOP\jboss_jetty\jetty\lib\fesi.jar;C:\DEVELO P\jboss_jetty\jetty\lib\fop_0_15_0.jar;C:\DEVELOP\jboss_jetty\jetty\lib\sax- bugfix.jar;C:\DEVELOP\jboss_jetty\jetty\lib\stylebook-1.0-b2.jar;C:\DEVELOP\ jboss_jetty\jetty\lib\turbine-pool.jar;C:\DEVELOP\jboss_jetty\jetty\lib\w3c. jar;C:\DEVELOP\jboss_jetty\jetty\lib\xml.jar;C:\DEVELOP\jboss_jetty\jetty\li b\xt.jar;C:\DEVELOP\jdk\lib\tools.jar Thank you for your help and let me know if there is anything else you need....Oh, just a quick reminder on my system. I have JDE up and running (correctly this time), I can process XML files great using Xalan but not Cocoon1 ... Thanks! Jeremy - jc...@bh... --- Work je...@co... --- Home |
From: Ovidiu P. <ov...@xe...> - 2001-05-09 07:02:31
|
It may happen that Cocoon 1.8.2 is again broken with respect to the command line processing. XSLT-process is invoking Cocoon1 through its command line interface, so if this is broken, XSLT-process will also fail. I only tested with a modified version of 1.8 which contains some fixes for the command line interface. I submitted these fixes to the Cocoon developers, and last time I checked they were integrated in 1.8.1. One way you can check to see whether this is the problem is to run in the command line: java org.apache.cocoon.Cocoon -p <your/property/file> file.xml [output-filename] You should get the result of the processing to the standard output, or into the specified output filename, if one is specified. Let me know what's the result. Regards, Ovidiu On Mon, 7 May 2001 17:49:07 -0400, "Jeremy Cowgar" <jc...@bh...> wrote: > Thank you for the reply. I have added a pointer to my cocoon.properties file > (the same one I use during web development) and recieve the same error, > Could not process file, most probably Cocoon1 could not be found! ... > > You asked for the bsh message window, and after looking at it, I am not sure > that it is getting to that point. Here it is: > > * bsh * > cd c:/DEVELOP/jboss_jetty/jetty/webapps/knopro5/ > javaw -classpath > c:/DEVELOP/emacs/site/jde/java/bsh-commands;c:/DEVELOP/emacs/site/jde/java/l > ib/jde.jar;c:/DEVELOP/emacs/site/jde/java/lib/bsh.jar;c:/develop/emacs/site/ > java/xslt.jar;c:/DEVELOP/jboss_jetty/jetty/webapps/knopro5;c:/DEVELOP/jboss_ > jetty/jetty/lib/cocoon.jar;c:/DEVELOP/jboss_jetty/jetty/lib/xalan_1_2_D02.ja > r;c:/DEVELOP/jboss_jetty/jetty/lib/xerces_1_2.jar;c:/DEVELOP/jboss_jetty/jet > ty/lib/servlet_2_2.jar;c:/DEVELOP/emacs/site/xslt/xslt.jar;c:/DEVELOP/jde-2. > 2.6/java/lib/jde.jar;c:/DEVELOP/jde-2.2.6/java/lib/bsh.jar;c:/DEVELOP/jboss_ > jetty/jetty/lib/bsf.jar;c:/DEVELOP/jboss_jetty/jetty/lib/bsfengines.jar;c:/D > EVELOP/jboss_jetty/jetty/lib/fesi.jar;c:/DEVELOP/jboss_jetty/jetty/lib/fop_0 > _15_0.jar;c:/DEVELOP/jboss_jetty/jetty/lib/sax-bugfix.jar;c:/DEVELOP/jboss_j > etty/jetty/lib/stylebook-1.0-b2.jar;c:/DEVELOP/jboss_jetty/jetty/lib/turbine > -pool.jar;c:/DEVELOP/jboss_jetty/jetty/lib/w3c.jar;c:/DEVELOP/jboss_jetty/je > tty/lib/xml.jar;c:/DEVELOP/jboss_jetty/jetty/lib/xt.jar;c:/DEVELOP/jdk/lib/t > ools.jar bsh.Interpreter > > BeanShell 1.0 beta - by Pat Niemeyer (pa...@pa...) > bsh % > > Here are a few more screens that might be revelant. > > *Messages* > Loading xslt-process... > Loading xslt-process...done > Fontifying category_select.xml... > Fontifying category_select.xml... (regexps......................) > Loading xslt-process...done > Updating speedbar to: c:/DEVELOP/jboss_jetty/jetty/webapps/knopro5/... > Updating speedbar to: c:/DEVELOP/jboss_jetty/jetty/webapps/knopro5/...done > Starting the BeanShell. Please wait... > (No files need saving) > Could not process file, most probably Cocoon1 could not be found! > > *xslt output* and *xslt messages* are both blank. > > Here is my classpath (don't laugh at the size, I added everything I could > think of to make this work, I was then going to start removing items until > things broke :) > > SET > CLASSPATH=.;C:\DEVELOP\jboss_jetty\jetty\lib\cocoon.jar;C:\DEVELOP\jboss_jet > ty\jetty\lib\xalan_1_2_D02.jar;C:\DEVELOP\jboss_jetty\jetty\lib\xerces_1_2.j > ar;C:\DEVELOP\jboss_jetty\jetty\lib\servlet_2_2.jar;C:\DEVELOP\emacs\site\xs > lt\xslt.jar;C:\DEVELOP\jde-2.2.6\java\lib\jde.jar;C:\DEVELOP\jde-2.2.6\java\ > lib\bsh.jar;C:\DEVELOP\jboss_jetty\jetty\lib\bsf.jar;C:\DEVELOP\jboss_jetty\ > jetty\lib\bsfengines.jar;C:\DEVELOP\jboss_jetty\jetty\lib\fesi.jar;C:\DEVELO > P\jboss_jetty\jetty\lib\fop_0_15_0.jar;C:\DEVELOP\jboss_jetty\jetty\lib\sax- > bugfix.jar;C:\DEVELOP\jboss_jetty\jetty\lib\stylebook-1.0-b2.jar;C:\DEVELOP\ > jboss_jetty\jetty\lib\turbine-pool.jar;C:\DEVELOP\jboss_jetty\jetty\lib\w3c. > jar;C:\DEVELOP\jboss_jetty\jetty\lib\xml.jar;C:\DEVELOP\jboss_jetty\jetty\li > b\xt.jar;C:\DEVELOP\jdk\lib\tools.jar > > Thank you for your help and let me know if there is anything else you > need....Oh, just a quick reminder on my system. I have JDE up and running > (correctly this time), I can process XML files great using Xalan but not > Cocoon1 ... Thanks! > > Jeremy - jc...@bh... --- Work > je...@co... --- Home > > |
From: Ovidiu P. <ov...@xe...> - 2001-05-07 05:51:18
|
I looked in the documentation and realized I forgot to mention that for Cocoon you also need to specify the properties file. Please run M-x customize-group RET xslt-process RET and setup the Cocoon properties file. If this doesn't work, could you send me the content of the *bsh* buffer? Is there any interesting message related to XSLT-process in the *Messages* buffer? Thanks, Ovidiu On Sat, 05 May 2001 15:28:03 -0400, Jeremy C <je...@co...> wrote: > I'm sorry. I have found the problem, and that was that my JDE looked great, > but the .jar files were not in my class path, as well as xslt.jar was not > in my class path. I added these, and now I can get it to process a XML file > via Xalan but not Cocoon 1.8.2 which is really what I use. It reports: > > Could not process file, most probably Cocoon1 could not be found! > > I double checked to make sure xslt.jar is in my class path. I can set the > processor to be Xalan and all works great, but it will not do some of the > things like SQL that I use in my sites. > > Thanks for all your help, > > Jeremy - je...@co... > > Oh, here's my new class path: > > SET > CLASSPATH=.;C:\DEVELOP\cocoon-1.8.2\bin\cocoon.jar;C:\DEVELOP\cocoon-1.8.2\lib\xalan_1_2_D02.jar; > C:\DEVELOP\cocoon-1.8.2\lib\xerces_1_2.jar;C:\DEVELOP\jboss_jetty\jetty\lib\servlet_2_2.jar;C:\DE > VELOP\emacs\site\xslt\xslt.jar;C:\DEVELOP\jde-2.2.6\java\lib\jde.jar;C:\DEVELOP\jde-2.2.6\java\li > b\bsh.jar;C:\DEVELOP\cocoon-1.8.2\lib\bsf.jar;C:\DEVELOP\cocoon-1.8.2\lib\bsfengines.jar;C:\DEVEL > OP\cocoon-1.8.2\lib\fesi.jar;C:\DEVELOP\cocoon-1.8.2\lib\fop_0_15_0.jar;C:\DEVELOP\cocoon-1.8.2\l > ib\sax-bugfix.jar;C:\DEVELOP\cocoon-1.8.2\lib\stylebook-1.0-b2.jar;C:\DEVELOP\cocoon-1.8.2\lib\tu > rbine-pool.jar;C:\DEVELOP\cocoon-1.8.2\lib\w3c.jar;C:\DEVELOP\cocoon-1.8.2\lib\xml.jar;C:\DEVELOP > \cocoon-1.8.2\lib\xt.jar > > I added everything I could find :-) > > > >Date: Sat, 05 May 2001 13:50:18 -0400 > >To: ov...@xe... > >From: Jeremy C <je...@co...> > >Subject: XSLT for Emacs > > > >I am having a bit of trouble getting this to function properly. > > > >I am running Emacs for Windows, 20.7 ... I have installed PSGML, JDE, and > >elib is installed (No errors on load and JDE works great). What happens is > >I get an error when hitting C-c C-x C-v that reports: Cannot find main > >class, program will exit. > > > >My Class path is: > > > >SET > >CLASSPATH=C:\DEVELOP\cocoon-1.8.2\bin\cocoon.jar;C:\DEVELOP\cocoon-1.8.2\lib\xalan_1_2_D02.jar;C > :\DEVELOP\cocoon-1.8.2\lib\xerces_1_2.jar;C:\DEVELOP\jboss_jetty\jetty\lib\servlet_2_2.jar > > > >Also, I get no syntax highlighting... Anyway, here is the revelant parts > >of my .emacs file as well. > > > >(add-to-list 'load-path (expand-file-name "~/emacs/site/jde/lisp")) > >(add-to-list 'load-path (expand-file-name "~/emacs/site/semantic")) > >(add-to-list 'load-path (expand-file-name "~/emacs/site/elib")) > >(add-to-list 'load-path (expand-file-name "~/emacs/site/eieio")) > >(add-to-list 'load-path (expand-file-name "~/emacs/site/xslt")) > >(add-to-list 'load-path (expand-file-name "~/emacs/site/psgml")) > > > >(autoload 'sgml-mode "psgml" "Major mode to edit SGML files." t) > >(autoload 'xml-mode "psgml" "Major mode to edit XML files." t) > >(autoload 'xslt-process-mode "xslt-process" "Run XSLT processor on buffer" t) > > > >(setq auto-mode-alist > > (append '(("\\.xml$" . xml-mode)) auto-mode-alist)) > > > >(add-hook 'xml-mode-hook 'xslt-process-mode) > > > >(setq defer-loading-jde nil) > >(if defer-loading-jde > > (progn > > (autoload 'jde-mode "jde" "JDE mode." t) > > (setq auto-mode-alist > > (append > > '(("\\.java\\'" . jde-mode)) > > auto-mode-alist))) > > (require 'jde)) > >(defun my-jde-mode-hook () > > (setq c-basic-offset 2)) > > > >(add-hook 'jde-mode-hook 'my-jde-mode-hook) > > > >(custom-set-variables > > '(xslt-process-cocoon1-properties-file > > "c:\\DEVELOP\\cocoon-1.8.2\\conf\\cocoon.properties") > > '(font-lock-support-mode (quote lazy-lock-mode)) > > '(xslt-process-default-processor (quote (Xalan1))) > >(custom-set-faces) > > > >Can you offer any assistance with my difficulties? > > > >Thank you very much, > > > >Jeremy - je...@co... > > > _______________________________________________ > Xslt-process-users mailing list > Xsl...@li... > http://lists.sourceforge.net/lists/listinfo/xslt-process-users > |
From: Jeremy C <je...@co...> - 2001-05-06 17:50:49
|
I'm sorry. I have found the problem, and that was that my JDE looked great, but the .jar files were not in my class path, as well as xslt.jar was not in my class path. I added these, and now I can get it to process a XML file via Xalan but not Cocoon 1.8.2 which is really what I use. It reports: Could not process file, most probably Cocoon1 could not be found! I double checked to make sure xslt.jar is in my class path. I can set the processor to be Xalan and all works great, but it will not do some of the things like SQL that I use in my sites. Thanks for all your help, Jeremy - je...@co... Oh, here's my new class path: SET CLASSPATH=.;C:\DEVELOP\cocoon-1.8.2\bin\cocoon.jar;C:\DEVELOP\cocoon-1.8.2\lib\xalan_1_2_D02.jar;C:\DEVELOP\cocoon-1.8.2\lib\xerces_1_2.jar;C:\DEVELOP\jboss_jetty\jetty\lib\servlet_2_2.jar;C:\DEVELOP\emacs\site\xslt\xslt.jar;C:\DEVELOP\jde-2.2.6\java\lib\jde.jar;C:\DEVELOP\jde-2.2.6\java\lib\bsh.jar;C:\DEVELOP\cocoon-1.8.2\lib\bsf.jar;C:\DEVELOP\cocoon-1.8.2\lib\bsfengines.jar;C:\DEVELOP\cocoon-1.8.2\lib\fesi.jar;C:\DEVELOP\cocoon-1.8.2\lib\fop_0_15_0.jar;C:\DEVELOP\cocoon-1.8.2\lib\sax-bugfix.jar;C:\DEVELOP\cocoon-1.8.2\lib\stylebook-1.0-b2.jar;C:\DEVELOP\cocoon-1.8.2\lib\turbine-pool.jar;C:\DEVELOP\cocoon-1.8.2\lib\w3c.jar;C:\DEVELOP\cocoon-1.8.2\lib\xml.jar;C:\DEVELOP\cocoon-1.8.2\lib\xt.jar I added everything I could find :-) >Date: Sat, 05 May 2001 13:50:18 -0400 >To: ov...@xe... >From: Jeremy C <je...@co...> >Subject: XSLT for Emacs > >I am having a bit of trouble getting this to function properly. > >I am running Emacs for Windows, 20.7 ... I have installed PSGML, JDE, and >elib is installed (No errors on load and JDE works great). What happens is >I get an error when hitting C-c C-x C-v that reports: Cannot find main >class, program will exit. > >My Class path is: > >SET >CLASSPATH=C:\DEVELOP\cocoon-1.8.2\bin\cocoon.jar;C:\DEVELOP\cocoon-1.8.2\lib\xalan_1_2_D02.jar;C:\DEVELOP\cocoon-1.8.2\lib\xerces_1_2.jar;C:\DEVELOP\jboss_jetty\jetty\lib\servlet_2_2.jar > >Also, I get no syntax highlighting... Anyway, here is the revelant parts >of my .emacs file as well. > >(add-to-list 'load-path (expand-file-name "~/emacs/site/jde/lisp")) >(add-to-list 'load-path (expand-file-name "~/emacs/site/semantic")) >(add-to-list 'load-path (expand-file-name "~/emacs/site/elib")) >(add-to-list 'load-path (expand-file-name "~/emacs/site/eieio")) >(add-to-list 'load-path (expand-file-name "~/emacs/site/xslt")) >(add-to-list 'load-path (expand-file-name "~/emacs/site/psgml")) > >(autoload 'sgml-mode "psgml" "Major mode to edit SGML files." t) >(autoload 'xml-mode "psgml" "Major mode to edit XML files." t) >(autoload 'xslt-process-mode "xslt-process" "Run XSLT processor on buffer" t) > >(setq auto-mode-alist > (append '(("\\.xml$" . xml-mode)) auto-mode-alist)) > >(add-hook 'xml-mode-hook 'xslt-process-mode) > >(setq defer-loading-jde nil) >(if defer-loading-jde > (progn > (autoload 'jde-mode "jde" "JDE mode." t) > (setq auto-mode-alist > (append > '(("\\.java\\'" . jde-mode)) > auto-mode-alist))) > (require 'jde)) >(defun my-jde-mode-hook () > (setq c-basic-offset 2)) > >(add-hook 'jde-mode-hook 'my-jde-mode-hook) > >(custom-set-variables > '(xslt-process-cocoon1-properties-file > "c:\\DEVELOP\\cocoon-1.8.2\\conf\\cocoon.properties") > '(font-lock-support-mode (quote lazy-lock-mode)) > '(xslt-process-default-processor (quote (Xalan1))) >(custom-set-faces) > >Can you offer any assistance with my difficulties? > >Thank you very much, > >Jeremy - je...@co... |
From: Jeremy C <je...@co...> - 2001-05-06 17:49:24
|
I am having a bit of trouble getting this to function properly. I am running Emacs for Windows, 20.7 ... I have installed PSGML, JDE, and elib is installed (No errors on load and JDE works great). What happens is I get an error when hitting C-c C-x C-v that reports: Cannot find main class, program will exit. My Class path is: SET CLASSPATH=C:\DEVELOP\cocoon-1.8.2\bin\cocoon.jar;C:\DEVELOP\cocoon-1.8.2\lib\xalan_1_2_D02.jar;C:\DEVELOP\cocoon-1.8.2\lib\xerces_1_2.jar;C:\DEVELOP\jboss_jetty\jetty\lib\servlet_2_2.jar Also, I get no syntax highlighting... Anyway, here is the revelant parts of my .emacs file as well. (add-to-list 'load-path (expand-file-name "~/emacs/site/jde/lisp")) (add-to-list 'load-path (expand-file-name "~/emacs/site/semantic")) (add-to-list 'load-path (expand-file-name "~/emacs/site/elib")) (add-to-list 'load-path (expand-file-name "~/emacs/site/eieio")) (add-to-list 'load-path (expand-file-name "~/emacs/site/xslt")) (add-to-list 'load-path (expand-file-name "~/emacs/site/psgml")) (autoload 'sgml-mode "psgml" "Major mode to edit SGML files." t) (autoload 'xml-mode "psgml" "Major mode to edit XML files." t) (autoload 'xslt-process-mode "xslt-process" "Run XSLT processor on buffer" t) (setq auto-mode-alist (append '(("\\.xml$" . xml-mode)) auto-mode-alist)) (add-hook 'xml-mode-hook 'xslt-process-mode) (setq defer-loading-jde nil) (if defer-loading-jde (progn (autoload 'jde-mode "jde" "JDE mode." t) (setq auto-mode-alist (append '(("\\.java\\'" . jde-mode)) auto-mode-alist))) (require 'jde)) (defun my-jde-mode-hook () (setq c-basic-offset 2)) (add-hook 'jde-mode-hook 'my-jde-mode-hook) (custom-set-variables '(xslt-process-cocoon1-properties-file "c:\\DEVELOP\\cocoon-1.8.2\\conf\\cocoon.properties") '(font-lock-support-mode (quote lazy-lock-mode)) '(xslt-process-default-processor (quote (Xalan1))) (custom-set-faces) Can you offer any assistance with my difficulties? Thank you very much, Jeremy - je...@co... |
From: Ovidiu P. <ov...@xe...> - 2001-05-03 18:18:11
|
Hi, On Thu, 03 May 2001 11:41:00 -0400, Sean OConnor <se...@pe...> wrote: > I realize I am probably missing something obvious, but I am a bit > confused on what is the current version of xslt-process. I see you r > documentation indicate there should be a 2.0 release, but the link to it > seems broken. I tried google, and even the geocities search engine, and > could not find any references to xslt-process-2.0.tar.gz. Am I missing > something obvious? rtfm? > TIA Sorry, it looks like I messed up things last time I've released 1.2.2. Version 1.2.2 is a bug-fix release, but somehow the generated HTML page contained the 2.0 version number, which is currently in development. > ps: the version I have looks promising, I'm still working through some > grokking issues though. Thanks! The new 2.0 release will be a much improved version, containing also an XSLT debugger, currently only for Saxon, but Xalan will come shortly after. There is no release yet, but you can check-out the sources from the CVS repository at SourceForge. I've also setup two mailing lists at SourceForge, so if you're interested in tracking the development of it, you could join them. Regards, Ovidiu |
From: Sean O. <se...@pe...> - 2001-05-03 18:15:10
|
Hello, I realize I am probably missing something obvious, but I am a bit confused on what is the current version of xslt-process. I see you r documentation indicate there should be a 2.0 release, but the link to it seems broken. I tried google, and even the geocities search engine, and could not find any references to xslt-process-2.0.tar.gz. Am I missing something obvious? rtfm? TIA Sean ps: the version I have looks promising, I'm still working through some grokking issues though. -- ------------------------------------ -- Sean O'Connor -- se...@pe... -- http://peoplespace.com ------------------------------------ |
From: Ovidiu P. <ov...@xe...> - 2001-04-10 01:41:00
|
On Mon, 9 Apr 2001 11:19:01 +0200, "Gerrit Niestijl" <g.n...@rr...> wrote: > Thaks for responding. I have been trying again with the new version (1.2.2). > It does not work when I invoke the processor the first time. If I kill the > bsh buffer after the first try, and then try again it works! After that it > stays like that, I have to kill the bsh buffer between every invocation to > make it work. > Maybe it has something to do with the writing of the temporary files, > because xslt-process leaves temporary files around when it failes. Sometimes > these contain the expected output, but other times they do not. I have not > been able to find a pattern in this behavior. Hmm, this is weird, I tried 1.2.2 on a freshly installed GNU Emacs on Win2000, with no special customization besides the one described in the setup for xslt-process. Can you try a similar one at your site, maybe there's something screwed up in the .emacs file. For the next version, 2.0, I am working on a different implementation that uses a standalone program to invoke the XSLT processor, BSH is no longer required. Also the new version is much improved in terms of functionality, and it will contain an XSLT debugger as well. Regards, -- Ovidiu Predescu <ov...@cu...> http://orion.nsr.hp.com/ (inside HP's firewall only) http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff) Did you miss my presentation, "Using Cocoon to build Web sites for wireless devices" at ApacheCon 2001 in Santa Clara, CA? You can still get my presentation on the Web at: http://www.geocities.com/SiliconValley/Monitor/7464/apachecon-2001/ |
From: Gerrit N. <g.n...@rr...> - 2001-04-09 10:29:26
|
Hello Ovidiu, Thaks for responding. I have been trying again with the new version (1.2.2). It does not work when I invoke the processor the first time. If I kill the bsh buffer after the first try, and then try again it works! After that it stays like that, I have to kill the bsh buffer between every invocation to make it work. Maybe it has something to do with the writing of the temporary files, because xslt-process leaves temporary files around when it failes. Sometimes these contain the expected output, but other times they do not. I have not been able to find a pattern in this behavior. Regards, Gerrit Niestijl ----- Original Message ----- From: Ovidiu Predescu <ov...@xe...> To: Gerrit Niestijl <g.n...@rr...> Sent: Saturday, April 07, 2001 6:47 AM Subject: Re: xslt-process > The problem was with the filename, as it started with a drive letter, > and the URL handling code was interpreting that as a URI scheme. I > fixed that and put out a new release. It seems to be working fine for > me, both with XEmacs/Linux and GNU Emacs/Windows 2000. Please let me > know if it works for you. > > Regards, > -- > Ovidiu Predescu <ov...@cu...> > http://orion.nsr.hp.com/ (inside HP's firewall only) > http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff) > > Hope to see you at my presentation, "Using Cocoon to build Web sites > for wireless devices" at ApacheCon 2001 at the Santa Clara Convention > Center, 5001 Great America Parkway, Santa Clara, CA 95054. |
From: Gerrit N. <g.n...@rr...> - 2001-04-09 10:29:20
|
Hello, Since I am using NTemacs for editing XML files which are to be processed by xalan and/or cocoon, I am very interrrested in your xslt-process mode. Unfortunately I can't get it working. I have searched the internet for more information on this but I have not found something yet. I am using ntemacs 20.6 and xslt-process 1.2.1 If I set the processor to Xalan or Saxon the folowing message appears in the xslt-messages buffer: Cannot process: java.net.MalformedURLException: unknown protocol: d (the file is on the d: drive) If I set it to cocoon the emacs message buffer says: Could not process file, most probably Cocoon1 could not be found! and no other messages show up in *xsl-messages* My classpath is OK, I have set it with an environment variable. Do you have any idea what goes wrong? |
From: Ovidiu P. <ov...@xe...> - 2001-04-09 10:28:36
|
Hi Gerrit, On Fri, 6 Apr 2001 11:09:36 +0200, "Gerrit Niestijl" <g.n...@rr...> wrote: > Hello, > > Since I am using NTemacs for editing XML files which are to be processed by > xalan and/or cocoon, I am very interrrested in your xslt-process mode. > Unfortunately I can't get it working. I have searched the internet for more > information on this but I have not found something yet. > > I am using ntemacs 20.6 and xslt-process 1.2.1 > If I set the processor to Xalan or Saxon the folowing message appears in the > xslt-messages buffer: > Cannot process: java.net.MalformedURLException: unknown protocol: d (the > file is on the d: drive) > If I set it to cocoon the emacs message buffer says: > Could not process file, most probably Cocoon1 could not be found! > and no other messages show up in *xsl-messages* > My classpath is OK, I have set it with an environment variable. > > Do you have any idea what goes wrong? The problem was with the filename, as it started with a drive letter, and the URL handling code was interpreting that as a URI scheme. I fixed that and put out a new release. It seems to be working fine for me, both with XEmacs/Linux and GNU Emacs/Windows 2000. Please let me know if it works for you. Regards, -- Ovidiu Predescu <ov...@cu...> http://orion.nsr.hp.com/ (inside HP's firewall only) http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff) Hope to see you at my presentation, "Using Cocoon to build Web sites for wireless devices" at ApacheCon 2001 at the Santa Clara Convention Center, 5001 Great America Parkway, Santa Clara, CA 95054. |