Hi,
I don't believe we can have an actual comment in json[1]. The JSON should
all be data, and if you include a comment, then it will be data too. In
jaggery still it is same. We can have a designated data element called
"_comment".
Here sample that you can try out.
eg:
{
*"displayName_comment":"give the jaggery app name", *
"displayName":"Coffee Shop",
"urlMappings":[
{
"url":"/orders/*",
* "url_comment":"Comments for url mapping on URL",*
"path":"/controller/order.jag"
}
]
}
It is drawback of json.
References
[1] http://www.json.org/
On Sun, Oct 28, 2012 at 1:30 PM, Senaka Fernando <[email protected]> wrote:
> Hi all,
>
> $subject?
>
> Thanks,
> Senaka.
>
> --
> *Senaka Fernando*
> Member - Integration Technologies Management Committee;
> Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
--
*Madhuka* Udantha
http://madhukaudantha.blogspot.com/
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
