Skip to Content

Wiki source code of ERRest Framework

Version 51.1 by Pascal Robert on 2011/03/15 01:38
Show last authors
1 = Presentations =
2
3 A presentation was made by Mike on February 16th 2010 about ERREST. The presentation was recorded and made available here :
4
5 http:~/~/webobjects.mdimension.com/wonder/screencasts/ERRest-2010-02-16.mov
6
7 It's also listed on the Screencasts page on wocommunity.org and in the podcasts RSS feed.
8
9 Mike also did a session about it at WOWODC West 2009, you can get this session by becoming purchasing a WebObjects Community Association membership.
10
11 Another ERRest session was made at WOWODC 2010, this one about ERRest integration with Dojo. You can get this session by becoming purchasing a WebObjects Community Association membership.
12
13 = Class names vs entity names =
14
15 A question was asked about situations where your EO class name is different from your entity name. Mike's answer was :
16
17 Everything internally is based on entity names. Your class name has very little to do with things other than your own source code. So for example:
18
19 routeRequestHandler.addDefaultRoutes("SamsSchool"); ~/~/ School.ENTITY//NAME//
20
21 Regardless, you will always have:
22 public class SamsSchoolController extends ERXDefaultRouteController {
23 ...
24 School school = (School) routeObjectForKey("samsSchool");
25
26 When those slides say "EntityName", they mean it :)
27
28 If you want to call it "School" to the outside, add this before you register the default routes for "SamsSchool":
29
30 ERXRestNameRegistry.registry().setExternalNameForInternalName("School", "SamsSchool"); ~/~/ "School", School.ENTITY//NAME//
31
32 After adding this, no other code changes. All you're saying is that the routes and type names that send over the wire should all say "School".
33
34 = WO HTTP adaptor =
35
36 The WO HTTP adaptor coming with WO 5.3 doesn't support PUT and DELETE operations, so you won't be able to use those two HTTP methods. You need to use either the 5.4 adaptor or the Wonder version of the adaptor.
37
38 = To-many relationships =
39
40 ERRest won't let you add or remove objects in a to-many relationship, it can only update an existing object that is in the relationship. To add a new object to a relationship, you first need to fetch (or create) the parent object and make a second call to create the object and add it to the relationship.
41
42 So let's say you have an existing Organization object and you want to add a Member to it. First, you need to fetch the Organization :
43
44 {{code}}
45
46 GET /cgi-bin/WebObjects/ra/Organization/1.json
47
48 {{/code}}
49
50 and after, you create a new Member :
51
52 {{code}}
53
54 POST /cgi-bin/WebObjects/ra/Organization/1/addMember.json
55
56 {{/code}}
57
58 = Same Origin policy =
59
60 If you are planning to offer your REST services to other people, they might run into Same Origin Policy problem. When using XMLHttpRequest on a page who is on a different domain than the REST service, XMLHttpRequest will tell you that it's not acceptable.
61
62 To get around that problem, many solutions has been found, but two of them are more accepted than the others : [[JSONP>>http://en.wikipedia.org/wiki/JSON#JSONP]] and [[HTTP//access//control>>https://developer.mozilla.org/en/HTTP_access_control]]. I didn't try the JSONP route, but I did try HTTP//access//control, and Dojo and Prototype are using this method to get around the Same Origin policy problem.
63
64 HTTP//access//control works by adding new headers in the request that says which HTTP methods the request wants to do, and it's send as a OPTIONS HTTP method. You MUST reply with some headers to this OPTIONS request. Support for those headers was added in ERRest somewhere in october 2010.
65
66 To enable the headers and support for the OPTIONS method, add this property:
67
68 {{code}}
69 ERXRest.accessControlAllowOrigin=*
70 {{/code}}
71
72 If you want to allow origin for only a specific host, change the value of the property to the IP or DNS name of the requester.
73
74 Now, sadly only newer (2008 or later) browsers support the HTTP Access Control standard. For older browsers, you have to support JSONP, or the [[window.name transport>>http://www.sitepen.com/blog/2008/07/22/windowname-transport/]]. JSONP is not integrated in JSONP, but you can use the window.name transport by enabling support with the following property.
75
76 {{code}}
77 ERXRest.allowWindowNameCrossDomainTransport=true
78 {{/code}}
79
80 == Dates ==
81
82 The default formatter for dates is :
83
84 {{code}}
85
86 %Y-%m-%dT%H:%M:%SZ
87
88 {{/code}}
89
90 If you want to work with the the GMT offset, you have to use this instead :
91
92 {{code}}
93
94 %Y-%m-%dT%H:%M:%S%z
95
96 {{/code}}
97
98 To change it, you have to set the "er.rest.timestampFormat" property :
99
100 {{code}}
101
102 er.rest.timestampFormat = %Y-%m-%dT%H:%M:%S%z
103
104 {{/code}}
105
106 If you are using Dojo, you can use dojo.date.stamp.toISOString and dojo.date.stamp.fromISOString to convert from or to a Java date object.
107
108 == JSON Schema support ==
109
110 ERRest have support for [[JSON Schema>>http://www.sitepen.com/blog/2008/10/31/json-schema/]] since october 2010. JSON Schema is like a mini-WSDL, where it describe which properties JSON objects have. Dojo use JSON Schema to perform client-side validation, which is cool because you can have some automatic validation based on your model, and validation is done even before the data is sent back to your REST service.
111
112 To get the schema, you need to check in your route action. For example, for the "index" action, you do:
113
114 {{code}}
115
116 public WOActionResults indexAction() throws Throwable {
117 if (isSchemaRequest()) {
118 return schemaResponse(yourERXKeyFilter());
119 }
120 ... do your normal work here
121 }
122
123 {{/code}}
124
125 And you call your REST route, but by adding "?schema=true" at the end of the URL. For example, ///ra/events.json?schema=true//. When you do that, a JSON Schema will be returned. Sample:
126
127 {{code}}
128
129 {
130 "name":"Event",
131 "properties":{
132 "isFullDay":{
133 "optional":true,
134 "type":"string",
135 "maxLength":5
136 },
137 "startDate":{
138 "optional":false,
139 "type":"string",
140 "format":"date-time"
141 },
142 "realDuration":{
143 "optional":true,
144 "type":"integer"
145 }
146 }
147 }
148
149 {{/code}}
150
151 So when you create a new Event with Dojo, if you try to put something else than a date in startDate, or you put a string in realDuration, it will fail because the schema says that startDate is using the date-time format, and that realDuration is a integer.