Of SOAP, Design Patterns and JAVA
1. SOAP and XML Web Services is not simple. MS Visual Studio, Disco.exe and WSDL.exe makes it simple but it's not simple.(who the hell said it's simple)
2. I just finished reading this Thread at the Microsoft Community Forums and all I can say is...Patterns provide repeatable solutions but it's not always the BEST solution. For me it's always been
- Find what is most appropriate
- Find a solution that has the least impact on the existing structure
- Find a solution that requires least amount of maintenance effort
- and above all, come up with the cleanest, simplest and the most elegant solution suited for the business requirement
One of the many things that I've learned from peer reviews and consultation(and even asking the community) is, true enough, this people can give you a fresh perspective on how to solve the problems at hand, but their lack of real understanding and appreciation of the bigger picture called 'Your System" sometimes lead to further complication. A number of times, I had to drop tables, get rid of classes because my peers find it redundant...but eventually, I had to put it back up because the "bigger" picture requires it.
The Context of doing Reports/Presentation here was blown out of proportions because of "bad design" and the use of DataTables is inappropriate because it breaks OOD rules. DTO, on the other hand, doesn't provide as much simplicity for displaying tabular information.
Please don't tell me that just because Martin Fowler or Some Guy who Blogs at BLOGALLYOUWANTABOUT.NET writes everything he knows and says it works for him means your work should be done the same way. If that's ALL there is to Software Development work then Projects should be a walk in the park.
I think it takes skill and technical aptitude to use patterns, but maturity to choose which best fits the solution.
3. Saturday is a few days from now and I'm still at Arrays with Java. JDBC, JSP and Servlets are up next then probably Struts.