Hi All, As per the off-line discussion I had with Jayanga, the problem was solved after a patch having the mentioned fix, was applied to the pack.
Thanks. *Dilan U. Ariyaratne* Software Engineer WSO2 Inc. <http://wso2.com/> Mobile: +94775149066 lean . enterprise . middleware On Mon, Nov 24, 2014 at 9:47 AM, Jayanga Dissanayake <jaya...@wso2.com> wrote: > Hi Anjana/Dilan, > > This is caused by the new json.gson implementation. It keeps the message > structure in the ConfigurationContext, which doesn't get updated with > service redeployment. > > I fixed this in [1]. So the same patch will solve this as well. > > [1] https://wso2.org/jira/browse/CARBON-15077 > > Thanks, > Jayanga. > > *Jayanga Dissanayake* > Senior Software Engineer > WSO2 Inc. - http://wso2.com/ > lean . enterprise . middleware > email: jaya...@wso2.com > mobile: +94772207259 > > On Mon, Nov 24, 2014 at 9:27 AM, Dilan Udara Ariyaratne <dil...@wso2.com> > wrote: > >> Hi Anjana and Jayanga, >> >> Is this a known issue and if yes, is there a fix involved with this? >> >> Thanks. >> >> >> *Dilan U. Ariyaratne* >> Software Engineer >> WSO2 Inc. <http://wso2.com/> >> Mobile: +94775149066 >> lean . enterprise . middleware >> >> On Mon, Nov 24, 2014 at 6:22 AM, Anjana Fernando <anj...@wso2.com> wrote: >> >>> Hi, >>> >>> @Jayanga, I guess this will be gone by what you just fixed recently in >>> the JSON builder. >>> >>> Cheers, >>> Anjana. >>> >>> On Sun, Nov 23, 2014 at 8:29 PM, Dilan Udara Ariyaratne <dil...@wso2.com >>> > wrote: >>> >>>> Hi All, >>>> >>>> I have been following some of the DSS 3.2.1 Samples and found out that >>>> an update made to the order of parameters of a data service xml only >>>> appears >>>> to reflect after a server restart. >>>> >>>> To be more specific on the issue, >>>> let me take an example and describe. >>>> >>>> With Ref. to: https://docs.wso2.com/display/DSS321/JSON+Mapping+Sample >>>> I tried here to add an employee using the post method with an input >>>> JSON. >>>> The order of key-value pairs of the JSON was according to the default >>>> order of parameters >>>> of the data service definition. >>>> >>>> Then I changed the order of expected parameters using the data service >>>> xml editor >>>> and retried. Still it accepted the same JSON without any error. >>>> >>>> Only after a server restart, an exception was thrown saying that the >>>> order of input JSON keys >>>> were not according to the definition which means the update only >>>> affected after restart. >>>> >>>> Shouldn't these updates be taken into effect while the server is >>>> running? >>>> >>>> Appreciate any feedback on this. >>>> >>>> Thanks. >>>> >>>> *Dilan U. Ariyaratne* >>>> Software Engineer >>>> WSO2 Inc. <http://wso2.com/> >>>> Mobile: +94775149066 >>>> lean . enterprise . middleware >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Anjana Fernando* >>> Senior Technical Lead >>> WSO2 Inc. | http://wso2.com >>> lean . enterprise . middleware >>> >> >> >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
