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 Allard, on January 27th, 2009
 Using Spring, it is easy to inject any instance with its dependencies, as long as the instance is managed by the Spring container. This typically means that the to-be injected beans are configured in the XML configuration. However, sometimes, it is impossible or ugly design to have objects managed by the Spring container. For example, when using a Rich Domain Model , your application will instantiate domain objects that contain domain logic, and thus need their dependencies to be injected.
A commonly seen strategy to inject these dependencies is to call a static method from the constructor. This static method will inject the newly instantiated instance with its dependencies using a reference to Spring’s application context. Although this method seems effective, it is purely limited to dependency injection. Spring offers a lot more, such as transaction support and security.
Spring’s load time weaving capabilty offers a more complete way to inject your unmanaged instances, making them no different than any spring managed instance.
Continue reading Injecting Domain objects with Spring
By Ben, on January 26th, 2009
Following a trackback to your own blog entry can be interesting from time to time. Today, for instance, I was led to an interesting blog from quite some years ago on the sys-con site by Michael Yuan entitled “Is Ruby Replacing Java? – Not So Fast”. In his blog, Michael talks a bit about why he thinks Ruby and RoR will not push Java out of the web application development arena. Part of his argument is that each development system tends to etch out a niche for itself, to attain dominance there and to be almost impossible to force out due to the traction it gathers in that niche.
His other argument, I think, is far more interesting and fundamental to the understanding of software engineering. To quote Micheal:
Instead, it matters far more to have better requirement gathering, better customer feedback, better development process, better trained developers, and better development tools (e.g., IDEs). In software engineering speak, the actual implementation of a system using a specific programming language has the lowest value in the value chain, and can be easily outsourced.
To put it another way (a way that I have tried to get many people to understand at different times):
It’s not about the language, people!!!
Continue reading It’s not about the language, people….
By freddie, on January 26th, 2009
Curious?
No it was not (yet) the news on ISIS Papyrus, neither was it the fact I almost won the Pullitzer price (I have first to write sensible things)
read on…
Continue reading What did 800 visitors a day bring to our blog and why we are going to pass the 1000!
By jettro, on January 23rd, 2009
For a while I am experimenting with flex. I wrote quite some posts about flex and security and I started writing about the Springframework BlazeDS Integration project. One thing that I do not really like about the configuration is the way to configure the remoting. All the hassle with the service-config.xml that needs to be available on the client as well as on the server. Not really nice. Using the maven way of creating a jar with these config files and unzipping this jar into the web server project as well as the client flex project is a way. Still, not ideal when developing in your ide when you want to add a new remote service.
What is the arternative? On the serverside, the mentioned spring project is doing a good job. You do not have to configure all endpoints. But you still need something on the client.
This post talks about a mechanism to enable you to loose all this configuration on the client
Continue reading Flex remoting without configuring the client
By jettro, on January 18th, 2009
 Sunday morning, it is raining, and I am playing with the new mac. I was browsing through the default bookmarks and stumbled upon the widgets download page. Usually I do not use these nifty little apps a lot. Which is about to change. I have found some nice widgets that will make my life on the mac easier.
This post is about those widgets, hope you find them useful as well. I’ll discuss a widget for storing passwords,
Continue reading widgets for the mac
By Ben, on January 18th, 2009
The other day I noticed that a bulb had burned out in my room. Which meant that I had to get a new bulb and replace the one that had failed. The act of replacing the bulb, perhaps surprisingly, led to some aggravation. Let me tell you about it.
The lamp in question does not take old-fashioned lightbulbs. No, this is a relatively modern lamp: it takes halogen spots. Halogen bulbs, as you might know, are not screwed into place. They use pin connectors which you stick into a recepticle which clamps onto the pins to prevent the bulb from falling out. In the case of smaller halogen bulbs a spring clamp suffices. Halogen spots are a little heavier, which means that their recepticles use two screws to clamp down on the pins.
My lamp does not just use halogen spots: my lamp is a product of early industrial design, which means that it is something really special. My lamp, you see, is the modern version of track lighting. Track lighting was very popular in the 1970′s: it consisted of a track with electrical leads in it on the ceiling. The lamps themselves were movable modules which clamped onto the track and used either metal hooks to hook onto the electrical leads or metal plates pushed onto the exposed leads by a spring. Track lighting allowed you to create the lighting form of your desire (more or less).
The modern track consists of two metal cables encased in plastic (thick enough not to slack, adjustable for length and isolated against contact by hands). In order to make electrical contact, the lamp modules use screw clamps and screws with a pointy tip. One clamp grabs onto one cable and if you tighten the screw the pointy tip just pierces the plastic isolation and makes contact. The clamps connect to a cradle that houses a recepticle for a halogen spot. And some ornamental metal bits cover the cradle up, making it difficult to electrocute yourself accidentally.
There is a simple and straightforward procedure to replacing a lightbulb in this lamp:
- Undo the clamp screws on the correct cradle and take the cradle down from the cables for easy access.
- Undo the recepticle clamp screws and remove the dead bulb.
- Put in a new bulb and tighten the recepticle screws.
- Put the cradle back on the cables.
- Tighten the clamp screws until both pointy ends have punctured the plastic and are making electrical contact.
Simple, easy. Any idiot can do it. And yet, after a few minutes fumbling with overhead screws and dropping screws and so on, I am left with one aggravated question:
WHO THE HELL DESIGNS A CEILING LAMP THAT REQUIRES A SCREWDRIVER TO REPLACE A BULB?
Continue reading The parable of the lightbulb
By jettro, on January 16th, 2009
 Since my last article about springframework and hippo “Roadtrip from springframework to hippo 7” I have made a lot of changes to the code and moved my project to the hippo forge. With this post I want to explain what I have changed and in some situations why. I will not repeat the stuff I already talked about in the previous post. One of the biggest areas I made changes in, is the stability of the solution. I used the Circuit Breaker implementation as discussed by Allard in his post “Bring some stability to your architecture“. Stability comes with reconnect options and a component that guards the repository. In case of to many errors the connections are closed and after a certain cool down period, new connections are created.
One remark I like to make is about the connection pool. This pool is probably not production ready. I did not do any performance tests and it is a bit rough around the edges.
That said, let’s move on and start talking about the solution.
Continue reading Connecting to Hippo ecm using a springframework connector
By jettro, on January 6th, 2009
  In my previous post I have created a flex client with a BlazeDS back-end using the spring blazeds integration. If you are familiar with the springframework, the configuration became a lot easier at the server side. Still I had some problems to get it easier at the client as well. I still needed the services-config.xml file with some destinations in it. In the side note I already mentioned another way of creating the client using Spring-ActionScript project. As it turns out, you do not really need Spring-ActionScript to loose the configuration. Still it gives you some help and I like to experiment with it a litle bit.
This post is going through the steps to refactor the current books-overview sample application of mine into a cleaner project using Spring-ActionScript.
Continue reading Creating the flex client using Spring ActionScript
|
|
