• Solution to Deployment issue using Netbeans 6.5.1 and Tomcat 6.0.22 on OX 10.5.7

    Somehow I always find myself in the middle of a very strange computer problem. This particular issue is a result of my wanting to learn to write JSP applications using Netbeans 6.5.1 with Tomcat 6.0.20. I don’t have time to do a full writeup, so here’s a nutshell version of the problem and my solution:

    Problem

    When I tried to use the Deploy option to push my Netbeans project to my Tomcat webapps folder, the deployment would fail. I could manually copy the .war file into my Tomcat webapps folder and everything would work fine. But, I thought, “Why should I have to do this if Netbeans is supposed to do it for me?”

    Solution

    Since I’m running OS X 10.5.7, I opened the Netbeans configuration file at

    /Applications/NetBeans/NetBeans6.5.1.app/
    Contents/Resources/NetBeans/etc/Netbeans.conf

    and added the following to the netbeans_default_options line:

    -J-Djava.io.tmpdir=/tmp

    Note: This must be added within the double quotes. Also, I didn’t distrub anything that was on the line already but merely added that tidbit of code.

    Explaination

    I found this piece of advice buried deep in a forum. Apparently, Netbeans puts the deployed files into a temporary folder before deploying them. The temporary folder it tries to use on OS X isn’t accessible (a permissions problem I guess). Adding that snippet of code tells Netbeans to use the OS X default temporary folder tmp for its intermediate work.

    Enjoy!

  • Hello, I’m Drungol and I’m Addicted to WoW

    Yes, I’m addicted to World of Warcraft.

    Mountain Dew Game Fuel Alliance Banner

  • What to do if Cygwin Does Not Work Properly in Vista

    So, I tried to install Cygwin on my Windows Vista Business machine today.  The install, via the setup.exe that downloads what you want to install, launched and completed as it always had in WIndows XP. I was pleasantly surprised considering how Vista has refused to install things normally before. Just when I was about to be happy, I clicked on the Cygwin Bash Shell shortcut, the prompt came up, but no commands worked.  Not ls, not dir, not anything! I let out my usual sigh of annoyance and cursed Vista (for the millonth time).

    I then proceeded to Google to find a solution.  Nothing. The forum posts pleading for help were responded to with the usual worthless suggestions (such as “Don’t use Vista“) and RTFM talk. I don’t really want to use Vista, but it has been forced upon me and I have little recourse but to use it.  Anyway, after trying a few things that didn’t work, I finally figured out what to do: Set your system path environment to the Cygwin bin directory and everything works fine!

    To do that, all you gotta do is follow these simple steps:

    1. Install Cygwin normally with the setup.exe program, selecting what you want to install.  For the purposes of this walkthrough, I’m going to assume you installed Cygwin in the default C:\cygwin location.
    2. Click on the Start Menu (or Windows Orb, for those of you Vista fanboys).
    3. Right Click on Computer, and choose Properties.
    4. Click Advanced system settings in the left-hand context sidebar (and accept the UAC prompt to go proceed as an Administrator).
    5. Click the Advanced tab
    6. Click the Environmental Variables button at the bottom of the dialog.
    7. In the Environment Variables list box, find the variable Path and double click on it
    8. In the resulting Variable Value box, move your cursor to the end of the line of paths already there and add ;C:\cygwin\bin Do not forget the semicolon before the path!

    That’s it! Remember, if you installed Cygwin somewhere other that C:\Cygwin, you’ll have to change your path to be different from my example. I’m hoping that if you did a non-standard install that you can figure out how to adjust the path!  I hope this helps somebody!

  • Using MS Server 2003 Admin Tools with Vista

    Today I tried running the Windows Server 2003 Admin tools with Vista Business and was a little surprised when I got the error message:

    MMC could not create the snap-in.

    I guess the only reason I was shocked was that I got no errors whatsoever. The install went just fine. Normally, when you attempt to install an older Microsoft tool that isn’t compatible, Vista will freak out and let you proceed no further.

    After a some Googling (and several leads that did not work), I found a fix on the Microsoft Knowledge Base: http://support.microsoft.com/kb/930056

    The fix was actually quite easy: Finding the fix was another story!

  • To WP or Not to WP…

    So, I have installed WordPress 2.7 on my long-forgotten TravisSmith.us domain. I have been considering migrating JerryTravis.com to WordPress, so for now, this is a testbed to see if I really like the platform enough to do so.

Categories

Archives

Scroll to Top