Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <15988333.post@talk.nabble.com>
Date: Tue, 11 Mar 2008 12:45:17 -0700 (PDT)
From: pds1602 <paul.soule@ds-s.com>
To: camel-user@activemq.apache.org
Subject: Re: Documentation
In-Reply-To: <ec6e67fd0803110351w6486ed92m4f198f20beeb2c3c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <15975864.post@talk.nabble.com>
 <ec6e67fd0803110351w6486ed92m4f198f20beeb2c3c@mail.gmail.com>


May I suggest two changes that I think will really accelerate Camel adoption:

1. None of the patterns are of any significant use, besides playing, unless
a global transaction can be applied to a route. It is absolutely vital to
have this. This includes things like reading from a file - it should be
transactional even to the level of a row of file data. Otherwise how can it
compete with commercial products like MQ Broker?

2. No additional components are added without extensive documentation and
all development stops until documentation is done. Do not accept any new
components without documentation and accept nothing unless it can
participate in a global transaction.

I know it sounds harsh but, please believe me, it must be done if your
target audience are enterprise developers. Having components released with
no documentation is unforgivable. Without the above, Camel will amount to
little, which is a shame because it's almost there....

Paul


James.Strachan wrote:
> 
> On 11/03/2008, pds1602 <paul.soule@ds-s.com> wrote:
>>  The documentation for Camel seems to be severely lacking or inconsistent
>> or
>>  both. For example the JPA documentation, the little that there is, is
>>  inconsistent. One part of the documentation says you should use jpa://
>> and
>>  the examples jpa:
> 
> Camel us usually pretty forgiving, you can use scheme:// or scheme:
> 
>> and the examples has options (e.g. polling) not mentioned
>>  in the list of jpa options. I spend hours figuring out how that
>> component
>>  worked. Immensely frustrating.
> 
> Sorry about that. Fancy contributing? :)
> 
>>  I'm now looking at the jdbc component and there is no documentation
>>  whatsoever, or none that I can find. Can someone give an example of how
>> to
>>  use it?
> 
> I'm not sure we have one right now other than the test cases
> -- 
> James
> -------
> http://macstrac.blogspot.com/
> 
> Open Source Integration
> http://open.iona.com
> 
> 

-- 
View this message in context: http://www.nabble.com/Documentation-tp15975864s22882p15988333.html
Sent from the Camel - Users mailing list archive at Nabble.com.