I pushed out some changes to the jackson branch last night which: - make objects serialized as json use human readable datetimes - allow you to configure pretty printed json via the candlepin.pretty_print=<boolean> config value (looks awesome in the logs for debugging, if i do say so myself) - use either jackson or jaxb annotations for reading/writing objects, prefering the jackson ones, if present.
These are done by making our own jax-rs JsonProvider and twiddling the jackson configuration. In the process of writing this I found out that we could really do it with the provider provided (heh) by RestEasy or Jackson without subclassing, but I still do think the provider will be the place to do input validation, so I went ahead and made the class.
-James
Given the feedback (albeit marginal) from the rest-easy guys.. if you all like this.. push it in.
It will break the java and ruby clients.. but that is ok. They can be fixed
-- bk
On 05/19/2010 09:49 AM, James Bowes wrote:
I pushed out some changes to the jackson branch last night which:
- make objects serialized as json use human readable datetimes
- allow you to configure pretty printed json via the candlepin.pretty_print=<boolean> config value (looks awesome in the logs for debugging, if i do say so myself)
- use either jackson or jaxb annotations for reading/writing objects, prefering the jackson ones, if present.
These are done by making our own jax-rs JsonProvider and twiddling the jackson configuration. In the process of writing this I found out that we could really do it with the provider provided (heh) by RestEasy or Jackson without subclassing, but I still do think the provider will be the place to do input validation, so I went ahead and made the class.
-James
candlepin mailing list candlepin@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/candlepin
Does this mean you are going to remove the non-jackson libraries for doing JSON once it is merged?
On 05/24/2010 08:56 AM, Bryan Kearney wrote:
Given the feedback (albeit marginal) from the rest-easy guys.. if you all like this.. push it in.
It will break the java and ruby clients.. but that is ok. They can be fixed
-- bk
On 05/19/2010 09:49 AM, James Bowes wrote:
I pushed out some changes to the jackson branch last night which:
- make objects serialized as json use human readable datetimes
- allow you to configure pretty printed json via the candlepin.pretty_print=<boolean> config value (looks awesome in the logs for debugging, if i do say so myself)
- use either jackson or jaxb annotations for reading/writing objects, prefering the jackson ones, if present.
These are done by making our own jax-rs JsonProvider and twiddling the jackson configuration. In the process of writing this I found out that we could really do it with the provider provided (heh) by RestEasy or Jackson without subclassing, but I still do think the provider will be the place to do input validation, so I went ahead and made the class.
-James
candlepin mailing list candlepin@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/candlepin
candlepin mailing list candlepin@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/candlepin
On Mon, May 24, 2010 at 09:56:50AM -0400, Adam Young wrote:
Does this mean you are going to remove the non-jackson libraries for doing JSON once it is merged?
yeah, i'd see no point in keeping a dep on jettison around.
On 05/24/2010 08:56 AM, Bryan Kearney wrote:
Given the feedback (albeit marginal) from the rest-easy guys.. if you all like this.. push it in.
It will break the java and ruby clients.. but that is ok. They can be fixed
-- bk
On 05/19/2010 09:49 AM, James Bowes wrote:
I pushed out some changes to the jackson branch last night which:
- make objects serialized as json use human readable datetimes
- allow you to configure pretty printed json via the candlepin.pretty_print=<boolean> config value (looks awesome in the logs for debugging, if i do say so myself)
- use either jackson or jaxb annotations for reading/writing objects, prefering the jackson ones, if present.
These are done by making our own jax-rs JsonProvider and twiddling the jackson configuration. In the process of writing this I found out that we could really do it with the provider provided (heh) by RestEasy or Jackson without subclassing, but I still do think the provider will be the place to do input validation, so I went ahead and made the class.
-James
candlepin mailing list candlepin@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/candlepin
candlepin mailing list candlepin@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/candlepin
candlepin mailing list candlepin@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/candlepin
-James
The branch is in master now. After a quick poll in channel we decided to stick with camelCase variable names, just to keep things saner.
Let me know if anything breaks!
-James
candlepin@lists.stg.fedorahosted.org