![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
|
Welcome to Vista Forums we are your forum to discuss Windows Vista x64 and x86 systems. Whether you need help or just want to post an idea you have on Vista, this is the forum for you.
br> br> |
| |||||||
| | Thread Tools | Display Modes |
| | #1 (permalink) |
| Guest | Problem with web reference I have tried using BizTalk, a Windows app and a Web app to add a web reference to a WCF service that was generated using the Web Service Software Factory. I need to do this via a web reference because ultimately I'll be using BizTalk and I don't want to have to use proxy classes as this will require variables and hard coding in the orchestration that will be calling the WCF service which makes it more of a problem when deploying. The operation generated in the WSSF has a service implementation with a method: public bool PublishRequest(PublishMetaData request) where PublishMetaData is a business entity within the service. When I add this service (via the .svc in the web references dialogue) in any application the method signature changes to: public void PublishRequest(PublishMetaData request, out bool PublishRequestResult, out bool PublishRequestResultSpecified) Can anyone tell me why this would happen and more importantly how I can stop it as I NEED the signature to be as exposed in the service implementation? The reason I NEED it to be the same is because BizTalk web service support doesn't seem to extend to "out" parameters rather like it doesn't extend to arrays as return types. The service is bound using basicHttp binding. TIA, Martin |
| | #2 (permalink) |
| Guest | Re: Problem with web reference Hello, Competitive! What version of WCF do you use? RTM? This is serializer behavior - it thinks that bool return type can be null. To resolve this issue you can add XmlSerializerFormat attribute to the contract ( interface ) . Have a look for more info ( http://msdn.microsoft.com/msdnmag/is...n/default.aspx ) You wrote on Fri, 15 Dec 2006 04:22:00 -0800: CD> I need to do this via a web reference because ultimately I'll be using CD> BizTalk and I don't want to have to use proxy classes as this will CD> require variables and hard coding in the orchestration that will be CD> calling the WCF service which makes it more of a problem when CD> deploying. CD> The operation generated in the WSSF has a service implementation with a CD> method: CD> public bool PublishRequest(PublishMetaData request) CD> where PublishMetaData is a business entity within the service. CD> When I add this service (via the .svc in the web references dialogue) CD> in any application the method signature changes to: CD> public void PublishRequest(PublishMetaData request, out bool CD> PublishRequestResult, out bool PublishRequestResultSpecified) CD> Can anyone tell me why this would happen and more importantly how I can CD> stop it as I NEED the signature to be as exposed in the service CD> implementation? The reason I NEED it to be the same is because BizTalk CD> web service support doesn't seem to extend to "out" parameters rather CD> like it doesn't extend to arrays as return types. CD> The service is bound using basicHttp binding. CD> TIA, With best regards, Vadym Stetsyak. E-mail: vadym_s@ukr.net |
| | #3 (permalink) |
| Guest | Re: Problem with web reference Vadym, Many thanks that seems to have done the trick with web applications. BizTalk is still failing to add the reference but I'm guessing this is not something to do with the service as such, but more something specific to BizTalk as adding it to a web applicaiton works fine. Thanks for the help and the reference, it'll be going on my project blog today! Cheers, CD "Vadym Stetsyak" wrote: > Hello, Competitive! > > What version of WCF do you use? RTM? > > This is serializer behavior - it thinks that bool return type can be null. > To resolve this issue you can add XmlSerializerFormat attribute to > the contract ( interface ) . > > Have a look for more info ( > http://msdn.microsoft.com/msdnmag/is...n/default.aspx ) > > > You wrote on Fri, 15 Dec 2006 04:22:00 -0800: > > CD> I need to do this via a web reference because ultimately I'll be using > CD> BizTalk and I don't want to have to use proxy classes as this will > CD> require variables and hard coding in the orchestration that will be > CD> calling the WCF service which makes it more of a problem when > CD> deploying. > > CD> The operation generated in the WSSF has a service implementation with a > CD> method: > > CD> public bool PublishRequest(PublishMetaData request) > > CD> where PublishMetaData is a business entity within the service. > > CD> When I add this service (via the .svc in the web references dialogue) > CD> in any application the method signature changes to: > > CD> public void PublishRequest(PublishMetaData request, out bool > CD> PublishRequestResult, out bool PublishRequestResultSpecified) > > CD> Can anyone tell me why this would happen and more importantly how I can > CD> stop it as I NEED the signature to be as exposed in the service > CD> implementation? The reason I NEED it to be the same is because BizTalk > CD> web service support doesn't seem to extend to "out" parameters rather > CD> like it doesn't extend to arrays as return types. > > CD> The service is bound using basicHttp binding. > > CD> TIA, > > > With best regards, Vadym Stetsyak. E-mail: vadym_s@ukr.net > > > |
| |
| |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Best Reference | Bob | PowerShell | 6 | 11-21-2007 08:08 PM |
| Useful Reference lists Vista ready, not ready, problem hardware, software,what's been tested | Adam Albright | Vista General | 0 | 03-16-2007 09:25 AM |
| Useful Reference lists Vista ready, not ready, problem hardware, software,what's been tested | Adam Albright | Vista installation & setup | 0 | 03-16-2007 09:25 AM |
| Best reference for .NET for use with PS | Marco Shaw | PowerShell | 7 | 10-23-2006 01:40 PM |