Thank you for the reply. I think I would still have a problem using a handler that stored a context because I would then need to access this context from inside the service interface. This works fine if you are only receiving one request at a time but when you start having concurrent requests you are left with a situation where you have no way to know from the service interface implementation which context you are supposed to pull information out of. You are left with the same problem which is not having a way to pass any additional information through your generated service interfaces. Please correct me if my thinking is incorrect. I am really trying to find a solution to this problem.
Thanks, Matt Troutman ________________________________ From: Virtual Light [mailto:[EMAIL PROTECTED] Sent: Thursday, May 22, 2008 9:01 AM To: [email protected] Subject: RE: How to access SOAP headers from inside generated service interfaces? If you want to access the headers the way to do that would be through a handler. You would then need to store the information that you need in an object (normally a context) that would be accessible to your application. Regards, Bill ________________________________ > From: [EMAIL PROTECTED] > Subject: How to access SOAP headers from inside generated service interfaces? > Date: Wed, 21 May 2008 16:42:15 -0400 > To: [email protected] > > Hello, > I am hoping someone can help me with this problem. I am generating a > service from WSDL that contains a lot of soap headers. When my service > interfaces are generated there doesn't appear to be any way to access > the incoming headers through the generated service interfaces. I know > that I can access the headers from inside the generated > MessageReceiverInOut class but that is not where you are supposed to be > writing your code. Is there just something I am missing? I don't want > to have to change generated code that will get stomped on any time I > need to make a change to my WSDL and regenerate. It seems like the > service generator should allow for the soap headers to be exposed to the > service interfaces by means of access to the messagecontext directly or > by the MessageReciever pulling them out and passing them to the service > interface as an additional argument. > > Thank you for taking the time to read my question. > > Matt Troutman > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
