As many of you surely do not know, all Macintosh computers that are not running OS X are only JDK 1.1.8 compatible, plus they have Swing support. This means that a lot of the good stuff, like the Collections interfaces, must be imported manually. While this is irritating sometimes, it has become a show-stopper when used with JRun. I wrote a very simple servlet that was completely JDK 1.1 compatible, and it tested out beautifully with TomCat (an excellent program, just like Apache). Tomcat was easily able to find the imported Collections package (com.sun.java.util.collections.*) However, when I shifted over to JRun (the actual web server's Servlet Runner), all sorts of problems appeared. First of all, when my servlet was in the correct directory structure for its package, JRun could not find it, even though the (sparse) documentation stated clearly that all packages must be in their respective directory structure inside the servlets folder. So, after some struggling, I ripped out all the packaging and dropped it all in the top level directory. Now, it can easily find my servlet, but it cannot find the Collections package. Since I only have the .class files for Collections, I don't have the option to de-package them, nor would I want to, since that might violate the distribution requirements by Sun. Whew...long rant. Has anyone else ever dealt with this stuff and/or have links to good documentation on dealing with JRun 2.3 The company that makes it (www.livesoftware.com) apparently got bought out some time in the past and the new company seems to only want to support version 3.0 (which is not for Macintosh). Also, can anyone please give me 1 good reason to develop on a Mac, especially in Java? Here at the University of Iowa, everyone seems to use them, but I have never had more trouble. They are always at least 2 steps behind UNIX & Windows.