Reliance on special properties: _class, _id

[eduard93]

RESTForms currently relies on _class, and _id properties understand which object do we need to open.

Our goal is to remove or minimize this reliance.

Possible approaches:

1. Remove special properties from request body and pass them as url params
2. Force FORM classes to use %JSONREFERENCE = OID for properties and provide id property. What about child updates in this scenario?

Other ideas?

[isc-afuentes]

1. I guess PUT /:form in Form.REST.Object (updateFormClassObject) will have to be removed?

• I think that if %JSONREFERENCE=OBJECT is used in a create / update operation, new objects will be always created.
• If %JSONREFERENCE=OID is used, references will be like "relative": "Form.Test.Person,1", which I'm not sure if it's easy to use from a client application (e.g. Angular) because it won't be the object itself but a "pointer".

In the same way Form.Adaptor has a ClassMethod toJSON method called from Form.REST.Object, we could encapsulate in Form.Adaptor all needed CRUD methods and use them from Form.Adaptor. Then we can build UnitTest to test all Form.Adaptor behaviours converting data from/to JSON using %JSON.Adaptor and Form.Test.* classes.

[isc-afuentes]

Have a look at the pull-request #8

I've just submitted a quick change to support CRUD operations using %JSON.Adaptor:

• Create: POST /form/object/:class
• Update: PUT /form/object/:class/:id
• Read: GET /form/object/:class/:id
• Delete: DELETE /form/object/:class/:id

(I've removed the former PUT /form/object/:class/:id because its reliance on _id, _class. We can recover this behaviour later if we need it, but maybe this way we can have still a RESTful service)

We can define different %JSON.Adaptor mappings using class parameters FORMCREATEMAPPING, FORMUPDATEMAPPING, FORMREADMAPPING

Unitest available in: UnitTests.ObjectCRUD