JAX-WS simplifies application development through support of a standard, annotation-based model to develop Web Service applications and clients. It replaces remote procedure calls defined by JAX-RPC and allows developers to write message-oriented and RPC-oriented web services. JAX-WS uses platform-independent technologies like HTTP, SOAP and WSDL and provides tools for generating artifacts and importing WSDL definitions.

3. Both servlet endpoints and EJB endpoints can have an object implementing the WebServiceContext interface injected using the @Resource annotation

4. Allows developers to write message-oriented as well as RPC-oriented web services

5. With JAX-WS, the developer does not generate or parse SOAP messages

6. the platform independence of the Java programming language beacuse jax-ws uses techology definined by the W3C : HTTP, SOAP and WSDL

10. Much easier to expose method as web services

12. Data Binding : JAX-WS leverages the Java Architecture for XML Binding (JAXB) 2.1 API and tools as the binding technology for mappings between Java objects and XML documents.

13. Support for MTOM : can send binary attachments such as images or files along with Web services requests

14. Support for SOAP 1.2 : JAX-WS supports both SOAP 1.1 and SOAP 1.2

15. Development tools : JAX-WS provides the wsgen and wsimport command-line tools for generating portable artifacts for JAX-WS Web services

16. Support for WS-Addressing (JAX-WS 2.1) : The new API enables you to create, transmit and use endpoint references to target a specific Web service endpoint

17. Support for JAX-WS 2.1 features : JAX-WS 2.1 introduces the concept of features as a way to programmatically control certain functions or behaviors

19. Both servlet endpoints and EJB endpoints can have an object implementing the WebServiceContext interface injected using the @Resource annotation

21. @WebMethod -> only the methods annotates with @WebMethod will be exposed to be a web services method

30. TargetNameSpace : XML namespace

31. ServiceName : wsdl:service

32. EndpointInterface : The qualified name of the service endpoint interface. This annotation allows the separation of interface contract from implementation.

33. PortName : wsdl:portName

35. Action : The XML namespace of the the WSDL and some of the XML elements generated from this web service.

38. mode: Represents the direction the parameter flows for this method. Possible values are IN , INOUT and OUT . INOUT and OUT modes

41. Name : DEPRECATED:

43. document/literal wrapped -> is that methods on a document/literal wrapped endpoint can have multiple parameters bound to the body of a SOAP message,

45. Use : Defines the encoding used for messages used in web service. Can only be LITERAL for JAX-WS 2.1. Def LITERAL

47. javax.xml.ws.RequestWrapper : annotates methods in the Service Endpoint Interface with the request wrapper bean to be used at runtime. Only the className is required in this case

48. javax.xml.ws.ResponseWrapper : annotates methods in the Service Endpoint Interface with the response wrapper bean to be used at runtime. Only the className is required in this case

50. javax.xml.ws.RequestWrapper : annotates methods in the Service Endpoint Interface with the request wrapper bean to be used at runtime. Only the className is required in this case

51. javax.xml.ws.ResponseWrapper : annotates methods in the Service Endpoint Interface with the response wrapper bean to be used at runtime. Only the className is required in this case

52. javax.xml.ws.ServiceMode : allows the Provider developer to indicate whether a Provider implementation wishes to work with entire protocol messages or just with protocol message payloads

53. javax.xml.ws.WebEndpoint : Used to annotate the get PortName() methods of a generated service interface

54. javax.xml.ws.WebFault : This annotation is generated by the JAX-WS tools into service specific exception classes generated from a WSDL to customize to the local and namespace name of the fault element and the name of the fault bean and to mark the service specific exception as one generated from WSDL

55. javax.xml.ws.WebServiceClient : specified in this annotation is sufficient to uniquely identify a wsdl:service element inside a WSDL document

56. javax.xml.ws.WebServiceProvider : Annotation used to annotate a Provider implementation class

58. javax.xml.ws.Feature : The @Feature annotation is used to enable/disable a feature to use for a web service endpoint implementation class. This annotation is used with @BindingType annotation.

62. WsGen : Tool to process a compiled javax.jws.WebService annotated class and to generate the necessary classes to make it a Web service

63. WsImport : Tool to import a WSDL and to generate an SEI (a javax.jws.WebService ) interface that can be either implemented on the server to build a webservice, or can be used on the client to invoke the web service

65. 1. Code the implementation class.

66. 2. Compile the implementation class.

67. 3. Use wsgen to generate the artifacts required to deploy the service.

68. 4. Package the files into a WAR file.

69. 5. Deploy the WAR file. The web service artifacts (which are used to communicate with clients) are generated by the Application Server during deployment.

70. 6. Code the client class.

71. 7. Use wsimport to generate and compile the web service artifacts needed to connect to the service.

72. 8. Compile the client class.

73. 9. Run the client.

75. The implementing class may explicitly reference an SEI through the endpointInterface element of the @WebService annotation, but is not required to do so. If no endpointInterface is specified in @WebService , an SEI is implicitly defined for the implementing class.

76. The business methods of the implementing class must be public , and must NOT be declared static or final .

77. Business methods that are exposed to web service clients must be annotated with javax.jws.WebMethod .

78. Business methods that are exposed to web service clients must have JAXB-compatible parameters and return types.

79. The implementing class must NOT be declared final and must NOT be abstract .

80. The implementing class must have a default public constructor .

81. The implementing class must NOT define the finalize() method.

82. The implementing class may use the javax.annotation.PostConstruct or javax.annotation.PreDestroy annotations on its methods for life cycle event callbacks.

83. Example package helloservice.endpoint; import javax.jws.WebService; @WebService public class Hello { private String message = new String("Hello, "); public void Hello() {} @WebMethod public String sayHello(String name) { return message + name + "."; } }

86. Example public class HelloClient { @WebServiceRef(wsdlLocation="http://localhost:8080/helloservice/hello?wsdl") static HelloService service; public static void main(String[] args) { try { HelloClient client = new HelloClient(); client.doTest(args); } catch(Exception e) { e.printStackTrace();}} public void doTest(String[] args) { try { System.out.println("Retrieving the port from the following service: " + service); Hello port = service.getHelloPort(); System.out.println("Invoking the sayHello operation on the port."); String name; if (args.length > 0) { name = args[0]; } else { name = "No Name"; } String response = port.sayHello(name); System.out.println(response); } catch(Exception e) { e.printStackTrace();}}}

88. use XML messages for communications between Web services and Web services clients

89. invoking services at the XML message level is provided by the Dispatch client API

90. The Dispatch client can send data in either MESSAGE or PAYLOAD mode

92. JAXB objects : JAXB objects can only be used with SOAP or HTTP bindings

93. javax.xml.soap.SOAPMessage : You can only use SOAPMessage objects with SOAP

95. Asynchronous : requests and responses using the invokeAsync method with a callback or polling object

97. extend the java.lang.reflect.Proxy