DfsProxyGen 6.7 is missing the field "Service model file" mentioned in Dev Guide

devnull69
devnull69 Member
edited September 17, 2013 in Documentum #1

Hi all,

I was trying to generate a C# proxy using the DfsProxyGen.exe as mentioned in the Development Guide 6.7

The screenshot and text mentions a field called "Service model file" where I should specify the file created by the generateArtifacts ant task. But this field is not available in the DfsProxyGen.exe shipped with 6.7 (or even 6.6) of the SDK.

Problem: I was able to successfully create a C# proxy by specifying the Shared Assemblies for the Productivity Layer. Calling the methods exposed by the Custom Web Service was not a problem until I tried to catch a ServiceException thrown by the service method. It ended up unhandled inside the proxy cs file without "bubbling up" to the caller method in my project.

Using the standard Productivity Layer objects for e.g. ObjectService I was able to successfully catch those exceptions as FaultException<SerializableException>, but with the proxy it just failed. Checking the proxy shipped with the sample AcmeCustomService I found out that it is totally different to the one created for my custom service. The only obvious difference is the missing service model file ...

Regards

Thomas

Tagged:

Comments

  • devnull69
    devnull69 Member
    edited September 12, 2013 #2

    I have found a solution ... but it's not really an option

    Even though the System Requirements section of the Dev Guide mentions ".NET Framework 3.5 SP1 or later", the Exception handling won't work with .NET Framework 4.0. As soon as I set the destination framework from 4.0 to 3.5, the Exceptions start to bubble up to the caller as expected.

    So, is there any alternative that allows using .NET Framework 4.0 together with a C# proxy generated by DfsProxyGen.exe?

  • christopher.imes
    christopher.imes Member
    edited September 14, 2013 #3

    Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility.  Questions written to the users' own "Discussions" space don't get the same amount of attention and can go unanswered for a long time.

    You can do so by selecting "Move" under ACTIONS along the upper-right.  Then search for "Documentum" and select the very first result that appears.  This will place you in the Developer Network subspace of the Documentum community.

    For further guidance on engaging with the communities for Documentum and related products, please refer to the IIG Communities Getting Started Guide.

Categories