I haven't tried using getCurrentContext() with EJB's deployed in other packages. It may work, because the current instance of MessageContext must stay in scope until the full treatment of the response message is completed.
It is normally not possible for the handler to access the backend service. According to the Axis Architecture Guide, the LAST handler in the server's request chain dispatches the request to the backend implementation after all the preceding handlers have been invoked. Besides, if you're dispatching to a session stateless EJB, you're not even sure about the way JBoss is creating instances of your EJB classes. I think that working things out with message contexts is much more straightforward. -----Message d'origine----- De : Arnaldur Hilmisson [mailto:[EMAIL PROTECTED] Envoyé : jeudi 24 novembre 2005 14:04 À : axis-user@ws.apache.org Objet : Re: using handlers to identify who is requesting service Hi, The problem is that the service bean is in another package (both packages are in jboss), does that work with the static method getCurrentContext()? And just to be sure... is there no way for the handler to call a method in the backend service before the actual call is made? Regards Arnaldur