[
https://issues.apache.org/jira/browse/AXIS2-5513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shameera Rathnayaka closed AXIS2-5513.
--------------------------------------
Resolution: Later
JSR 353-Java API doesn't provide enough data to make this change. In processing
we need to know every token in JSON which is not available with above
spec.Hence I am moving this to later.
> Decouple google-gson from JSON xml stream basae approach using JSR 353(Java
> api to JSON processing)
> ---------------------------------------------------------------------------------------------------
>
> Key: AXIS2-5513
> URL: https://issues.apache.org/jira/browse/AXIS2-5513
> Project: Axis2
> Issue Type: Improvement
> Components: json
> Affects Versions: 1.7.0
> Reporter: Shameera Rathnayaka
> Assignee: Shameera Rathnayaka
> Labels: gson, json, jsr-353
> Fix For: 1.7.0
>
>
> Currently newly added JSON XML Stream API base approach, tightly couple with
> google-gson. Decoupling google-gson from this would make more extensible to
> use other JSON Stream APIs(like Jakson). Here we can use factory method
> pattern to create JSON XMLStreamReaders/writers . And we can provide an
> api(this will be JSR 353-Java API for JSON processing) to implement Gson,
> Jakson or any other Json Stream support api to write the logic under that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]