No. Although, Jakarta XML Web Services's roots come from JAX-RPC, Jakarta XML Web Services is a completely different component than JAX-RPC.

One of the main difference between JAX-RPC and Jakarta XML Web Services is the programming model. A Jakarta XML Web Services based service uses annotations (such @WebService) to declare webservice endpoints. Use of these annotations obviates the need for deployment descriptors. With Jakarta XML Web Services, you can have a webservice deployed on a Java EE compliant application server without a single deployment descriptor. Apart from these, other additional features (such asynchronous callbacks etc) are also present.

Yes.

Yes from https://maven.java.net/content/repositories/releases/com/sun/xml/ws.

Run the following command

$ wsgen or wsimport -version

Alternatively, each Jakarta XML Web Services jar has version information in its META-INF/MANIFEST.MF.

((BindingProvider)proxy).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "..."); 
            

You can do the following:

HelloService service = new HelloService();
Hello proxy = (service.getHelloPort());
((BindingProvider)proxy).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "userfoo");
((BindingProvider)proxy).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, "passbar"); 
            

USERNAME_PROPERTY, PASSWORD_PROPERTY are used primarily for service requests. I think when you instantiate Service, it fetches WSDL and the server is returning 401. You could try any one of the following solutions.