Dear Internet Surfer!
Why don’t you share an interesting problem from your firsthand experience and lets see if we are interested in solving it together?
For the un-initiated, I am working on my lesser liked topics in the programming world, JS and WS!
I had recently started appreciating the WS without XML/Annotations a few weeks back, but to my surprise, the XFire implementation is no more supported in Spring 3.x hence I had to fall back on XML and Annotations.
I could come up with a working example of contract first WS development from here, and I was happy to see things working as expected, except for the inherent pain of seeing and using XML/Annotations.
This made me re-visit my understanding of whether to use java-first or wsdl-first approach for development.
I was initially a supporter of java-first simply due to my dis-liking for XML, now it seems a wsdl-first approach can keep the concentration of implementation towards the data structure of the messages that go to-and-fro.
That said, if I develop a java-first implementation, and give the 3rd party implementation team the link to the wsdl, does the 3rd party implementor stand to loose anything?
Either way’s even if they are using something other than java to consume the services, they have to wrap the response as per their conveneince, the only tradeoff that I seem to have is the structure of the wsdl message is not the fundamental change item, but the java method arguments become the items that define/control the change.
The only flexibility that I might be loosing here is the power of functional programming language, as-in imagine if a functional programmer implements a wsdl as per my current understanding, I question, does that programmers changing of the wsdl based on the arguments that come and go, affect(ease/pains) my implementation?
To conclude, do I stand to loose anything if I *still* go the java-first implementation way?
Couple of days back at work, I got my first opportunity to document the requirements for a particular moderation flow.As a practice we document everything in microsoft project management tool(read: ms word).
And the pain of tracking the changes, without review/comments is unacceptable!
Hence with the motivation set in, this is the template that I could come up after a *lot* of thinking:
|As a||I want to do …||So that…||Only If…||My action affects…|
and here’s an instance of an entry derived from that template:
|moderator||See new artefacts entered by users||I can validate the contents.||There are new artefacts available in the system.||Displaying the artefacts with ability to go to next artefact and/or approve/disapprove them.|
I have modified the actual text that was prepared for generality and not keeping office work in public!
Incase you have not already guessed, this instance deals with viewing artefacts for moderation.
While preparing this template, I was not cent percent aware of the domain that I was dealing with and also, I was new to this module, maybe that can work in favour of most people in similar situation!
What do you think? Does this template gives you the ability to cover all/most scenarios in your development story?
We are one year young on this 19th day of January 2011.
Let us look back as to what we had planned to achieve and what all was materialized!
Any plans/suggestions are welcome.