Skip to main content

Jazoon 2007: Some more notes on last day

I'm just back from some dubbin' in Publin, I mean pubbin' in Dublin, so little time to write a full post. However, I did find the notes I lost from day 4 in Jazoon:


Last Day. Neil Gafter on closures.

First talk OSGi from Ergon Informatik.

The speaker is really happy with OSGi. It's great, it works really well, etc. Running osgi demo.

Bundles/plugins managed in a phone on a console app called J9 Console.

Goes on to talk about RCP. eSWT for embedded. Subset for SWT. Can run without RCP/osgi context if you don't need them.

JFace, gui toolkit. eJFace for embedded.

eWorkbench lets you bundle simul apps running. eUpdate is the update mechanism that is in eclipse. Pretty cool, the whole update manager is run on an embedded device.

Services can be shared between apps in the same VM.

Issues they have encountered in eRCP. Useful list.

Use JFace fonts and typesets to avoid memory leaks.

Some negative experiences.. Complex bundle dependencies. The services have states to manage, and this can be tricky to learn. Plus all the usual embedded ui issues.


Web 3.0/semantic web Q&A session with Henry Story following the previous session that we unfortunately did not attend.. Very interesting.


Java and SecondLife.

Seems like SL has potential in using resources as in uri resources...

Abit about the SL script language. The scripts are only evalutated when in the SL engine, client side.

Scripts can also call http requests that the SL server will shoot off to external servers. 1 KB limit on the response. An example is a SL phone booth that shoots off SMS requests to external servers.

The 1KB limit can be workaround by having the SL object being able to respond with packets. Note that client code cannot be changed once deployed many places.

Communication is used between the client and an external server but needs to be done through a remote channel. The external server then XML-RCPs to the external server.

The java library (a port of the C# library) for utilizing SL clients is somewhat dead, appearantly. But offers good control.


Sort of split in half when it comes to deciding on the next talk. It's either a very interesting presentation on Jackrabbit or a talk from Netcetera on the complexity of software.

After talking with David about Jackrabbit for a little while I decided to jump in on the talk bout Build-up of artificial complexity. A talk straight to my heart.

Code grows ugly. We all know the problem, so what is the solution? Discipline and modularity are old solutions. Reduce number of (external) components is another one. I like addressing every req with an external component. His advice is be sceptical and choose the frameworks/components you *like*.

People don't like being constrained away from their personal favourite tech stacks. Limitation is dangerous, so don't restrain too much.

Will read more of this stuff. Read Greene's essay, but can't find the article on the net. Will just have to wait for the slides to come online (nudge nudge, Jazoon).

Popular posts from this blog

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do:

# install vcsh & myrepos via apt/brew/etc
vcsh clone mr
mr update

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

    -> ~/.atom/*

    -> ~/.mrconfig
    -> ~/.config/mr/*

    -> ~/.tmuxinator/*

    -> ~/.vimrc
    -> ~/.vim/*

    -> ~/bin/*

    -> ~/.gitconfig

    -> ~/.tmux.conf    

    -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

I discovere…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s

You'll get this .git/config:

[svn-remote "svn"]
        url =
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):

(Compared to regular remote branches, they look very odd because there is no remote name i…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…