+1, This is great. What if the response also shown as an XML? so that we can see the entire structure of the response message, rather than some strings.
Thanks, Waruna On Wed, Mar 16, 2011 at 7:05 PM, Ruchira Wageesha <[email protected]> wrote: > Hi Azeez, > > Along with the schema import support of the Tryit, we will have to get rid > of form-field ui as it lacks the flexibility. i.e. If the the types are > complex and have a certain depth, then it's very hard to give a form-field > based ui. > > So the tryit ui is being redesigned(with the help of chanka) by giving user > an XML editor(editarea) where he can modify payload. When the editor is > loaded for the first time, it will contain a sample payload as we can see in > Soap UI like tools. Then user can replace '?' (see the payload of the > attached images) with their desired content. > > Further, the Stubs generated from Mashup Server's stub generator tool, was > also modified to accept the payload as a Badgerfish JSON. As we get the > sample payload XML in the tryit ui, user can get the sample payload > Badgerfish JSON by simply calling {service}.{operation}_payloadJSON() method > of the stub. Then he can simply modify the payload JSON, instead of creating > BF JSON himself. > > I have attached the images of new tryit layout below. Please let this > thread know your comments. > > Thanks, > Ruchira > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- ------------------------------------------------------------------------- Waruna Ranasinghe Senior Software Engineer, WSO2 Mobile: +94 724 318285 BLOG: http://warunapw.blogspot.com www.wso2.com - "Lean . Enterprise . Middleware"
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
