On 16/04/2008, Martin Gilday <[EMAIL PROTECTED]> wrote:
> Thanks for the positive feedback guys.  The TODOs are there are my short
>  term goals of where I think I can take it.   I tried to make something
>  semi-realistic by using JMS, as a lot of samples just use "direct" to
>  "direct" routes.  I assume this is simply for ease of writing the sample
>  tests, as unless I am missing something you would never really bother
>  doing that?

Yeah - its really to a make the simplest example with the simplest
dependencies. The direct: endpoint just depends on the camel-core.jar
so there's no need for a JMS provider, a message broker and all that
stuff which can cause confusion for beginners.

But loads of folks using Camel use JMS so having a good JMS tutorial
would really help folks do more real world stuff; once they've moved
beyond learning how to use EIP with Camel.


>  I think Jonathan's idea of getting the tutorial code in the svn repo is
>  a good, otherwise they are going to get out of sync pretty quickly if I
>  keep attaching new zip files.  What is the best way to do this?  Should
>  I create a JIRA task so a committer can put it somewhere?

Perfect. There's more details here...
http://activemq.apache.org/camel/contributing.html

but basically just raise a  JIRA and attach some code (remember to
click the checkbox when you add your attachment that you are granting
the ASF use of the code etc). Then we can commit it and hopefully use
it as an integration test - as well as a tutorial and working example
folks can reuse.



>  James I think your restructuring of the user guide is a step in the
>  right direction.  However I think it might be worth it if I try hacking
>  at merging the two getting starting guides.  The short one is too short
>  being just a simple list of what you need to know, and should probably
>  just be on the user guide page itself.

Great idea! :)

It definitely needs a bit of refactoring.

>  Then I can rework the longer
>  guide.  I think I will move the critque of the docs to a new page and
>  then move some of the general "how to read the docs" info to be an
>  introduction to the user guide.  This should keep each part focussed on
>  the topic.

Great stuff


>  I've tried updating the navigation bar [1] to include tutorials but it
>  had no affect on the home page.  Is there somewhere else I need to
>  change or is it just caching?
>
>  [1]http://cwiki.apache.org/confluence/display/CAMEL/Navigation

Its a tad complex. This page might help a little...
http://activemq.apache.org/camel/how-does-the-website-work.html

basically caching means it takes a while to appear - though you can
usually check your updates at
http://cwiki.apache.org/CAMEL/

one extra complication is the generation of that static html sometimes
has bugs (i.e. some changes to included pages like navigation don't
always force the regeneration of the entire site). So I often kick off
a manual export to HTML from time to time.

-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com

Reply via email to