Totally agreed with everything said so far in this thread. I'd also like improved tools for working with Camel. e.g.
create a command line console for Camel for use in ServiceMix https://issues.apache.org/activemq/browse/CAMEL-743 a visualisation plugin using Eclipse / Zest / GEF https://issues.apache.org/activemq/browse/CAMEL-418 Delayer https://issues.apache.org/activemq/browse/CAMEL-640 tracer - configuration from spring XML https://issues.apache.org/activemq/browse/CAMEL-700 2008/7/23 Claus Ibsen <[EMAIL PROTECTED]>: > Hi > > DSL Documentation: > ================== > - Yes it is definitely needed. For new users to Camel starting with the Java > DSL can be a bit troublesome to know how to use, after you got the hello > logger here I am working with from(xxx).to("log:hello") > > 1) We could add documentation to the javadoc (and use SNIPPET or some other > tools to extract it to the wiki). We are able to quickly determinate what DSL > types we have documentation for and not. Also the IDEs will be able to quick > tooltip the javadoc for end-users. > > > 2) We could add it to wiki. However it's harder to be sure that we got them > all covered and staying in-sync for the future, and that all options is > documented as well. > > > 3) How can we with tools get the documentation in the spring XSD as well? there's an existing JIRA for this... https://issues.apache.org/activemq/browse/CAMEL-632 am hoping at some point someone hacks JAXB to preserve javadoc comments and add them to the <xs:documentation> elements in the generated XSD -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
