I agree with Ben. Can we have some of this "subclasses for web services" discussion on the design call so we can more quickly get on the same page?
-Burke On Mon, Apr 16, 2012 at 10:41 AM, Ben Wolfe (Commented) (JIRA) < [email protected]> wrote: > Ben > Wolfe<https://tickets.openmrs.org/secure/ViewProfile.jspa?name=bwolfe>commented > on [image: > New Feature] RESTWS-221 <https://tickets.openmrs.org/browse/RESTWS-221> > *Decide how sub-classes should be > handled*<https://tickets.openmrs.org/browse/RESTWS-221> > > What is the goal of preventing: POST patient { gender: 'M' } ? Preventing > this forces users to know the API more than they should need to. Is it only > because we intend to break the patient/person inheritance eventually? > DrugOrder will always extend order, so updating Order properties from > DrugOrder seems ok. > > Why not just leave them as they are in the openmrs api world? > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators<https://tickets.openmrs.org/secure/ContactAdministrators!default.jspa> > . > For more information on JIRA, see: http://www.atlassian.com/software/jira > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
