I just tested and it seems that Jettison 1.2 produces the same JSON. The tests were passing in ActiveMQ as core module was still using 1.0 version. So the only workaround for now is to actually downgrade to 1.0. I'll try to see what's changed in between and if it can/should be fixed.
Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Jul 13, 2010 at 8:48 AM, Dejan Bosanac <de...@nighttale.net> wrote: > Hi, > > it must be the due to jettison version used. Can you try upgrading it > to 1.2 (lib/optional folder) and see if it works for you? > > Cheers > -- > Dejan Bosanac - http://twitter.com/dejanb > > Open Source Integration - http://fusesource.com/ > ActiveMQ in Action - http://www.manning.com/snyder/ > Blog - http://www.nighttale.net > > > > On Mon, Jul 12, 2010 at 9:38 PM, gtsafas <gtsa...@rblt.com> wrote: >> >> Additional example >> >> {"map":[{"entry":[{"string":[8059,"N"]},{"string":[8055,"NSDQ"]},{"string":[8 >> >> >> >> -- >> View this message in context: >> http://old.nabble.com/JMS-MAP-JSON-Improper-Data-structure-tp29140193p29143081.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> >
