Friday, May 29, 2009

JavaOne sessions

I'm attending JavaOne this year, it starts on Tuesday. These are the sessions i look forward the most to (in no particular order):


Return of the Puzzlers: Schlock and Awe (TS-5186)
Josh Bloch and Neal Gafter present a couple of interresting programming puzzles, will be fun.

Effective Java: Still effective after all these years (TS-5217)
Again, Joshua Bloch. His book "Effective Java" is one of the best programming books i've read.

Java Platform Concurrency Gotchas (TS-4863)
Concurrency is a difficult issue, this session presents issues with code examples.

Ghost in the virtual machine: A reference to references (TS-5245)
Bob is the author of google guice (see below) and from what I've heard, he is also a great speaker.

Defective Java Code: Mistakes that matter (TS-5335)
About bugs in java code, static analysis etc.

Drizzle: A new database for the cloud (TS-5410)
Drizzle is a great project, positive, helpful people.

JDBC? We don't need no stinkin' JDBC: How LinkedIn scaled with memcached, SOA and a bit of SQL. (TS-4696)
Always interesting to hear how big companies handle scalability issues really job related for me.

Introduction to Google Guice: The Java Programming language is fun again (TS-5434)
Google Guice really opened my eyes to what you can do with java, the subject of the talk is so true, it shows what java is capable of and that java can be fun. This is how modern java development should be done.

Sunday, May 10, 2009

Drizzle-JDBC in central maven repository

Now releases of Drizzle-JDBC are in the central maven repository which makes it very easy to use if you are building your projects with maven (or ant + ivy).

Just add the following dependency to your pom.xml:
<dependency>                                                                        
<groupid>org.drizzle.jdbc</groupid>
<artifactid>drizzle-jdbc</artifactid>
<version>0.1</version>
</dependency>

And you are good to go, maven will download the dependencies for you!

Note, drizzle-jdbc uses SLF4J for logging, so if you don't use that you'll need to add a dependency to one of the logging implementations as well:

<dependency>                                                                        
<groupid>org.slf4j</groupid>
<artifactid>slf4j-nop</artifactid>
<version>1.5.6</version>
</dependency>