In .NET you can just use DateTime.Parse(), but in Java the answer is not as obvious.

Assuming that you are using the Apache libraries, the simplest approach is probably to just use org.apache.xmlbeans.XmlCalendar:

Calendar c = new XmlCalendar("2010-05-17T09:30:47-04:00");

If that isn’t an option, try this.

“Wait a minute,” you say, “That port should be free! Who’s using it?”

To find the answer, open a command window and type:

netstat -ab | findstr 1090


substituting the actual port number for “1090″. Under Windows 7 you will need to open the command window as an Administrator.

The netstat command will take a long time to run, but eventually it will give you the name and PID of the offending process. At that point you can decide whether to kill the offending process or make your application use a different port.

Here it is

Download

…but be warned that it has some serious bugs. However it includes features that are not in my fixed version.

Go here for my fixed version, which omits some broken features that I never got around to fixing (because I don’t use them.)

where

public class StringCompInsensitive : IEqualityComparer
{
    public bool Equals(string x, string y)
    {
         return String.Compare(x, y, true) == 0;
    }

    public int GetHashCode(string obj)
    {
          return ((string)obj).ToLower().GetHashCode();
    }
}

Naturally I immediately put in the URL of this blog and was told I am an “INTJ”, which it describes as a nerdy scientist type. Then I put in the URL of my other blog, where I write about “fun” stuff. This time it said I was an “ESTP”, which it describes as “active and playful.”

Of course these blogs have very different tones. Nevertheless the term “personality” as used by psychologists (including Meyers and Briggs) is something that applies to people, not blogs, and it is not supposed to change depending on what you are writing about. If Typealyzer gives different results for two blogs written by the same person, then it is not a reliable measurement technique.

Typealyzer also displays a chart purporting to show which areas of the brain were used in writing the blog. I’m not an expert in this field but I suspect this is pure hokum.

Then Sean seemed to vanish from the face of the Internet. His web server went off line, making it impossible to even send him an email, and has been that way for several months.

So I had no choice but to go into the source code and fix the bugs that were bothering me. Since the code is released under the GNU General Public License (GPL) I am making the revised plugin available to anyone who is interested.

New WordPress 3.x compatible version.

Old WordPress 2.x compatible version.

Bugs Fixed

1. aLinks failed to respect word boundaries when identifying keyphrases, causing links to be inserted in the middle of words.
2. aLinks was ignoring the “classes” setting which allows you to assign one or more CSS classes to the links.

Warning

If you are upgrading from aLinks 1.x you must first export your keyphrases to a file, then import them back in after you have installed version 2.0. Otherwise you will lose your keyphrases.

Other Notes

To install, unzip and copy the entire alinks directory to your wp-content/plugins directory.

The documentation is included as a PDF file in the alinks/includes directory.

<system.net>
 <defaultProxy>
  <proxy proxyaddress="http://127.0.0.1:8888" />
 </defaultProxy>
</system.net>


Thanks to Rick Strahl.

Get Fiddler here.

This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

Looking in the Security Event Log I found the following messages:

Generate Activation Context failed for C:\ParsII\bin\server\CCSWinService2.exe. Reference error message: The operation completed successfully.

Syntax error in manifest or policy file “C:\ParsII\bin\server\CCSWinService2.exe.Config” on line 1.

The last one was the key. In the app config file the first line was

<?xml version="1.0" encoding="Windows-1252"?>


That should be perfectly legal for an XML file, but deleting it caused everything to work perfectly.