>>My biggest issue is with the poor state of the documentation. It does not allow me to easily obtain a good level of competency, which I think is >>needed to feel like I can be productive with a tool, and to feel that the tool is worth using. >>Once I got past the documentation and did a lot of testing, and raising cases with Rocket Software (the guys here in Australia should now know their >>XDOM backwards!), I have a much clearer understanding of what is possible and what the limitations are.
Gregor, This is a good point and pretty important. When I approach a methodology like this and find that there is a lack of documentation then the question comes up. Do I spend the time to dig around to attempt to find enough documentation to make this tool usable? I consider using intrinsic tools the best choice, if the benefiit outweighs the cost. However if it is trivial to roll my own, or if there is an alternative extrinsic tool, then it is tempting to bail out. Availability of code examples (cookbooks, etc.), best practice guides, technical specs and so on, often determine which languages/tools I choose. Charles Shaffer Senior Analyst NTN-Bower Corporation _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
