Problems using .NET productivity layer objects calling a custom web service

devnull69

Hi,

someone in our company developed a custom DFS web service and sent me the WSDL URL. I used this URL to generate a C# proxy with DfsProxyGen.exe. It generated a .cs file for the service (called FileServices.cs).

I was able to create all the instances for the request (service context, repository identity, remote service, transfer profile, object identity, data object, reference relationship) using the .NET productivity layer objects. But the service method exposed by the FileServices web service expects two parameters, one of which is of type DataPackage, the other is of type OperationOptions.

Now, if I create instances for DataPackage and OperationOptions from the .NET productivity layer, I cannot use them as parameters to the service call ("Argument type Emc.Documentum.FS.DataModel.Core.DataPackage is not assignable to parameter type OurServices.DataPackage") where OurServices is the namespace of the remote service. The proxy seems to expose another DataPackage class (partial) which is required to use as a parameter to the service call.

Did I forget something important here? How can I use .NET productivity layer objects like DataPackage as parameters to custom DFS web services?

Regards

Thomas

devnull69

In the meantime I was able to help myself:

You'll have to add the productivity layer DLLs (whose classes you wish to exclude from the proxy) as "Shared assemblies" to the DfsProxyGen.exe together with the DataModel.Shared.dll and the Runtime.dll by copying the productivity layer DLL into the DfsProxyGen folder before calling it.