1. First of all, I understand that for the application server that we are using, the supported Java EE version is 1.4. This means that there is no JAX-WS 2.0. Instead there is JAX-RPC 1.1, so we would have to use JAX-RPC 1.1. Is this important at all? Next time, if the application server is to be upgraded to one that supports Java EE 5, would there be an issue?
3. I have also read about web services implemented with session bean, in a book about EJB 3.0. This is in contrast to implementation using servlets, as described in the article above. Does that mean that if I have EJB 3.0, I can implement the web service with session beans, but if I am using just Java EE 1.4, I have to do it as how the article above described?
1. When we code a session bean as a web service, is JAX-RPC or JAX-WS being used?
2. About the Apache Axis, you mean that there would be a need for a separate web application to host the web service?. How would the web service on this web application be able to access our application, which is another web application?
we are using Sun Java System Application Server 8.2, which is based on J2EE 1.4. So we can't use JAX-WS, right?
I would want to ensure that if the application service is upgrade to a Java EE 5 compliant one, the web service will still work with minimum changes.
If we use Axis2, we can use it on the current application server, and next time, when it's being upgraded, it's still no issue. Right?