Databases
StackOverflow2013
Postsdbo
POWCF Multiple contracts with duplicate method names
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWCF Multiple contracts with duplicate method names
    primarykey
    data
    text
    <p>I have a service with multiple contracts like so.</p> <pre><code>[ServiceContract] public partial interface IBusinessFunctionDAO { [OperationContract] BusinessFunction GetBusinessFunction(Int32 businessFunctionRefID); [OperationContract] IEnumerable&lt;Project&gt; GetProjects(Int32 businessFunctionRefID); } [ServiceContract] public partial interface IBusinessUnitDAO { [OperationContract] BusinessUnit GetBusinessUnit(Int32 businessUnitRefID); [OperationContract] IEnumerable&lt;Project&gt; GetProjects(Int32 businessUnitRefID); } </code></pre> <p>I then explicitly implemented each one of the interfaces like so.</p> <pre><code>public class TrackingTool : IBusinessFunctionDAO, IBusinessUnitDAO { BusinessFunction IBusinessFunctionDAO.GetBusinessFunction(Int32 businessFunctionRefID) { // implementation } IEnumerable&lt;Project&gt; IBusinessFunctionDAO.GetProjects(Int32 businessFunctionRefID) { // implementation } BusinessUnit IBusinessUnitDAO.GetBusinessUnit(Int32 businessUnitRefID) { // implementation } IEnumerable&lt;Project&gt; IBusinessUnitDAO.GetProjects(Int32 businessUnitRefID) { // implementation } } </code></pre> <p>As you can see I have two GetProjects(int) methods, but each one is implemented explicitly so this compiles just fine and is perfectly valid. The problem arises when I actually start this as a service. It gives me an error staying that TrackingTool already contains a definition GetProject. While it is true, it is part of a different service contract. Does WCF not distinguish between service contracts when generating the method names ? Is there a way to get it to distinguish between the service contracts ?</p> <p>My App.Config looks like this</p> <pre><code>&lt;service name="TrackingTool"&gt; &lt;endpoint address="BusinessUnit" contract="IBusinessUnitDAO" /&gt; &lt;endpoint address="BusinessFunction" contract="IBusinessFunctionDAO" /&gt; &lt;/service&gt; </code></pre> <p>Any help would be appreciated.</p> <p>Thanks, Raul</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USHaxElit
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWCF Multiple contracts with duplicate method names
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWCF Multiple contracts with duplicate method names
      1. USKonstantin Salavatov
      1. VTFavorite
    3. VO
      singulars
      1. POWCF Multiple contracts with duplicate method names
      1. This table or related slice is empty.
      1. VTUpMod
    1. COas @monO mentions in his answer - the actual individual method names must be unique in your service class. The WSDL doesn't know anything about your interfaces and all and it doesn't allow method overloading with different parameters; you need to make those method names unique over the entire service class!
      singulars
      1. POWCF Multiple contracts with duplicate method names
      1. USmarc_s
    2. COAh, I guess I gotta read up on how the WSDL is actually created. I thought that each contract has it's own namespace inside the WSDL.
      singulars
      1. POWCF Multiple contracts with duplicate method names
      1. USHaxElit
    3. CO...actually I find that pretty confusing, too. @marc_s: the WSDL does know about the different interfaces. They are exposed as dedicated ports with dedicated bindings.
      singulars
      1. POWCF Multiple contracts with duplicate method names
      1. USAlex
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload