Good stuff! It included JDBC drivers for most popular DB and faster UI.
Personal edition is free! 🙂
Recently, I need to write a small Java program to get / put files from a WebDAV server. The most well-known Java library to serve this purpose is Apache Slide which is now under version 2.1 since 2004. Since WebDAV is totally not a new thing, so I thought Slide should be pretty stable and reliable in this case. I planned to spend one day to program the sample, but the result is so disappointing… I can’t even do what I want.
I found a serious bug in version 2.1, it cannot list all child elements in a folder. Primarily, I thought it’s my programming problem. But eventually, its command line program doesn’t work too. I queried Apache Bugzillia, someone already mentioned it just few days after 2.1 released in Dec 2004. But so far it’s still open. 😦 I feel very shocked. This issue has been lasted for 2 years and seems they don’t have any plan for 2.2 beta or 2.1 bug fixed version.
Hopefully, my project allows me to have an alternative of network drive connectivity using SAMBA. I remember my old day, I’ve thought to use Slide in my client’s content management project. I wonder how can I make sure it’s reliable for content management API as well. But anyway, I guess Slide is too old now as
a content management framework. You can find many other new alternatives actually.
Please let me know if any other WebDAV library in Java.
Sometimes freedom is not necessarily good. I’m not a man of decision-making. It would waste my a lot of time when too many dishes in the menu or too many opinions in my mind. And it’s the same in development world. In Java world, the problem is more serious. Honestly I still can’t figure, which is the best framework with less overhead in performance. Before I can sort this out, which web service I should use becomes another issue. Seems I can never start to write a line of code.
Should I use iBatis or Hibernate? XFire or AXIS? Perl, PHP or Ruby? Debian, Fedora, Ubuntu or Suse? Make the wrong decision, and you can waste a ton of time, as we found out on a recent project when we wasted a week try to make AXIS2 work for a web service project, only to find out that XFire was the right choice.
Microsoft offers the certainty of no choices. Choice isn’t always good, and the open source community sometimes offers far too many ways to skin the same cat, choices that are born more out of pride, ego or stubbornness than a genuine need for two different paths. I won’t point fingers, everyone knows examples.
We spend a lot of time complaining about all the evil ways Microsoft uses to foist themselves on the world. By doing this, we automatically remove any blame that we ourselves may bear for their successes and our failures. The reality is that there are good, practical reasons that drive people into the arms of the Redmond tool set, and we need to accept that as a fact and learn from it, rather than shake our fists and curse the darkness. For we have met the enemy, and it is us, not Microsoft, at least not all the time…
It’s quite hateful that Eclipse always generates hidden files .project and .classpath in project folder. Sometimes you’re not awared if something goes wrong in these files.
After upgrading your Eclipse and if you found the following compile error, I’d suggest you to check .classpath in your project folder.
The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object. Fix the build path then try building this project
Most likely you would see a line like this.
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/ org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/j2re1.4.2_03"/>
The stupid Eclipse appended this for no reason. Just simply remove it to make it work again. 😉