Direkt zum Hauptbereich

My language skills over time... update

Skills, as everything else, develop over time. Some get rusty though. I was once a very skilled c programmer, now I dread to manage memory myself. I suppose with time the tools change and the languages change with it. I don't think there is A Best Language for coding. They have different objectives, some are good in some context, some even fun, some are not fun but they do the thing they are suppose to best. It took me a long time to realise, that the language I choose is not strictly to communicate with the computer but with the next developer (including myself). The computer will interpret and run the code once it works, but the next developer is in charge of understanding the code, the Why and How, so she/he can maintain it, use it, or even learn from it.

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

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.
Kommentar veröffentlichen
Next »

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
Kommentar veröffentlichen
Next »