manually defining endpoints (SharePoint 2010 BDC WCF data source related)

[Amr Ellafy]

first thanks for this wonderful library !

the issue:

I developed a simple web service to expose data to SharePoint as an
External Content Type. SharePoint supports WCF data sources.

in order to add a WCF data source in SharePoint Designer you have to
provide two urls:

1- Service Metadata url
2- Service Endpoint url

I refer to this post https://groups.google.com/d/msg/servicestack/GMd3JwNq7eA/kEmslhX1GhYJ
were Demis advised to use the either /servicestack/soap11 or /
servicestack/soap12, but this doesn't work with SharePoint designer
and i keep getting the following error "Cannot find any matching
endpoint configuration"

already said, 'SyncReply.svc' and 'AsyncOneWay.svc are deprecated now
and SharePoint will accept them during as Service Endpoint url while
you setup WCF data source, but later on querying the following error
will raise:

System.ServiceModel.EndpointNotFoundException: There was no endpoint
listening at http://myserver/ServiceStack/SyncReply.svc that could
accept the message. This is often caused by an incorrect address or
SOAP action. See InnerException, if present, for more details. --->
System.Net.WebException: The remote server returned an error: (404)
Not Found.

[Demis Bellot]

Note: SyncReply.svc no longer exists and has been deprecated for a while.

So you'll need to concentrate on the WSDL that's generated by ServiceStack.

/servicestack/soap11 and /servicestack/soap12 should return the WSDLs but will only do so if you've mounted servicestack at /servicestack

If you installed the ServiceStack.Host.AspNet version from NuGet it's hosted at / - so will be /soap12

and if you installed ServiceStack.Host.Mvc version from NuGet it's hosted at /api - so will be /api/soap12

Doing a GET against against /soap11 will return a WSDL whilst POST'ing the SOAP message will execute the web service.

So you first need to make sure the urls you give SharePoint designers are returning WSDLs.

Cheers,

--
- Demis

http://twitter.com/demisbellot

http://www.servicestack.net/mythz_blog

[Amr Ellafy]

yes, they return WSDLs but SharePoint somehow is trying to discover endpoints by reading the WSDL file so it locates SyncReply.svc as it is defined in the generated WSDLs by ServiceStack. 

can i override ServiceStack configuration so i can have real endpoints i can use with SharePoint ?

[Demis Bellot]

I can't see the SyncReply.svc declared in the WSDL here.

What version of ServiceStack are you running?

Can you upload a copy of your WSDL?

Cheers,

[Amr Ellafy]

Hi,

I'm using the recent package on NuGet (version: 3.5.1)

WSDL can be found here : http://pastebin.com/wMZ3Asib

you can see SyncReply.svc defined at the end of the WSDL.

[Demis Bellot]

okie I see the problem, it was falling back to the old urls if the incoming request urls wasn't the same:

https://github.com/ServiceStack/ServiceStack/commit/affaa75f858145254578c7fd2fae75ed8ca8ab42#L4L58 

I've updated and pushed a new version to NuGet v3.54 can you do an update and let me know if that fixes it?

Cheers,

[Amr Ellafy]

Thanks for your quick response ! NuGet latest version now is 3.5.3, is it the same ?

[Demis Bellot]

Crap apologies, I forgot to hit submit, it should be there now:

https://nuget.org/packages/ServiceStack/3.5.4 

Can you try again?

[Amr Ellafy]

simply awesome ! very good job !

[NSZ]

Hello,

Check below link for SharePoint 2010 Introduction to Publishing

https://www.youtube.com/watch?v=aDl8pZ1eaBQ&list=PLzmjg4MO6i7J5t45SFRsmuxL2dUaELxAy

Thanks

NSA