Welcome Welcome to our blog about all kind of topics that are related to software development. We blog about:
SOA, BPM, EDA, ECM and all the other buzz words. Beware some post might not be so common as you think. We are not scared to go against main stream thoughts.
Technologies like java, maven, springframework, OSGi and front end technologies and frameworks like jQuery, DWR, Flex.
Finally to make this happen we need tools and of course a Mac (well some of us do). So we blog about that as well.
Linked in We now have a linked in group, join the group if you are a regular reader and want to see who else reads this blog.

|
By jettro, on February 29th, 2008
OSGi has a service spec called http.service (see Service Compendium document of the OSGi Alliance). Felix has an implementation for it that is based around jetty 4.x. Since we are at jetty 6.1.7 at the moment I thought about trying to create an implementation of my own. Not that it is really necessary, you can expose resources without complying to the spec (see my other post).
But the spec is there for a reason, so let’s try to adhere to it first. The specification is up to the following two interfaces and one exception.
- HttpContext – Enables bundles to use provided information about a servlet or resource during registration.
- HttpService – Enables other bundles to dynamically register sevlets or resources into the Http Service URI namespace.
- NamespaceException – Thrown when a problem arises during registration of a servlet or resource into the Http Service UIR namespace.
At first I tried to create my own implementation for these interfaces. It did not look to hard, but in the end I found the following patch which made my life a lot easier. jetty6 patch
To be able to understand the implementation of an Http Service using jetty, you should understand the basics with respect to Jetty. In a forthcoming post I’ll talk more about these details. Within this post I’ll concentrate on the using of the service. I do need to make a few remarks. What if you do not want to apply the patch, change the pom, etc. Well you can download the one I have created from here : org.apache.felix.http.jetty-0.9.0-GRIDSHORE.jar. Another thing I would like to stress is the current state of the bundle. There are a lot of TODO’d in there. It looks like security is not implemented as it should. There is a completely different implementation at the ops4j website. One disadvantage is the level of control, need to look into that thing again. It is much more complicated, uses other bundles of the pax project. It does look interesting, but for me it is not easy enough. Another implementation is available at the sling website. But again a lot to graps before you can start. So for now I have chosen to continue with the slightly limited implementation, adhere to the spec and my bundles should work with the others as well.
Read more to learn about the sample using http.service and maven to build the bundle.
Continue reading Creating a jetty based OSGi HttpService for apache felix
By freddie, on February 21st, 2008
In my post “Why ECM should play an important role in the Business Process and SOA discussion” of February 11th, 2008 I made a statement “that we need to close the loop between inbound – outbound – inbound communication” and find a way to “prevent each developer, application and PC user to become its [...]
By jettro, on February 18th, 2008
This is a very small blog item. Still I want to share it with you all using the mac and vmware fusion. This morning I had a problem with my virtual machine. I could not ping a linux ubuntu image running mysql for some reason. I still did have internet connection from the vm, [...]
By jettro, on February 15th, 2008
This is my third post in the osgi basics series. The topic of today is embedding a servlet container within an osgi container. Of course I am continuing to use felix and now I start using jetty from mortbay. Starting from version 6.1.x, jetty is packaged as a bundle in itself. It is very [...]
By Allard, on February 13th, 2008
We all know how a typical web application is usually built up. The image at the side rougly displays the different layers that are to be found in an application. Typically, the user interface layer receives HTTP requests, calls one or more methods in the Business logic layer, and responds with an HTTP message [...]
By jettro, on February 13th, 2008
I already wrote before i have a Mac. I do not use the internet explorer on the mac and if I am using a windows machine I mostly use opera or firefox. Why am I telling you this, well that means I do not very regularly test on internet explorer. The previous post from [...]
By freddie, on February 13th, 2008
This Post is all about laughing and not to worry to much about SOA, BPM, ROI, CEP. I came across “Greg the Architect” and his small movies underpin a lot of what i have written about lately.
If you do not see the youtube movies in this page, you have to install the flash [...]
By jettro, on February 13th, 2008
This is the second step in a series of items about exploring the felix osgi container and some sidesteps to make life easier while developing osgi bundles. You can find the first step here: http://www.gridshore.nl/2008/02/10/starting-with-osgi-using-apache-felix-step-1/
This is so easy, I do not want to spend to much time here. There is a special maven [...]
|
|