Timing Seam Injection

One of the main concepts in Seam is the Bijection of Components. Seam can inject components into eachother and can outject them for use in for instance XHTML pages. However, bijection takes time, how much time is mainly dependent on how much dependencies need to be loaded. However, normally you cannot easily measure the overhead time of bijection.

Revised Seam Application Scoped Repositories

In yesterdays blog I wrote about repositories in a Seam application that have application scope. In this blog I also presented a possible solution. In this blog I wish to present a better solution that also makes use of the Seam Managed Persistence Contexts.

Seam Application Scoped Repositories

Sometimes bugs are so obvious that they hit your blind spot. This happened to me last day, while working on a Seam project at one of our customers. I was writing JMeter tests as part of the QA team to stress test the application, and I got some weird exceptions...

Custom Repository Layout in Gradle

For one of the projects I work on with some colleagues, we have a number of jar files, which are not part of any Maven(-ized) repository. We decided to upload these jar files to the downloads page of github, so that we have a url which we can refer to. Using some customization in our Gradle build file, we managed to download these jars as though they were hosted on a Maven(-ized) repository.

usePlugin 'java'

repositories {
 mavenCentral()
 add(new org.apache.ivy.plugins.resolver.URLResolver()) {
  name = "GitHub"
  addArtifactPattern 'http://github.com/asikkema/adoptimizer/downloads/[organization]-[module]-[revision].[ext]'
 }
}

dependencies {
 compile "gdata:client:1.0@jar"
 compile "gdata:analytics:2.1@jar"
 compile "gdata:analytics-meta:2.1@jar"
}

There are other options, but this was the most terse we came up with.