AXIS vs JAX-WS for Web Service Client?

The client side of JAX-WS is part of the standard Java API, and the reference implementation is reliable and performant, while Axis requires 3rd party dependencies. If you don't need any functionality implemented by Axis and not offered by JAX-WS, I really don't see any reason why you should opt for Axis and not for JAX-WS.

One thing to keep in mind in the comparison. If your web client app has a need to connect multiple users to your back end simultaneously, the Java reference implementation has no way of doing this (at least that I've been able to find). By using the Authenticator class, you're tied to only allowing a single user to ever access the back end and you don't even control the lifespan of that user connection.

The Authenticator is a surprisingly difficult-to-use API with severe limitations.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.