D
Darren Parr
Guest
[quote user="Peter Judge"] The GEN and MAP files are the same thing, basically; I'll call them the mapping file. GEN = "generated". If you have a GEN and a MAP file with the same name in the same (PROPATH) directory then the DOH will read the gen first and overlay the MAP contents. The GEN is intended to be changed only by PDSOE. The schema section in the mapping file is not used by the catalog at all. It is used to build temp-table and/or datasets on the fly for passing into the methods in the E or other business logic. Not sure what you mean by #3. The GET on the service's / was intended to replace the need for the GET /static/service.json catalog (as you can probably tell). I don't know if anyone/the JSDO is using it so I think you could quite easily replace that GET / with your own operation. [/quote] Thanks. When you say "overlay". What do you mean? Does the existence of the .map file supercede the .gen or is it doing some fancy matching up of the contents? What part does the schema play in a typical interaction from the JSDO when it calls PUT which then runs the Update method in the data object. We're passing a dataset to the handler from the client. Does it just pass it in as a handle without any checking to the data object or is it using its own schema defn in some way to verify the incoming json? I guess my question is what requirement is there for the schema defn in the .gen and the catalog to remain in sync? -D
Continue reading...
Continue reading...