Hi Ah great to know it was hardcoded. I would suggest to ask them to add an option so you can turn that off. As there are use cases where you only need a one way transformation.
They could also consider different strategies how to control this mapping. So there is a default strategy that does as today. And then people can switch to different ones, such as one that simply dont include those signs. And another that allow end users to provide their own mapping code to have 100% control how they want to do that. An alternative is that we introduce an option in the Camel component but then it would need to process the output message and remove those @ signs. But its IMHO better to improve this in the xmljson library itself. On Mon, Nov 17, 2014 at 9:10 PM, salemi <sal...@avaya.com> wrote: > Hi Clause, > > I looked at their json-lib code and based on what I read they need to have > the @ sign for the attributes and # for the text elements. > They need those "annotations" to be able to covert a json properly back to > xml. The @ and # signs are hard coded in their code. > > Do you think I should asked to change the code? > > Ali > > > > > > ----- > Alireza Salemi > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-xmljson-add-signs-to-the-json-output-how-to-remove-the-signs-tp5759013p5759220.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
