Albert, I have indicated that one can write a AXIS Handler, but that is dis-connected processing. i.e. Handler is invoked after or before the end point is called, hence the SOAP header or Body or Message viewing ability is part of pre-processing or post processing, which is not what is intended. I need a way of accessing those details, while I am in the end-point, wouldn't that be graceful? Hope there is a way forward on that. Regards, Santosh
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mon 30/06/2003 18:50 To: [EMAIL PROTECTED] Cc: Subject: Re: SOAP Message or SOAP Body or SOAP Header access from endpoints (H OW TO) I am quoting my own message. http://marc.theaimsgroup.com/?l=axis-user <http://marc.theaimsgroup.com/?l=axis-user&m=105650439419684&w=2> &m=105650439419684&w=2 this should work. Quoting [EMAIL PROTECTED]: > All, > > I have recently started to use AXIS and need help on How to access the SOAP > Message or SOAP body or SOAP Header, with which a end point was invoked in > the first place. > > e.g. I have a interface definition in terms of an WSDL. How do I access the > actual SOAP message delivered on the wire in the end point Implementation > class. > > One can write an AXIS Handler to access that, but that is completely > dis-jointed from the end point, hence I wanted some tips on How to do it in > the end point. > > Please help. > > Regards, > > Santosh > > Santosh Joshi > > TASKFORCE development, > +44(1473)605316 > a.p.solve Limited > > http://www.apsolve.com <http://www.apsolve.com> > > ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ <http://horde.org/imp/>
