Correct Answer : Option (C) : All of the above
Explanation : If you are deploying into a Java EE 5 (or better) container, you may simply create a bean that is annotated with javax.jws.WebService or javax.jws.WebServiceProvider and deploy that into a container in your web application.
Correct Answer : Option (A) : True
Explanation : It will generate the configuration (a file called sun-jaxws.xml) and wrapper beans required to expose your service.
Correct Answer : Option (C) : Both (A) and (B)
Explanation : Spring provides a factory that can export beans annotated with javax.jws.WebService or javax.jws.WebServiceProvider inside the Spring context and then publishes the services using the JAX-WS runtime.
Explanation : You can build a Java-based web service on Solaris that is accessible from your Visual Basic program that runs on Windows.
Explanation : The web service interface can change over time without compromising the client's ability to interact with the service.
Explanation : Exposing a stand-alone SOAP endpoint using the SimpleJaxWsServiceExporter or the support for JAX-WS in a Java EE container in conjunction with Spring is simple, but these solutions ignore the largest cross-section of developers—people developing on Tomcat.
Correct Answer : Option (B) : jaxws:endpoint
Explanation : For our example, we’ll embed CXF since it’s robust, fairly well tested, and provides support for other important standards like JAX-RS, the API for REST-ful endpoints.
Explanation : Tomcat doesn’t support JAX-WS by itself, so we need to help it by embedding a JAX-WS runtime. There are many choices, and you’re free to take your pick. Two popular choices are Axis2 and CXF, both of which are Apache projects.