Nested WCF Services
-
Hi All, The current application that I'm working on is made up of several modules which have a WCF tier to expose them to other projects. There is then another project which will consume all of these modules and then use these to perform logic and then expose itself with another WCF tier. E.g. Core | | | | \/ \/ Module1 Module2 etc etc When I execute a test that should access the Core WCF methods which then in turn should call a number of methods from the underlying modules which have a WCF tier, I get the following error: WCF_Core_Test.Class1.TestViewOrder: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail] : Could not find default endpoint element that references contract 'OrderHistory_API.ILogic' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element. Basically the core WCF wants to know about each of the endpoints for the underlying modules, even though these are correctly working when they standalone. Shouldn't all of the be done automatically when I add a service reference? Any help would be appreciated. Phil
-
Hi All, The current application that I'm working on is made up of several modules which have a WCF tier to expose them to other projects. There is then another project which will consume all of these modules and then use these to perform logic and then expose itself with another WCF tier. E.g. Core | | | | \/ \/ Module1 Module2 etc etc When I execute a test that should access the Core WCF methods which then in turn should call a number of methods from the underlying modules which have a WCF tier, I get the following error: WCF_Core_Test.Class1.TestViewOrder: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail] : Could not find default endpoint element that references contract 'OrderHistory_API.ILogic' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element. Basically the core WCF wants to know about each of the endpoints for the underlying modules, even though these are correctly working when they standalone. Shouldn't all of the be done automatically when I add a service reference? Any help would be appreciated. Phil
If I understand you are essentially calling a WCF service from within a WCF service method correct. In which case, then yes all the end points need to be defined. The code doesn't know that it is executing from within a service, an exe, or a webpage, it just knows it needs to connect to a service and needs to know how.
I know the language. I've read a book. - _Madmatt