Hi Matt, Can't you inject the message context into your service implementation class:
http://xfire.codehaus.org/MessageContext I have used that in the past to get the Soap header and all kinds of other goodies: The MessageContext The MessageContext class stays with an XFire invocation from start to finish. It is useful for: * Accessing Messages, their xml streams and their headers * Storing/retrieving properties which need to be shared across different handlers * The service being invoked * The XFire instance being invoked --- Matthew Kerle <[EMAIL PROTECTED]> wrote: --------------------------------- Hi Yogesh. Thanks for your input, the application will be deployed to an intranet,so will don't need any SSL or message digest encryption. The client apidoc link is good but doesn't that apply to the client side? My question relates to accessing HTTP or SOAP headers from theServiceImpl class on the server side from xFire... -- Matthew Kerle ITConsultant Canberra,Australia Mobile: +61404 096863 Email: < Matthew Kerle Web: Matthew Kerle Yogesh Chawla - PD wrote: Hi Matthew,Here is some xfire documentation on using basic auth. I think you could use this in conjuction with https (aself signed cert on the server is probably fine):http://xfire.codehaus.org/Client+APIBasic Auth on Tomcathttp://tomcat.apache.org/tomcat-5.5-doc/realm-howto.htmlPerhaps this will work for you?Cheers,Yogesh---------------------------------------------------------------------To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email ---------------------------------------------------------------------To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
