G
gcherivi
Guest
Yes, the generated mapping is the correct one. Mapping XML won't generate the mapping, if parameter name are similar (in Paramater and Request section as below screen shot) i.e. CustID. The mappings rules are implicitly executed by Runtime. If parameters names are differ or if we map to http body, tooling will generate the mapping in the mapping.xml file. Hope it helpful! Regards, Ganesh From: bfvo [mailto:bounce-bfvo@community.progress.com] Sent: Wednesday, January 22, 2014 7:07 PM To: TU.Mobile@community.progress.com Subject: RE: Server 500 error when GETting data from an Business via REST RE: Server 500 error when GETting data from an Business via REST Reply by bfvo I see your point. One more try however. I'm trying to call: @openapi.openedge.export(type="REST", useReturnValue="false", writeDataSetBeforeImage="false"). @progress.service.resourceMapping(type="REST", operation="read", URI="?filter=~{filter~}", alias="", mediaType="application/json"). method public void ReadSysUserRBE(filter as character, output dataset dsuser): Just a basic READ method (of the CRUD methods). if I take a look in the mapping.xml in the staging dir however I see no corresponding mapping for the filter parameter: mapping:MappingBean id="mapping" xmlns:mapping="http://www.progress.com/caf/mapping1.0" ![CDATA[ mapping:messageMapping xmlns:conditional="http://www.progress.com/caf/mapping1.0/conditional" xmlns:mapping="http://www.progress.com/caf/mapping1.0" mapping:mapInput/ mapping:mapOutput conditional:conditionalRuleSet conditional:if condition="${(rest.resourcename == 'SysUserRBE') and (rest.operationname == 'bfv.system.SysUserRBE..ReadSysUserRBE') and (rest.verb == 'GET')}" mapping:rule source="${idl.param['dsuser']}" target="${http.body}"/ /conditional:if /conditional:conditionalRuleSet /mapping:mapOutput /mapping:messageMapping ]] /mapping:MappingBean Is this correct or should there be a mapping for the filter (input) parameter as well? The stack is trying to tell something about parameters. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...