Period in RESTful WCF Starter Kit - wcf

I am using RESTful WFC's WebInvoke and WebGet attribute classes. In the UriTemplate parameter I want to capture a variable which includes the period character. How do I do so?
So
[WebInvoke(Method = "PUT", UriTemplate = "{id}")]
[OperationContract]
TItem UpdateItemInXml(string id, TItem newValue);
I would like it to match the url:
http://service.svc/A.1

I couldn't find a way to do so. The solution I implemented was to base64 encode the id in the URL.

Related

WCF Service not restfull

My first WEB servicee usinf Visual Studio 2013 Express WEB, and I can't make it restfull. basically want to return a json string and got the following service definition;
[OperationContract]
[WebInvoke(Method = "GET",
ResponseFormat = WebMessageFormat.Json, UriTemplate = "Name")]
string Name();
Implementation of Name just returns a string which is shown when I Invoke the function through the WCF Test Client, but calling the http://localhost:58116/Service1.svc/Name returns nothing. I was expecting a json representation of the Name.
Any idea's?

REST service does not get POST payload

I have a big problem.
I created a WCF service.My POST declaration looks like this:
[OperationContract]
[WebInvoke(UriTemplate = "json/put",
Method = "POST",
BodyStyle = WebMessageBodyStyle.Wrapped,
RequestFormat = WebMessageFormat.Json,
ResponseFormat = WebMessageFormat.Json)]
string PutData(string jsonText);
I was expecting that when I'm sending data (I'm using fiddler2 to test it) that it will automaticly "put" into the jsonText variable.
The service works, but there is no data :(.
Can anybody help? The whole project
WCF expects the JSON payload to be deserialized into a type. Try creating a class that is shaped like your JSON payload and use that as the parameter type.

Inconsistent treatment of quotes in JSON payload

Why is it possible to send in a WCF DataService the following JSON string:
{ SomeElement: 'val1', SomeOtherElement: 'val2' }
whilest you have to send in an normal WCF Service like
[OperationContract,
WebInvoke (Method = "POST",
ResponseFormat = WebMessageFormat.Json,
RequestFormat = WebMessageFormat.Json,
BodyStyle = WebMessageBodyStyle.Wrapped)]
public string SomeMehtod(string SomeElement, string SomeOtherElement)
the following JSON string
{ "SomeElement": "val1", "SomeOtherElement": "val2" }
This inconsistency is not clear to me. Why do I have to use double quotes in the normal web serive whilest I can omit the quotes for the element name in WCF data services?
Maybe somone knows an answer to this....
I am very familiar with the internal plumbing behind WCF's JSON parsing infrastructure, and essentially, the plumbing that takes care of the second situation is really designed to support "strict" standards-complaint JSON.
It's just a coincidence that the first situation works with non-compliant JSON. Don't read into it. It was not a conscious design decision. Hope this clears up confusion!
For more details, you can just explore DataContractJsonSerializerOperationFormatter, DataContractJsonSerializerOperationBehavior, and DataContractJsonSerializer using Reflector.

Changing JSON response root node message in WCF

I created a REST GetTime Service in WCF and the service returns JSON as the response message. Also the WebMessageBodyStyle is set to wrapped so it would have an ID associated with that data it returns. But when I use Fiddler to test my service the response string is:
{"GetTimeResult":"2010614104013"}
As the response above the ID of the string is GetTimeResult, I'm wondering is there any way on changing that bit of test to timestamp. So it looks like this:
{"timestamp":"2010614104013"}
Cheers.
If you are using the DataContract/DataMember attributes in your code, you add a name (as well as some other named parameters).
[DataMember(Name = "timestamp")]
public string GetTimeResult
As pointed out in this article, suppose you are not using a data member explicitly in a data contract and want to return, say, a timestamp as a simple string for the response. Just use the annotation [return: MessageParameter(Name = "timestamp")] with your operation contract method:
[OperationContract]
[WebInvoke(Method = "GET", UriTemplate = "/timestamps", ResponseFormat = WebMessageFormat.Json, BodyStyle = WebMessageBodyStyle.Wrapped)]
[return: MessageParameter(Name = "timestamp")]
string GetStringTimestamp();

WCF Rest Service Client - Parameter Names are case sensitive

When using the following interface to talk to PHP from .NET, .NET builds the request body XML with parameter names barcode and branch. The parameter names should be Barcode and Branch. Yes, the PHP server is case sensitive.
Am I forced to capitalise my parameter names? or can I specify names using attributes?
Many Thanks
Neil
[ServiceContract]
public interface IStockEnquiryService
{
[OperationContract]
[WebInvoke(Method = "POST", BodyStyle = WebMessageBodyStyle.Wrapped, ResponseFormat = WebMessageFormat.Xml, UriTemplate = "")]
Branches GetStockInfo(string barcode, string branch);
}
Try applying the MessageParameterattribute to the method arguments and specify the right case in its Name property.