Skip to main content

Blog Archive for kohsuke during February 2007

For some reason, the blogsphere suddenly noticed my year-old NLink project, so I'm getting a lot of traffic lately. Maybe I've never sent out the announcement, when I originally released it, so here it goes... Historically, JNI has been the only option to invoke native libraries. The problem with calling native libraries with JNI is that, for every method, you need to write a java method...
Hudson has always been distributed as a single war file, and the installation was as easy as dropping this war to your web container. I thought this was easy enough, but then people pointed out that installing a web container is not all that easy. There has been some discussion about this in the users list, and usual options like bundling Jetty was mentioned, but none of them seemed quite right...
This is a follow up to my previous post. A reader asked how my "danegrous classloader trick" works, and another reader asked if he can use this technique to run his applications (with JAXB 2.1) on JavaSE 6. I've got a few internal people who had the same question, so I'm going to explain how it works today. The following picture illustrates the basic design: When our code gets the control...
As Jave SE 6 adoption increases, it's getting more and more painful that you can't run JAXB/WS 2.1 tools in a straight-forward fashion on JavaSE; since we care about development experience, we decided that it's time to fix this. The crux of the problem is to load JAXB/WS 2.1 API in JavaSE 6, where 2.0 APIs are in the bootstrap classloader. So I needed to pull off some dangerous classloader...
Maven 2 is really a terrible terrible tool (with all the bugs, no documentation, verbose XML, ...), yet I'm finding it more and more useful these days. Hudson is now built on Maven2, and so does the JAX-WS RI extensions that I wrote. Glassfish v3 is also built entirely in Maven2. Since I rely more on Maven2, I wanted more Maven2 support in Hudson. It can already build a Maven project, but it...
Today is a release day of JAX-WS RI 2.1 (see the announcement.) Before I head for a party (I'm sure we can count on our managers to throw one for us!), here are a few things I wanted to mention in some details. Performance I hope you've seen the performance benchmark that we posted. I think numbers speak for themselves. Kudos go to our performance team and the SJSXP team. I also contributed a...
In this post I'm going to talk about the details of the benchmark Bharath did (kudos to him and the rest of the performance team.) For more about the JAX-WS RI 2.1 release in general, please refer to Vivek's post. Summary The basic idea of the benchmark is to have a lot of clients send a lot of requests to the server concurrently. The server echos back the data to the client, and then we...