I assume endpoint[1] is the one exposed through APIM. If direct call to .jag [2] is returning the correct response, I don't see a reason why API Gateway would alter the response. We simply don't touch the message content. Jaggery doesn't get involved in this part of the gateway processing as well.
Can you try moving the Jaggery App to a different server and see if the result changes? (or you can try the latest nightly build of APIM) I went through the JIRA pointed by IsuruP. But was unable to find the commit that fixes the issue. Can you try deploying the fix as a patch to APIM and see if it solves the problem. BTW, API names look bit odd. eg: http://api.wso2con.com:8280/wso2_con_public_api/1.0/conferences/1/agendas/1/tracks/1/events >From an external developer point of view, I cannot understand why there are so many '/1' in there. And also top level API name has lot of duplication. The domain name api.wso2con.com says most of what is needed. right? How about something like, http://api.wso2con.com:8280/api/1.0.0/agenda/track/1/events? On Tue, Mar 4, 2014 at 11:05 PM, Isuru Perera <[email protected]> wrote: > Looks like an issue with the Jaggery version being used by APIM. May be > following is related? > > https://issues.apache.org/jira/browse/STRATOS-490 > > > On Tue, Mar 4, 2014 at 11:42 AM, Indika Sampath <[email protected]> wrote: > >> >> Hi API-M team, >> >> I encounter an issue with the JSON message in API-M. The WSO2 Con API >> backend currently deploy in the API-M. It has number of Jaggery endpoints. >> >> When I call the endpoint [1] I come up with the following JSON result. >> >> [ >> { >> "id": {}, >> "title": "Registration", >> "description": "Registration", >> "venue": "Ball Room", >> "eventTypeId": {}, >> "fromDateTime": "2014-03-25 08:30:00", >> "toDateTime": "2014-03-25 09:00:00", >> "isCrossTrack": {} >> } >> ] >> >> But If I call the same endpoint which is locally deployed Jaggery server >> [2] I end up with the following JSON result. >> >> [ >> { >> "id": "1", >> "title": "Registration", >> "description": "Registration", >> "venue": "Ball Room", >> "eventTypeId": "1", >> "fromDateTime": "2014-03-25 08:30:00", >> "toDateTime": "2014-03-25 09:00:00", >> "isCrossTrack": "1" >> } >> ] >> >> All the integer fields empty in the API-M JSON result. Can you guys look >> in to this issue. >> >> [1] curl -i -H "Accept: application/json" -X GET >> http://api.wso2con.com:8280/wso2_con_public_api/1.0/conferences/1/agendas/1/tracks/1/events >> >> [2] curl -i -H "Accept: application/json" -X GET >> http://127.0.0.1:9763/con_api/conferences/1/agendas/1/tracks/1/events >> >> Thank you. >> >> -- >> Indika Sampath >> Software Engineer >> WSO2 Inc. >> http://wso2.com >> >> Phone: +94 716 424 744 >> Blog: http://indikasampath.blogspot.com/ >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Isuru Perera > Senior Software Engineer | WSO2, Inc. | http://wso2.com/ > Lean . Enterprise . Middleware > > about.me/chrishantha > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- /sumedha b : bit.ly/sumedha
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
