anchor.diff:  ....
   
   As you can see, this generated class extends the main client entry point
  -in JAX-WS, `javax.xml.ws.Service` . While you can use `Service`
  +in JAX-WS, `jakarta.xml.ws.Service` . While you can use `Service`
   directly, this is far simpler since it provides the configuration info
   for you. The only method we really care about is the `getEchoPort()`
   method, which returns an instance of our Service Endpoint Interface. Any
  
positive.code: ....
  package echo;
  
  @javax.jws.WebService(endpointInterface="echo.Echo")
  public class EchoImpl implements Echo
  {
     public String echo(String arg0)
  
negative.code: artifacts called "wrapper classes" will be generated for you at deploy
  time. This actually goes beyond the JAX-WS specification, which requires
  that wrapper classes be generated using an offline tool. The reason for
  this requirement is purely a vendor implementation problem, and since we
  do not believe in burdening a developer with a bunch of additional
  steps, we generate these as well. However, if you want your deployment
  to be portable to other application servers, you will unfortunately need
  