I have few questions on the low-level architecture of Axis.
1. According to the architecture guide of Axis, it states that there are 3 chains of handlers that a MessageContext object has to go through before being serviced
i) Service ii) Global iii) Transport.
IIRC, Service handlers i.e., Request/Response handlers can be used to pre-process/post-process SOAP messages. But how can a developer use Transport and Global handlers and what is the main purpose of these handlers?
2. What would be acting as a transport listener if I deployed the Axis as a WAR in a web application server. How does the control get back to the Application server if I deployed an EJB component as a web service?
EJB would be hosted by the application server and web service would be deployed in the Axis. So control has to go back to the application server .... how does this work?
Can anyone point/help me in understanding the lower level workings of Axis?
Any tutorials/references would also be appreciated!!!
Thanks, Vivek
_________________________________________________________________
MSN Toolbar provides one-click access to Hotmail from any Web page – FREE download! http://toolbar.msn.com/go/onm00200413ave/direct/01/
