Tulio Camminati

Release Plan

Mario: is of course the developer trying to save the princess

Princess: is the release

Barrels: are either feature requests or bugs

Hammer: reconsider / won't fix

Kong: release manager

Story: Mario starts at the wrong end. He is actually done developing at the time the release comes into action, but has to run his way up through the plan to make the release on time and help the princess. On the way up, there are all kind of features and bugs rolling down wanting to hurt Mario. He has no possibility whatsoever to get them done faster. However, it is in his power to keep some of them from getting done before he reaches the princess.

Kommentare

Beliebte Posts aus diesem Blog

Welcome People of People

You can take it out here. If you're nice, I shall come back to you.

ThreadLocal as an Enum - I'm not afraid to admit it!

Well, as disturbing as it might be, I am not afraid to at least admit it: I did not know about the elegance of the following construct: public enum TLData { INSTANCE; private final ThreadLocal< String > myData = new ThreadLocal< String >(); public String getMyData() { return myData.get(); } public void setMyData( final String myData) { this .myData.set(myData); } } Since you are using an Enum, nobody can create new members from outside, you don't have to care about privatizing any methods and you can access it as easy as: public class myClass { public void myMethod() { /** * setting the data */ TLData.INSTANCE.setMyData( "some data" ); /** * getting the data */ String myData = TLData.INSTANCE.getMyData(); } } Isn't that fancy? I had to admit I never thought of it myself. A colleague of mine had to put it under my nose.

JUnit testing services and clients with javax.xml.ws.Endpoint

Following situation: you have written some generic stub to use in your projects that creates a client for a service. Your client is smart and does some magic for connections (proxy, cache or other kind of magic). Or maybe you just have written a service for that matter. Anyway, you now want to test it. Unit testing the functionality of your methods is a must. But you still want to reach 100% coverage and need to test the service as it would run in real life. Then you can use the javax.xml.ws.Endpoint class. If you prefer figuring it out yourself, you can find the code (as a project for netbeans) -- here -- To follow the code examples as html click --here-- So here is how you do it: If you've coded nothing fancy, then you probably have a class like this: This is a generic client for opening connections to services. It gives you back a port of the type of your service where you can call your operation as a method of the port. It is very convenient if you h