The Eclipse WTP tools seem to have problems when the JDK in use changes.  There does not appear to be any UI feature that allows a user to tell the WTP server which JDK to use, causing it to fail to start with various error messages.  Thankful to this blog post, I have found a fix that has reliably worked.  I keep referring to the page, so thought I'd regurgitate it here...

Solution : delete the [WORKSPACE_NAME]\.metadata\.plugins\org.eclipse.debug.core\.launches\[WTP_SERVER_NAME].launch file

Social Bookmarks :                                              

  Export this post to PDF document

Add a comment

Posted by Wyatt on February 18, 2012 12:26:17 PM EST #

I'm excited about HTML 5 and the rich user experiences it can offer, but with so many people using old web-browsers much of the capability cannot be used (reliably).  If you're still using an older web-browser, please consider upgrading today.  You would be helping to make the world a better place...

• Firefox - My everyday browser.
• Chrome - Growing on me, but I still don't trust Google.
• Opera - Always a strong contender.
• Internet Explorer - We all know IE, but Microsoft is definitely catching up.
• Safari - If you're using a Mac it's definitely a viable option.  On a PC it works, but Chrome is better WebKit experience.

Social Bookmarks :                                              

  Export this post to PDF document

Add a comment

Posted by Wyatt on December 9, 2011 1:48:00 PM EST #

On November 16^th, Congress holds hearings on the first American Internet censorship system. This bill can pass. If it does, the Internet and free speech will never be the same.

Join us to stop this bill.

http://www.mozilla.org/sopa/

https://wfc2.wiredforchange.com/o/9042/p/dia/action/public/?action_KEY=8173

Social Bookmarks :                                              

  Export this post to PDF document

Add a comment

Posted by Wyatt on November 16, 2011 12:05:00 PM EST #

One common task when setting up a new HTTP server is to configure iptables to allow traffic to your HTTP server. The commands below will allow traffic on ports 80 and 443. You may need to adjust the 5 and 6 values to your environment - these are appropriate for a clean CentOS 6.0 installation.

sudo iptables -L -v
sudo iptables -I INPUT 5 -p tcp --dport 80 -j ACCEPT
sudo iptables -I INPUT 6 -p tcp --dport 443 -j ACCEPT
sudo /sbin/service iptables save
sudo iptables -L -v

Social Bookmarks :                                              

  Export this post to PDF document

Add a comment

Posted by Wyatt on November 12, 2011 11:04:24 PM EST #