Èç¹ûÔÚÀàºÍ½Ó¿ÚÖÐдµÄ·½·¨ºÍÀà×¢ÊÍÉú³ÉwsdlÎĵµÖÐÒ²Éú³ÉÏàӦעÊÍ£¬²»ÖªµÀÈçºÎʵÏÖ£¿¿ÉÒÔ¿¼ÂÇ×Ô¼ºÐ´Ò»¸öjava2wsdlµÄ¹¤¾ß ĿǰµÄµÄ¹¤¾ßËÆºõûÓÐÖ§³ÖÕâ¸ö¹¦Äܵġ£ ÒòΪÏÖÔڵŤ¾ßÖ»ÊǶÁÈ¡annotationÎÞ·¨¶ÔÔ´Âë½øÐÐɨÃè Äã¿´Ò»ÏÂÕâ¸ö¾ÍÃ÷°×ÁË.http://blog.csdn.net/shenghuafen/archive/2005/08/02/444293.aspx ÔÚÎÄÕÂÖÐÓÐÒ»¶ÎÕâÑùµÄ»°: Õâ¾ÍÊÇÄã˵µÄÎĵµ×¢ÊͰÉ. 2.7 Documenting the Service
As we have seen, a WSDL 2.0 document is inherently only a partial description of a service. Although it captures the basic mechanics of interacting with the service -- the message types, transmission protocols, service location, etc. -- in general, additional documention will need to explain other application-level requirements for its use. For example, such documentation should explain the purpose and use of the service, the meanings of all messages, constraints on their use, and the sequence in which operations should be invoked.
The documentation element allows the WSDL author to include some human-readable documentation inside a WSDL document. It is a convenient place to reference any additional documentation that a client developer may need in order to use the service. It can appear in a number of places in a WSDL 2.0 document (as can be seen in the syntax summary presented later), thoug