Skip to main content

Jazoon 2007: Afternoon and evening

Great, I managed to do a java Black Belt attempt on Java 5 and ended up with 0/5 points. I've never even heard of that Scanner class. Think I better get started on that certification (again).

...

Went to a talk by Red Hat's Jan Wildeboer. Virtualization. RH now delivers a full stack with JBoss server and clustering. Most OS'es are built being able to dynamically use CPU and memory (not Windows of course).

Some keywords: VMWare invented x86 virtualization. Hypervisor, ring zero. There were performance issues (20% with heavy io, which is especially overhead intensive). Now there is something called para-virtualization with minimal overhead (1 - 5 %).

Talking about perfomance, live migration, upgrades..

Jboss clustering is still the solution for scaling up memory exploit as the JVM is not dynamically using memory or CPUs.

Virtualization offers us a lot of better perfomance, especially as more CPU's and memory are fitted onto boards.

The talk was a bit out of my league, but it is interesting to hear an alternative to Sun's Solaris/Zones we might consider. The RH guy claims he 's not allowed to present benchmarks, but that RH would win anyway.

...

The other guys went to see the GigaSpaces talk, so I'm tapping in on this one. I'm an old Hibernate user, and I've always wanted to dip into JDO, so that's bout the reason I'm here.

JPox Spatial, some GIS extension on the JDO standard.

Problem is mainly today that there are no tools with a DB back-end that supports GIS stuff. Or they're proprietary, etc.

JDO is a standard. JPOX is Sun's implementation. It also implements JPA.

Talks alot about different libraries from various commercial vendors that are compliant with JDO/Spatial, or the other way around.

The API for JPOX is pretty similar to Hibernate, only slighty worse (save, then get ID).

The spatial api for example gives us a query to ask whether a point is inside a polygon (or does polygons collide, etc).

All in all I think this might be a very exiting for GIS developers. There is an ISO standard on the way for doing these kind of data stores, and having a JDO API on top of these sounds like a good idea.

The speaker is doing some defence of JDO vs Hibernate, JDBC, EJB. Not new to me, I'm no happier with hibernate than I am with JPOX/JDO.

Runs with maven 1. Admittedly lacks the modularity of Spring/Hibernate.

Good idea, implementation sounds slightly immature, quite early into the market. Speaker is quite nervous, but engaged in what he's talking about.

...

Caught a talk on unusual use of Java to get stuff the way you usually would've done it in C. I've never been a C programmer so this talk went pretty much over my head, but it was still somewhat amusing to hear some innovative way of making your own iterators. Neil Gafter was in the seat behind me, and when he laughs it eases my mind thinking this is not stuff I have to do on my own, but can rather wait till it enters Java 7 (closures that is).

...

Now tapping into a talk on Java EE. Figured it was about time I try listening to something I actually know anything about. Leader of the Italian JUG presenting a year of experience with JEE 5. He's also written an Italian book on JEE 5.

The main difference is easier use with POJOs, annotations, injection, etc. Focus here is on EJB 3 and JPA. I've got to post this now but I'll post back on how it went. Probably not too many surprises in store here.
Labels:

Comments

  1. tbeg16/8/07 11:14

    There are quite some open source GIS desktop tools that work with open source Postgresql/Postgis (postgis.refractions.net) spatial DB backend.

    Especially Udig (udig.refractions.net) is worth looking at. Based on eclipse RCP and has an experimental jpox-spatial plugin.

    regards,
    Thomas

    ReplyDelete
  2. Unknown15/12/07 00:35

    Gigaspaces and spatial pojo's are a topic that I am exploring right now. I posted this comment to the geotools mail list Pojo Data Store. The response I got mirrored your impressions. Currently I am looking at using hibernate spatial link and using gigaspaces as a second level cache in front of postgis.

    ReplyDelete
  3. Anonymous13/1/08 16:50

    JPOX is not Sun's implementation. It is an independent project. It implements JCP standards.

    The API for JPOX is pretty similar to Hibernate, only slighty worse (save, then get ID)
    Not sure what you're referring to here. JPOX supports application id (id defined by user, or generated by JPOX at persist) AND datastore id (id generated by JPOX at persist). If the id is selected to be generated in the datastore then you have to store first.

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant...
6 comments
Read more

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...
1 comment
Read more

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org  - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...
Post a Comment
Read more

Git-SVN Mirror without the annoying update-ref

This post is part of  a series on Git and Subversion . To see all the related posts, screencasts and other resources, please  click here .  So no sooner than I had done my git-svn presentation at JavaZone , I got word of a slightly different Git-SVN mirror setup that makes it a bit easier to work with: In short, my old recipe includes an annoying git update-ref step to keep the git-svn remote reference up to date with the central bare git repo. This new recipe avoids this, so we can simply use git svn dcommit   directly. So, longer version, with the details. My original recipe is laid out in five steps: Clone a fresh Git repo from Subversion. This will be our  fetching repo. Set up a  bare repo. Configure pushing from the fetching repo to bare repo In the shoes of a developer, clone the repo Set up an SVN remote in the developer's repo In the new approach, we redefine those last two steps: (See the original post for how to do the fir...
17 comments
Read more

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --...
12 comments
Read more