From: Mark C. <co...@ma...> - 2008-12-13 17:02:25
|
I followed the instructions here (I'm using eXist 1.2.4 (8072) running on the included Jetty webserver and downloaded saxon 9.1.0.3j & jakarta regexp 1.5 - both latest versions): http://atomic.exist-db.org/HowTo/XSLT2/ I saw that it mentioned that the Cocoon steps were optional, so I didnt follow any of those steps. However, then I got some error message related to the regular expression library (RESyntaxException), and so I added the appropriate regexp jar to the endorsed folder but that didnt solve the problem. Searching this mailing list, I found a couple of other people had the same problem. They were told to also make the Cocoon changes. So, I did that and then got an error message saying that PrefixResolver could not be found. Seems that this class is in the xalan-2.7.1.jar file (which the "howto" says to delete). So I put that jar file back in the endorsed folder, and now everything works fine. May I suggest the following changes to the HowTo?: 1. Don't mark the Cocoon changes as optional (In the default case, cocoon changes are no optional. Maybe there are other situations where it is optional, but maybe this could be worded differently). 2. Don't say to delete the xalan jar file 3. Change the "saxon xslt processor" section of cocoon.xconf so that the transformer-factory value is "net.sf.saxon.TransformerFactoryImpl" instead of "com.icl.saxon.TransformerFactoryImpl". I know the HowTo tells you to be careful about this, but why not make it the default anyway? Hope this helps someone. -- View this message in context: http://www.nabble.com/Upgrading-eXist-for-XSLT-2.0-%28Saxon%29-tp20992180p20992180.html Sent from the exist-open mailing list archive at Nabble.com. |
From: Mark C. <co...@ma...> - 2008-12-14 08:30:02
|
Ok, you can ignore the bit about not deleting the xalan jar. That can indeed be deleted. This was yet another example of Vista's UAC working against me. Despite being careful (though maybe not careful enough) to run my text editor in Administrator mode when editing the config files, it seems that one of my changes slipped through to the VirtualStore and, therefore, did not manifest in the next database startup. In other words cocoon was still configured to use xalan. Are there any long terms plans for how to deal with UAC? Its cost me many hours over the last couple of months. Also, in my opinion, it makes sense to separate config and data from program code anyway. How exactly to do that, is another question. Mark Carter wrote: > > I followed the instructions here (I'm using eXist 1.2.4 (8072) running on > the included Jetty webserver and downloaded saxon 9.1.0.3j & jakarta > regexp 1.5 - both latest versions): > > http://atomic.exist-db.org/HowTo/XSLT2/ > > I saw that it mentioned that the Cocoon steps were optional, so I didnt > follow any of those steps. > > However, then I got some error message related to the regular expression > library (RESyntaxException), and so I added the appropriate regexp jar to > the endorsed folder but that didnt solve the problem. > > Searching this mailing list, I found a couple of other people had the same > problem. They were told to also make the Cocoon changes. So, I did that > and then got an error message saying that PrefixResolver could not be > found. > > Seems that this class is in the xalan-2.7.1.jar file (which the "howto" > says to delete). > > So I put that jar file back in the endorsed folder, and now everything > works fine. > > May I suggest the following changes to the HowTo?: > > 1. Don't mark the Cocoon changes as optional (In the default case, cocoon > changes are no optional. Maybe there are other situations where it is > optional, but maybe this could be worded differently). > 2. Don't say to delete the xalan jar file > 3. Change the "saxon xslt processor" section of cocoon.xconf so that the > transformer-factory value is "net.sf.saxon.TransformerFactoryImpl" instead > of "com.icl.saxon.TransformerFactoryImpl". I know the HowTo tells you to > be careful about this, but why not make it the default anyway? > > Hope this helps someone. > -- View this message in context: http://www.nabble.com/Upgrading-eXist-for-XSLT-2.0-%28Saxon%29-tp20992180p20998252.html Sent from the exist-open mailing list archive at Nabble.com. |
From: Andrew W. <and...@gm...> - 2008-12-14 09:35:19
|
> Are there any long terms plans for how to deal with UAC? Its cost me many > hours over the last couple of months. Don't you just do everything in your "users" area? -- Andrew Welch http://andrewjwelch.com Kernow: http://kernowforsaxon.sf.net/ |
From: Wolfgang <wol...@ex...> - 2008-12-14 17:18:51
|
> Are there any long terms plans for how to deal with UAC? For the next release, the installer should ask for the location of the data dir, which should default to the User area if you are on Vista. On Unix-based systems, most people (including myself) seem to prefer that the data dir remains within EXIST_HOME. However, I'm not sure how your issues with eXist's or Cocoon's configuration could be solved. Moving the entire webapp/ directory outside of EXIST_HOME would make it even more difficult for new users to understand eXist's setup. eXist also needs conf.xml at startup to find its data directory. How are other Java-based distribution addressing those issues on Vista? Wolfgang |
From: Mark C. <co...@ma...> - 2008-12-15 14:38:33
|
Wolfgang Meier-2 wrote: > > How are other Java-based distribution addressing those issues on Vista? > I don't know of any standard approach and I don't really have exposure to enough java-based distributions to take an educated guess. However, since now the program files, data and config are all outside of user folders, it makes sense to keep it that way otherwise don't you open eXist up to whole new batch of potential bugs/features? How about recommending (during Vista installations) to use EXIST_HOME outside of the Program Files folder? Does that solve the problem? -- View this message in context: http://www.nabble.com/Upgrading-eXist-for-XSLT-2.0-%28Saxon%29-tp20992180p21014911.html Sent from the exist-open mailing list archive at Nabble.com. |
From: Mark C. <co...@ma...> - 2008-12-17 10:44:40
|
Another option is to use the "Application Data" folder in the "All Users" user folder: c:\Users\All Users\Application Data\eXist This uses a shortcut and so actually resolves to: c:\ProgramData\eXist Maybe that's a bit neater (more standard) than using something like "c:\eXist". -- View this message in context: http://www.nabble.com/Upgrading-eXist-for-XSLT-2.0-%28Saxon%29-tp20992180p21050829.html Sent from the exist-open mailing list archive at Nabble.com. |