Ah OK - looks like we need to enhance the Smooks library then? >> Yes.
Fancy taking a stab at it? :) >> No but we need a generic solution to allow user to work with non-XML >> format (otherwise they will use smooks with mule or jboss esb with smooks >> even if camel is better). Of course, Smooks is a competitor because it >> provides routing facility >> (http://svn.codehaus.org/milyn/trunk/smooks-examples/jms-router/) like >> spring integration, CXF, ... Life is not a game and this is the same for >> the java frameworks. Camel can support any payload? >> I don't know but I think that we should be able to provide as a parameter >> the payload (like spring integration or mule) to the endpoint in order to >> work with the content (message, header, ...). James.Strachan wrote: > > 2008/12/11 cmoulliard <[EMAIL PROTECTED]>: >> This is not possible because the current implmentation only support EDI >> (http://cwiki.apache.org/CAMEL/smooks.html) > > Ah OK - looks like we need to enhance the Smooks library then? Fancy > taking a stab at it? :) > > >> It is time to propose for Camel 2.5 or 3.0 a generic solution (= >> endpoints) >> to process correctly non XML format in Camel. > > Camel can support any payload? > >> By the way, I think it should be a good idea in the camel project tree to >> split the component providing endpoint from the component like csv, >> suoercsv >> providing support for DataFormat ? > > Not sure I follow? > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ > > ----- Charles Moulliard SOA Architect My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ -- View this message in context: http://www.nabble.com/Is-there-a-way-to-extend-marshall-method-of-CsvDataFormat-class-tp20955830s22882p20957528.html Sent from the Camel - Users mailing list archive at Nabble.com.
