1. Does Jakarta XML Web Services 2.0 support JAX-RPC 1.X?
No. Although, Jakarta XML Web Services's roots come from JAX-RPC, Jakarta XML Web Services is a
completely different component than JAX-RPC.
2. What is the difference between JAX-RPC and Jakarta XML Web Services ?
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.
3. Can a Jakarta XML Web Services and a JAX-RPC based service co-exist?
7. How do I do basic authentication in Jakarta XML Web Services ?
You can do the following:
HelloService service = new HelloService();
Hello proxy = (service.getHelloPort());
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.
Use java.net.Authenticator class in your client application.
Provide a local access to the WSDL using catalog. There is a catalog sample in the jax-ws distribution.
Configure web.xml to allow GET requests without authentication
8. Which standards are supported by Eclipse Implementation of XML Web Services?
Web Services Addressing 1.0 - Core
Web Services Addressing 1.0 - SOAP
Web Services Addressing 1.0 - Metadata
Web Services Addressing 1.0 - WSDL Binding (RI