Re: Schema resolution failure when the writer's schema is a primitive type and the reader's schema is a union

2012-08-31 Thread Scott Carey
My understanding of the spec is that promotion to a union should work as long as the prior type is a member of the union. What happens if the union in the reader schema union order is reversed? This may be a bug. -Scott On 8/16/12 5:59 PM, Alexandre Normand alexandre.norm...@gmail.com wrote:

Re: Schema resolution failure when the writer's schema is a primitive type and the reader's schema is a union

2012-08-31 Thread Doug Cutting
I responded to the Jira, but will respond here too for completeness. I believe the problem is that the decoder is incorrectly constructed with the reader's schema rather than the writer's schema. It should instead be constructed in this example with: JsonDecoder jsonDecoder =