Stephen & Victor, At 02:54 PM 12/9/2002, you wrote:
Traditionally, Mac OS (up until Mac OS X) has been able to handle 31 characters. I believe this began in 1984 with the original Macintosh. This is why it truncates to 31 characters. I don't recall why it's 31, but I'm guessing that it has more to do with "32" than 31 (perhaps it has something to do with the ":" which was used as the "folder" delimiter much like "\" on Windows & "/" under Unix--e.g., "Macintosh HD:java:fop-0.20.4:lib:avalon-framework-cvs-20020315.jar").Clay Leeds wrote:> The files were ZIP'd, and when they were unZIP'd using Stuffit Expander, > the avalon JAR file's long filename was changed from: > > avalon-framework-cvs-20020315.jar > > to: > > avalon-framework-cvs-20020315.j > > Adding "ar" at the end of that filename, resolved the problem, and I am > able to run FOP on my Mac. Unfortunately, it took a few days to > figure out > this problem. First, thanks for the input. I'll be glad to update the FAQ, but I am a little confused about what to put into it. The file name was truncated after 31 characters, which is too odd of a number to seem to have been done on purpose by StuffIt. What caused the filename truncation? Without understanding that, I am not sure how to help.
Stephen Bannasch wrote:
MacOSX Note: Don't use Stuffit to expand the archive. Use the following shell command instead:
tar -xzf <source>.tar.gz
gunzip should work for a zip file also (I think).
This is fine, but I think it would be better to state something like:
MacOSX Note: Use the following shell command to extract FOP under Mac OS X:
tar -xzf <source>.tar.gz
If you use Stuffit to expand the archive, the following filename:
fop-0.20.4\lib\avalon-framework-cvs-20020315.jar
may be truncated to 31 characters
fop-0.20.4\lib\avalon-framework-cvs-20020315.j
causing an exception:
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/avalon/framework/logger/Logger
at org.apache.fop.apps.Fop.main(Unknown Source)
Simply rename the file as follows and all should be fine:
fop-0.20.4\lib\avalon-framework-cvs-20020315.jar
As for adding this info to the FAQ, I thought it might be useful to include some information about this since it's not easy to find. It would've saved me some time if it were in the FOP FAQ. Believe it or not, it wasn't easy to find on Apple's site. I found it in an obscure link (I don't recall the page with the link):> Java Home. Many Java applications require the identification of a "Java > Home" directory during installation. The equivalent on Mac OS X should > always be /Library/Java/Home. This is actually a symbolic link to the > current installed J2SE version, and allows access to the bin subdirectory > where command line tools such as java, javac, etc. exist as expected. The I am not a Mac guy, so please excuse my ignorance. Is this something that Mac people should already know? In other words, I wonder whether it is even appropriate to address this in FOP doc as it is primarily a sysadmin issue, or at least a Mac or Java issue. Also, what if /Library/Java/Home points to a 1.1 or 1.2 java runtime? If we tell the user to use that, then FOP doesn't work. Again, I am not sure what to recommend here.
http://developer.apple.com/qa/qa2001/qa1170.html
BTW, although I haven't really done much with the Java end of things on my Mac, I considered myself something of an advanced Mac user. To be more clear, I never really ran JAVA applets outside of web pages. Now I'm developing with XSL-FO, and since I can FOP it on my Mac, I thought it'd be nice to start playing with it. Unfortunately, I had problems, and when I searched far and wide for help, and did not find "the answer" anywhere.
Clear as mud!? :-)
- Clay Leeds
- Web Developer
- [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
