[
https://issues.apache.org/jira/browse/OFBIZ-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184425#comment-14184425
]
Scott Gray commented on OFBIZ-5790:
-----------------------------------
It does the conversion at the point of entry and exit based on the
content-type/accept http headers. My statement that you quoted above was in
reference to why I didn't see the need for a JSON type that you mentioned
previously.
I was simply saying that the number of likely places we'd want to convert
Objects to JSON strings and vice-versa is limited enough that we could consider
forgoing the extra code required to abstract it out and simply use the library
directly.
The issue with multiple exit points for JSON right now is because they aren't
using the json request chain from common-controller.xml (or whatever we decide
to replace it with). I'm sure we'd prefer these events to output a Map of data
than hard-coding a JSON response directly to the response stream. And if that
is the case, then it seems like the number of touch points on a JSON library
would be minimal.
> 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)
