Second, you should use WSDL if at all possible. If you have existing Java code, use Java2WSDL to generate a first cut at a WSDL file. Then you can clean up the file and
Third, use TCPMon as a tool when you’re debugging. Doing so can save you many hours of frustration and give you some insight into what your code is doing.
Fourth, ask Axis to generate a JUnit test case for you and write a decent set of tests for your application.
Fifth, make sure you use the Ant
Much like XML-RPC, the applications for Axis and Web services are broad. Anywhere you can think of invoking a method on an object is a possible candidate for a Web service. The primary areas where Web services can make a difference are as
Invoking functionality on a machine not owned by you.
Invoking functionality on a machine that uses a different language and/or platform.
Today, most of the activity in Web services involves using Web services to integrate heterogeneous applications within the same organization. We’re beginning to see some use of Web services to integrate applications across the Internet. eBay, Google, and Amazon.com have started developer programs that allow access to their applications via Web services technologies.
Perhaps your company will be the
XML is being accepted as a way of transferring information between application programs and computers. The volume of data that’s being
The answer is that you may not want to sign or encrypt the entire document. You may only want to sign or encrypt an element or a few elements. Perhaps an XML document represents a bunch of information, but you only care about or want to be responsible for part of that information. Think of a document that represents a complex agreement among multiple parties. Each part may only want to sign the part of the document they’re responsible for. Likewise, some of the terms of the agreement may be between only two parties, but the entire agreement stands or
Technically, the solution rests with a pair of specifications from the World Wide Web Consortium (W3C): the XML Signature Syntax and Processing Recommendation and the XML Encryption Syntax and Processing Recommendation. The XML Signature Recommendation describes how to use digital signatures and hashing/message
XML Security is the xml.apache.org project that’s implementing these four recommendations. The project was started in September 2001 when the XML Security project at the University of Siegen in Germany donated a code base that implemented the Canonicalization and part of the XML Signature Recommendations. Since then, the project has completed implementation of the required portions of the XML Signature Recommendation and has begun implementation of the XML Encryption Recommendation. There has been some cooperation with the Apache Axis project, in particular a set of Axis handlers that can be used to digitally sign SOAP messages. These handlers use the older SOAP Signature specification, which has been superseded by the WS-Security specifications. The Web services project is interested in building a complete WS-Security implementation.