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

Python and Access-Control-Allow-Origin

Ok, here is something that probably happens a lot: You are trying to do some .js (if not you should get started), and write some code in your favorite ide, save it, load it in your favorite browser and everything is ok. You are a good developer and start making packages and loading your files when you need them: lazy . You don't want to overdo things, and manage to put stuff into a bunch of .js and .html. You load them into your browser and BAM: Access-Control-Allow-Origin   Failed to load resource: Resource failed to load   So now you are all WTF, right? You Google (some would Bing ) it and sure enough, what you were thinking is the ugly true and by now you get angry as a bird. Why? Ok, for those that didn't know there is a thing called Same Origin Policy , that forbids you from loading stuff across different domains and bla bla bla... So what does it has to do we you? You sure enough are not trying do load across domains, your are loading a file... you may think, but no...
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...
Kommentar veröffentlichen
Next »