Hi,
just a follow up. The problem was not in Jettison itself, but XStream
version 1.3.1. I implemented a workaround fix in the trunk and
upgraded Jettison to 1.2, which will make everything ok for the 5.4.0
release. Hopefully, XStream 1.3.2 will fix this. See
https://issues.apache.org/activemq/bro
Hi,
jars from lib/optional are loaded as well, so keep only one instance
of the library in those folders.
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
Checked on DEV Machine, confirmed that swaping to 1.0 fixed the issue
-jettison1.2.jar
$VAR1 =
'{"map":[{"entry":[{"string":[113,"N"]},{"string":[19,30057090]},{"string":[55,"STRL"]},{"string":[17,1005000322]},{"string":[382,1]},{"string":[39,2]},{"string":[14,100]},{"string":[11,2304210071300010
Ok, now I was under the impression .jars go into the lib folder and
lib/optional was not loaded? If there is a file in lib will it take
precedence over the lib/optional? or will it be ignored? I ask because I
realize I had jettision 1.2 inside of the activemq/lib folder and jettision
1.1 inside of
Hi,
yes, putting Jettison 1.0 in lib/optional folder (and deleting the one
that comes with the distro) should do the trick for now.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http
So you are saying that I should be downgrading to Jettison 1.0?
Dejan Bosanac wrote:
>
> 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 downg
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
--
Dej
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
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.
