| bsanjeev@gmail.com 2005-10-24, 10:32 am |
| Consider this scenario.
I have a orchestration that I intend to expose as an webservice. That
orch. in turn invokes a class which consumes other webservices and
returns some data to the caller. Some of those webservices that the
class calls, uses soap-header attribs, and also since I only get to
know the url and the webmethod to call during runtime(via the consumer
of bztlk orch), I had to create a generic webservice connector that
takes in wsdl url, method name and params and uses the
system.reflection to invoke a specific webmethod of a given webservice
url and I generate my webservice proxy class dynamically using
codedom.. To take care of soap-header attribs, I am using soap
extensions to inject xml to the outgoing message. Now, here is the
trick.. the calling app should have something like...
<webServices>
<soapExtensionTypes>
<add type="DRC.WSC.SoapClientExtension" priority="1" group="0" />
</soapExtensionTypes>
</webServices>
in its config in order to execute/invoke the soap extensions.
This orch. can be consumed by one or many services - could be an exe,
webservices, or an another orch. itself. If one of them is not going to
have this info. in their config, I would not be able to invoke soap
extensions to inject the header info. To give you an idea from the
architecture perspective.. the above scenario somewhat looks like..
Caller(app, ws, orch.) --> app.config, web.config comes from here
|
---> orch.(DRO) that invokes DRC
............|
............---> DRC invokes WSC
..................|
..................---> WSC invokes soap extensions --> msg gets sent
Now, how do I go about keeping that config info. within the DRO or its
children instead of expecting the clients to have(submit) that info.
everytime they want to consume this orch.?
DRO is the orch. that invokes a .net class DRC which has a reference to
WSC.
I hope I was clear, any help or suggestions on this would be much
appreciated.
|