Hi I think this is a good idea. When you store data in a RDBMS you may want to use SQL types that is readable by humans, such as VARCHAR2 (or what they are called today).
So maybe have some way to make this easier to say if header/body should be binary or text based. Yes you can create your own AggregationRepository or extend the existing. But maybe if it was possible to add an option on the JDBC AggregationRepository to control if its binary or text, that would be nice. On Sat, Sep 8, 2012 at 12:07 PM, AlanFoster <a...@alanfoster.me> wrote: > Thanks for your Response Christian > > I wonder if there's a nice way to keep all of the functionality of the > current Jdbc aggregator that the sql-component offers, but just change the > way it marshalls the data? Through blueprint property setters > > I looked into the source code for this area, and I noticed the main point of > marshalling/unmarshalling the exchange is done with the codec : > private JdbcCamelCodec codec = new JdbcCamelCodec(); > > This would be the only thing that needs to be changed right? But the class > type is final so it can't be extended and the JdbcAggregationRepository > class has no getters/setters for the codeec field so it can't be changed at > all through blueprint configuration =[ > > Can you recommend the expected way to change this sort of functionality > without creating my own new aggregation repository from scratch please? > > Thanks again for the help > Alan > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Change-Sql-Component-BLOB-datatype-to-XML-for-Aggregator-serialization-tp5718845p5718896.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
