Hi Reuben, I'm the person who submitted the component to the community.
It's great news that you are already jumping ahead of time and using it! ;) Any feedback provided will have huge value at this point. If you happen to open JIRAs, please post them here too to aid tracking, or assign them to me. If you get the chance, review the docs as well, and do let me know if they are clear and detailed enough. I definitely thought about adding support for a generic DbCommand operation, but wanted to see first what the traction was. It should be pretty straightforward. Can you open a ticket? I'll work on it. Thanks a lot! P.S.: Soon I'll be releasing a camel-xmljson data format to convert from XML to JSON and back directly without JAXB or passing via interim Java objects. It's based on json-lib's highly-configurable XMLSerializer. Hopefully it should make life easier when working with XML and JSON. So keep tuned! Regards, Raul. On 23 Mar 2012, at 21:23, RubyTuesdayDONO <reubengarr...@gmail.com> wrote: > I'm really glad we now offer a mongoDB component. It's even helped push me > out of the nest - I'm building trunk for the first time just so I can try it > out! > > What do you think about adding support for arbitrary DB commands? It could > be a neat way to trigger a Map-Reduce, execute server-side javascript, or > even run administrative operations. > > I'm thinking this would be easy to implement since MongoDB accepts command > invocations encoded in a BSON document. We'd only have to add an operation > like "dbCommand" to the endpoint, and send the command to it in the same way > that queries are sent for the findAll operation. > > http://www.mongodb.org/display/DOCS/Commands > > ~ Reuben > > -- > View this message in context: > http://camel.465427.n5.nabble.com/DISCUSS-Camel-and-MongoDB-tp5117168p5590738.html > Sent from the Camel Development mailing list archive at Nabble.com.
