«
»

First Impressions on Spring Source Tool Suite


Last night I run the Spring IDE for Java. Apart from the fact that Eclipse in my laptops is slow due to low memory, the Spring IDE seems to be heavier than Eclipse. I am used to work with python and Eclipse using pydev, and start-up times are poor, but Spring seems even worse, so like 10 minutes waiting for things to load, etc…

The welcome page looks great, with information from Spring web site, feeds, and download center with cool software like SVN repository, sync of development task with MS Outlook, Trac integration, Grails, Groove, etc… When trying to install those applications got an error, so man, bad luck to me.

Then created a Java project Buscaplus and tested BerkeleyDB. The experience of IDE is pretty nice, getting nice suggestions with the autocomplete.

I still can’t seem to work out the Subversion repository from Google code, will try this weekend. the default repository is CVS, and since the easy-to-install functionality did not work, will have to go the long way.

I run tests for BerkeleyDB and I was not impressed by performance. Aprt from this, Oracle has changed the implementation for Java from the original from Berkeley, so you only have BTREEs, can’t create tables without environments, etc… This was a total blowout, I can’t use it for OctopusDbm, I prefer an original implementation of BerkeleyDB and Tokyo instead of a Java flavour. As part of this, Java implementation does not physically writes data in the xxxx.db file you determine, but creates partitions of about 10MB each. I don’t like this, prefer the original way. If I choose to have a file 500MB with a cache of 128MB then the software should do what I need. So a C++ will have to be worked out for OctopusDbm.

Going back to Spring, I missed an integrated application server coming with the install of the suite. I thought that would come with the installation, so will have to install tmServer based on Tomcat someway.

As a conclusion, Spring IDE is ok, but had problems with me. Many things are integrated like Aspect projects and Spring views and perpectives are cool, but gee, some things did not work and I don’t like that.

[Update Feb 22]

I installed again Spring and everything went perfect. For some reason first install had problems with Equinox. I now see installed the dmServer (Development) and tcServer (Tomcat) as well as the download center works ok.

Post to Twitter Tweet This Post Post to Plurk Plurk This Post Post to Digg Digg This Post Post to Ping.fm Ping This Post

,

This entry was posted on Friday, February 19th, 2010, 12:12 pm and is filed under Technology. You can follow any responses to this entry through RSS 2.0. You can leave a response, or trackback from your own site.

  • John,

    I did not test or run Java API with C modules yet. I guess the advantage would be for OctopusDbm faster in the stored procedures based on code, which is something nice to think about. Will give it a run whenever have some time.

    Have you used this Java API? Have any performance numbers?

    Thanks for commenting
  • Sounds like you're using Berkeley DB JE (Java Edition). You can still use Berkeley DB's original Java API if you want, which does all the things you describe are missing.
blog comments powered by Disqus