Tool kits for designing and building Web services have a core set of capabilities, including SOAP messaging integration, plus automated help for WSDL wrappers and debugging distributed Web services.
Choosing the right tools depends on the language and environment. But the most interesting question isn't "Which tool kit?" but "For which application, and how?" When users answer this question they reveal much about the current state of Web services.
New Tools, New Choices
Stories in this report:
- Users Face Big Decisions Over .Net, Java and Web Services
- The Story So Far: Application Development
- .Net vs. Java: Five Factors to Consider
- Overview: Building Web Services
- University's Data Traffic Unsnarled
- Skimping on Java Development May Do More Harm Than Good
- The Security Challenges of Web Services
- Taking Enterprise Application Integration to the Extremes
- The Payoff From Software Quality
- How to Thrive in the Hot Java Market
- Development on the QT
- The Future of Software Development
- Case Studies in Application Development
- The Future of Application Integration
- Reporter's Notebook: Application Develoment and Web Services