S
Srinivas Munigala
Guest
Even for PATH parameter, you need to map tt object to single path parameter (as shown in attached file). And your request would be as below: http://localhost:8980/ttQueryPath/rest/ttQueryPathService/test/{"Country":"India","Name":"OpenEdge","Address":"iLabs","Address2":"","City":"Hyd","State":"AP","PostalCode":"400005","Contact":"Gloria Shepley","Phone":"(617) 450-0086","SalesRep":"HXM","CreditLimit":66700.00,"Balance":903.64,"Terms":"Net30","Discount":35,"Comments":"This customer is on credit hold.","Fax":"","EmailAddress":""} But, I would suggest to map temp-table / dataset like objects to body instead of path / query parameter as it would be very easy to send json format data in body rather path / query. From: Stefan Drissen [mailto:bounce-14941@community.progress.com] Sent: Thursday, September 25, 2014 12:47 PM To: TU.OE.Development@community.progress.com Subject: RE: [Technical Users - OE Development] REST input to temp-table? RE: REST input to temp-table? Reply by Stefan Drissen I understand the query part. How should the path be mapped? From what I see so far, using a temp-table / dataset as input from the path / query is not going to give a usable solution. Maybe an example based on tt above will help. I have defined the following rest resources: /lala/{adm_nr}/{debtor} - /lala/621/1010 /lala/{adm_nr} - /lala/621?country=NL /lala - /lala?country=NL The first allows me to get one entity using its key. The second and third allow me to search entities using a partial key (adm_nr = company) and query parameters The only sensible way I see of achieving this at the moment is to define all input temp-table fields as input parameters. Is this correct? Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...