[ https://issues.apache.org/jira/browse/OFBIZ-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184293#comment-14184293 ]
Scott Gray commented on OFBIZ-5790: ----------------------------------- Adrian, Jacopo, please don't think of my question as voicing a strong opinion, it really was just a doubt/concern of something I was unsure about. To be honest I don't see a need for an internal JSON type because I have no idea what we'd do with it. That doesn't mean there isn't a need, I just don't know what it is. At the moment I can only visualize JSON as an external input/output format for data that we already represent internally using Lists and Maps. I would never be concerned about whether a string contains JSON or not because the framework would have already converted it to a List/Map the moment it was received from the external source. I wasn't picturing the use of static utility methods, just direct access to whatever library we chose to include. Either way though, I really don't mind what approach is taken, I was offering some thoughts that came to mind. > Json string parameters as a service input are not recognized by OFBiz > ServiceEventHandler. > ------------------------------------------------------------------------------------------ > > Key: OFBIZ-5790 > URL: https://issues.apache.org/jira/browse/OFBIZ-5790 > Project: OFBiz > Issue Type: Improvement > Affects Versions: Trunk > Reporter: Amardeep Singh Jhajj > Priority: Minor > Attachments: CommonEvents.java.patch, JSON.java.patch, > OFBIZ-5790.patch, jackson-annotations-2.4.0.jar, jackson-core-2.4.2.jar, > jackson-databind-2.4.2.jar > > > I was trying to pass the Json string as a input to a service, but is not > recognized by ServiceEventHandler. > Example Json String- {"faciltyId": "WebStoreWarehouse"} > I worked on this issue and attached a patch here. Here I have used Jackson > Json library for parsing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)