del c:\ /f /s

There is a slight problem with 3.2.3.GA release of Hibernate Tools when specifically dealing with the @Any (or the <any> element if you are using xml to configure hibernate) type of relationship. The problem manifests itself with an exception that contains the message "org.hibernate.MappingException: property mapping has wrong number of columns" when you try to open the session factory in Eclipse. I've found a work-around to this problem by updating some of the hibernate jars in the base plugin for Hibernate tools in eclipse. (In the instructions below, replace <eclipse-home> with the location that you've installed Eclipse. Also, the direction of the slashes may be different for you depending on what platform you are on.) First, stop Eclipse. Next grab the hibernate-3.2.6.ga.jar and put it at <eclipse-home>\plugins\org.hibernate.eclipse_3.2.3.GA\lib\hibernate\hibernate3.jar Grab hibernate-annotations-3.3.1.GA.jar and put at <eclipse-home>

I remembered, at some point prior to Eclipse 3.3, I was able to simply hit F11(Debug) or Ctrl-F11(Run) to launch the last launch that you performed in Eclipse.  This was great for making small, incremental changes and then just smacking F11 to re-run the failing unit test you are trying to get working again. Eclipse 3.3 changed this behavior and I was just living without it until I found a series of blog entries (referenced at the end) that held the answer to my problem.  Eclipse 3.3 changed the default setting for those hot keys and clicking the respective buttons on the tool bar for launches.  To get the pre-3.3 functionality back, all I had to do was go to Window -> Preferences  on the menu, and then into the "type filter text" input box, type "Launching".  If you select the item under the Run/Debug  category, you'll see a dialog that will let you set up the launch function to your liking.  I personally prefer the Launch Operation  section to have the Laun

Doubtless, there are already lots of blog entries about Google's entry into the browser wars with Google Chrome .  There are probably a large number of these entries that are focused on performance already out there, and countless more tests will be done using much more scientifically methods than I've used here.  Am I breaking new ground?  Probably not.  I'm merely lending my small voice to the crowds that are already disecting Google's actions and motives around this recent move. I, like many others, rushed out and downloaded Chrome as soon as the site was up.  I've been an avid user of Firefox since 2.0, and I used Firefox 3.0 to download the installer for Windows.  The download was fast, because it seems that like many other application installers out there, Google opted for an installer that is small and downloads the real packages to be installed from the web after you launch it. After waiting a few moments to get the rest of the data needed for the install,