Home on Adam Warski: programming articles & videos

You can look at dependency injection as a fancy name for passing parameters to a function (or constructor arguments to a constructor).

Previous versions of Veripacks focused on defining what classes are visible outside of a package hierarchy (exporting).

I recently took over the maintenance of xsbt-proguard-plugin from siasia.

Veripacks 0.1 allowed to specify which classes should be exported from a package hierarchy, by using a simple @Export annotation, and later verify that the specification is met.

How often do you see code like this, especially when using dependency injection, single-responsibility principle, and other “good practices”?

As Scala 2.10 was released some time ago, it is high time to update the projects using 2.

Using some free time during my Christmas & New Year break, I worked on a new project, which implements some of the ideas from my earlier blog “Let’s turn packages into a module system”.

Using some time during the weekend, I decided to finally explore one the new features in the coming Scala 2.

MongoDB is a really great “NoSQL” database, with a very wide range of applications.

Thanks to Sonatype OSS repositories, ElasticMQ version 0.6.1 is now synced to central.

Many projects are divided into modules/subprojects using the build system (Maven, Gradle, SBT …); and writing modular code is generally a Good Thing.

Summer is definitely over, so it’s about time to release a new version of ElasticMQ (0.

In one of the projects that we are currently working on we have a fairly typical setup with one server (Apache with mod_rewrite) proxying traffic to backend servers.

Scala blends functional and object-oriented programming in many nice ways.

It’s good to do something different once in a while.

Konrad recently shared on our company’s technical room an interesting article on how caching is done is a big polish social network, nk.

ElasticMQ is a messaging server, with a Scala, Java, and an Amazon SQS-compatible interface.

Envers is an entity auditing framework, making it possible to store and query for historical data.

ElasticMQ is a message queue server, with Scala, Java, and an Amazon SQS-compatible interface.

For quite some time inheritance was the dominant model of structuring programs in OO languages like Java.

ElasticMQ is a message queue system, with Java, Scala and an Amazon SQS-compatible REST interface.

ElasticMQ 0.3 just got released!

Time to start blogging in 2012 :) I just released version 0.2 of ElasticMQ – a simple message queue system, which implements the Amazon SQS interface.

ElasticMQ is a simple messaging system, exposing an SQS-compatible REST interface.

Using Envers is now even easier!

Some Envers uses had problems because of the limited flexibility in specifying which fields from superclasses (especially those annotated with @MappedSuperclass) should be audited or not.

I will have the pleasure to speak on OpenBlend 2011, in exactly a week: 15th September 2011, which will take place in Ljubljana, Slovenia.

I think everybody will agree that writing modular applications and modularity in general is a good thing.

Wanting to explore Scala and some new Scala/Java libraries I started writing ElasticMQ.

Recently I tried deploying a web application which uses Envers into AS7, but unfortunately I encountered some problems (see the forum discussion).

The CAP theorem, stated by Brewer and proved by Gilbert and Lynch specifies a property of distributed systems.

Łukasz Antoniak, who is a regular contributor to Envers (thanks!)

Statically-typed languages are great because, well, they have static typing.

Confitura 2011 went past very quickly, it was a great conference and a great occasion to meet with the polish Java community on the SPOINA after-party.

In less than two weeks (11th June) I will have the opportunity to present a talk on CDI & Portable Extensions during the Confitura 2011 conference, organized by the Warsaw JUG.

This Friday (6th of May) I will have the pleasure to present two talks: one on Envers and one on Torquebox, thanks to an invitation from the RivieraJUG.

I’ve been looking at alternatives for java-style DI and DI containers which would use pure Scala; a promising candidate is the Cake Pattern (see my earlier blog post for information on how the Cake Pattern works).

Development of Hibernate4 is well under way, with the Alpha2 version released recently.

For almost a year we’ve been successfully using Torquebox together with CDI/Weld as a base for two of our services: JBison and Circular.

Lately we did some performance tuning, and in order to find out which methods are the hotspots I wrote a simple timing interceptor (it uses some code from a Seam forum post by Tobias Hill).

Continuing the mini-series on Dependency Injection (see my previous blogs: problems with DI, assisted inject for CDI and improving assisted inject), I took a look at how DI is handled in Scala.

In my two previous posts I wrote about some problems with DI and a solution to part of those problems: assisted inject (as known in Guice)/autofactories (my implementation for CDI).

DB test is a set of helper classes which let you run tests that use a database.

My last post sparked quite a lot of interest – thanks for all the comments both on the blog and on dzone!

Suppose you have a Product entity and that you want to implement a method which sends the product to a customer (let’s call it ship).

I’d like to welcome Erik-Berndt Scheper as our new Envers contributor.

I will be presenting Envers (data auditing in Hibernate) at JBoss One Day Talk 2010 in Munich, on the 1st of October.

Thanks to the patch provided by Matthew B.

Hernan Chanfreau backported some of the recent Envers changes and fixes from the 3.5 branch.

Tomek Szymański just commited two new features to cdi-ext.