Hello,
Sorry that the 3 comments below really have nothing to do with JAMES, but here it goes: I don't see why you complain about your free "ZIP" utilities in this forum when java JDK provides a jar utility to manage archives. It's called 'jar' and it's in the bin directory of your java JDK. And yes it's free. And as for custom jar's, why don't you just drop them in the phoenix 'lib' directory? Or better yet, why don't you fix your build.xml to include your JAR's? That's what it's for. Also having spaces in a filename is OS specific and has nothing to do with JAMES. Just put quotes "" around your filenames. -----Original Message----- From: Brian J. Sayatovic [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 13, 2004 10:33 PM To: James Users List Subject: Upgrading James I'm feeling like a n00b to James even though I've been using it for well over a year now. I've been running 2.2.0a for some time now on my Windows XP box. Tonight, I had planned to upgrade to the final 2.2.0 release. My suaul plan of action is to stop the James NT service, rename my F:\Program Files\James folder to F:\Program Files\James.old and then extract the new James. I compare and edit the new wrapper.conf to use my latest JRE. I then add my three custom JARs to the james.sar in the apps folder. Next, I start James, and check the logs. If everything looks ok, I stop James, move over the old repositories, then start it again and check the logs one last time. This, time, though, thinsg went terribly wrong. My Zip program, UltimateZip, seemed to be corrupting james.sar when I added my 3 cusotm JARs to it. Once I got past that, the wrapper.log would contain errors describing as MalformedURLException stemming from "no protocol" when looking for ENTITY declarations located in relative files. I suspected this was from the space in my folder name, so I hacked the registry entry for the service to point to wrapper.exe and wrapper.conf using the 8.3 naming. When this didn't work, I moved my whole James folder to F:\James. That fixed that problem, but then the vanilla config.xml from james.sar led to more errors stemming froma ClassNotFoundException for some file stream store repository class. I've given up for the night. I deleted all my new stuff, renamed my old folder back, unhacked the registry and now my old 2.2.0a version is runnong fine. A few points I'd like to share with people: 1. There is no excuse for a program NOT to work with spaces in paths. Unix supports them. Windows supports them. So should you! 2. A free, decent ZIP utility is hard to come by 3. Adding custom libs/classes to James is a pain in the butt -- is there an easier way??? 4. There needs to be a simpler way to upgrade James in place, or at least an automated tool to help do all of the above. Or, at least, how about a Wiki page on this subject? Anyone have some advice before I start again tomorrow? Regards, Brian. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
