Hi Claus, Using Javadoc as a starting point is a good thing but probably not enough in some case where by example we need more information about : - How to use Xpath to extract from the header/body data ? - How can I split the content of my body ? - How to create correctly a choice.when - otherwise or try/block .... ?
To increase the visibility of Camel compare to another opensource ESB solution like Mule, ... we must improve the quality of the documentation in order to show How easy is it to develop a solution using Camel and Why Camel simplify the developer's life ? The documentation must be orchestrated around three sections like this is partially the case today : - EIP : Each pattern must be explained with java DSL language and its equivalent in Spring XML config file - Processor : Each processor type must be .... - Expression : Each expression language ... Remark : The SCALA documentation uses a little bit this approach. Kind regards, Charles Moulliard Claus Ibsen wrote: > > > > Hi > > This is an area where Camel sadly lack documentation - the DSL. > We have had a discussion about this for Camel 2.x how to add such > documentation. > > If anyone have good ideas we are glad to hear about it. The issue is that > we would like to document the DSL where we code it, eg in the java code > and then with some tool being able to extract it into wiki. > > From the javacode we should be able to extract it into the camel-spring > XSD as well, and a 3rd bonus is if its javadoc based then your java editor > can also popup with help if you use the DSL in java. > > Also keeping it in java code then the chance is much higher that the wiki > documentation is not out-of-sync. > > For now the best option is to look the unit test using this constructs, > search the wiki documentation and these mailing lists. > > > Med venlig hilsen > > Claus Ibsen > ...................................... > Silverbullet > Skovsgårdsvænget 21 > 8362 Hørning > Tlf. +45 2962 7576 > Web: www.silverbullet.dk > -----Original Message----- > From: cmoulliard [mailto:[EMAIL PROTECTED] > Sent: 8. august 2008 17:06 > To: [email protected] > Subject: Is there a wiki page describing the processor : TryBlock, handle, > End, finally ? > > > Hi, > > I have checked the wiki web site but without success. To be sure, I prefer > to ask questions > > 1) Is there a wiki page describing the processor of type : TryBlock, > handle, > End, finally ? > > 2) It should be interesting to create a table in the processor page to > list > all the processor available and to explain what they can do or offer ? > > Kind regards, > > Charles Moulliard > > > > > ----- > Enterprise Architect > > Xpectis > 12, route d'Esch > L-1470 Luxembourg > > Phone +352 25 10 70 470 > Mobile +352 621 45 36 22 > > e-mail : [EMAIL PROTECTED] > web site : www.xpectis.com www.xpectis.com > My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ > -- > View this message in context: > http://www.nabble.com/Is-there-a-wiki-page-describing-the-processor-%3A-TryBlock%2C-handle%2C-End%2C-finally---tp18893613s22882p18893613.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > > ----- Enterprise Architect Xpectis 12, route d'Esch L-1470 Luxembourg Phone +352 25 10 70 470 Mobile +352 621 45 36 22 e-mail : [EMAIL PROTECTED] web site : www.xpectis.com www.xpectis.com My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ -- View this message in context: http://www.nabble.com/Is-there-a-wiki-page-describing-the-processor-%3A-TryBlock%2C-handle%2C-End%2C-finally---tp18893613s22882p18921146.html Sent from the Camel - Users mailing list archive at Nabble.com.
