James, In the 1.0 release there will not be an Axis servlet, there is now a Servlet Context listener which is a standard way of initializing things and is supported by adding an entry to web.xml.
As for issues in moving to a new SOAP platform....One of the things that will need to happen is that there will need to be an extension of the ResourceHandler class for the given platform. Today we ship with a ResourceProvider which is Axis specific. The ResourceHandler class is an abstract implementation of a GenericHandler (JAX-RPC handler). This class is the front-door which receives the requests, so this is where most of the potential issues would occur. The other thing to look out for is the classloaders. Typical J2EE environments provide a classloader heirarchy to alleviate class clashing. It's really just something to look out for. Classes like Qname are not based on interfaces, so each platform has their own implementation which may, or may not, cause issues. The only other thing I can think of off the top of my head is the versions of JAX-RPC and SAAJ implemented/supported on the given SOAP engine. Axis used version 1.2 so if it uses 1.1 then you may run into issues. The main thing is to try it, and document everything...ask questions...then share your findings with the list ;-) -Sal -----Original Message----- From: James Lorenzen [mailto:[EMAIL PROTECTED] Sent: Monday, July 25, 2005 9:50 AM To: [email protected] Subject: Effort, if possible, to move to a SOA and non-Axis SOAP Engine Our team might have to move our apache-muse web services under a SOA (Services Oriented Architecture). They also their own SOAP Engine implementation. They are trying to stay away from Axis. If we made this move, what issues can you forsee arising, if any? For example, it seems the entry point for muse is the WsrfAxisServlet. This is a different servlet and URL in our architecture. Hope this isn't too broad a question. James. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
